On 1 apr, 17:07, DNova <dno...@[EMAIL PROTECTED]
> wrote:
> Sounds to me like your orchestration may not be exposed as a simple
> web service. =A0In my experience BizTalk will always wrap parameters
> (which I understand is good practice). =A0There are a few things you can
> do to get aroundthis, some of them less elegant than others.
>
> Real quick and dirty:
> Create an orchestration variable of type XmlDo***ent (browse .NET
> types to get it).
> In your Message Assignment shape do:
> do***ent.LoadXml("<MyExposedResult>...</MyExposedResult>");
> using a string containing an instance of your XML response.
> Then ResultMessage =3D do***ent; will assign this to your result message
> and you can use it as you please.
> Be sure you get the XML right in the LoadXml.
>
> You could also store the XML as a resource within the project, which
> is probably a neater solution.
>
> Alternatively you could make a map to your result message type and
> just put some filler in it, like a constant value or something, do the
> transform first and the assignment second and you'll be set.
>
> If you want to see what your SOAP response looks like this will tell
> you more about what types you're returning. =A0I hope this helps,
> granted it's not exactly pretty.
>
> Kind Regards,
> -Dan
Hi Dan,
Thanks for your answer. For now I have implemented the quick and dirty
way and I am happy
to say that the project compiles now.
What would be the best way to start testing the application?
Best Regards,
Bas
|
