I have 2 orchestrations.  My 'Called' orchestration will be calling a web
service (I will be sending a request and getting a response back).



In my 'Calling' orchestration, I create 2 messages  - both are 'Web Message
Types', one is the request, the other is the response.  I construct the
request message and then call my 2nd orchestration.  In the parameters
property of the CallOrchestration shape, I use the 2 parameters I set up in
the 'Called' Orchestration.



In my 'Called' orchestration, I set up 2 Orchestration Parameters that have
the same 2 message type as above.  The 1st parameter I call 'In' and is the
request message and the direction is IN.  The 2nd parameter I call 'Out' and
is the response message and the direction is OUT.



I've tried a couple different things, but I get errors



1) In the 'called' orchestration, my first step is to have a send shape
perform the request of the web service, the 2nd step is to have a receive
shape get the response from the web service.  For the receive shape,  I
assign the message property to a message that I created (named myResponse)
in this 'Called' orchestration.  It is the same message as the response
message in my original 'Calling' Orchestration.  I then use a construct
shape to construct the OUT parameter... I do the following in the Message
assigment shape in the construct...  Out = myResponse;



When I compile, I get this error:  'out' parameter must be definitely
assigned





So then I tried this...



2)  In the 'Called' Orchestration I remove the construct of the OUT
parameter and in the Receive shape, I assign the message property directly
to the OUT parameter...



When I compile, I get the same error:  'out' parameter must be definitely
assigned





I imagine the #2 above would be the best way to go, but I can't get past the
error.





Any ideas what I'm doing wrong?





Thanks in advance, Brian

[ Post a follow-up to this message ]

Without seeing "called orch", I'm not sure - perhaps the orchestration
compiler isn't convinced all paths will initialize your out parameter.

As a workaround, you might try constructing your out param right at the top
of the called orchestration (assigning it to, say, xmlDoc where
xmlDoc.LoadXml("<failed/>" or some such thing.)  You can construct it again
later with the actual content.

Scott Colestock
www.traceofthought.net


"Brian Cesafsky" <Brian.Cesafsky@AutoTrackerPlus.com> wrote in message
news:OFsKgQVYFHA.712@TK2MSFTNGP14.phx.gbl...
>I have 2 orchestrations.  My 'Called' orchestration will be calling a web
>service (I will be sending a request and getting a response back).
>
>
>
> In my 'Calling' orchestration, I create 2 messages  - both are 'Web
> Message Types', one is the request, the other is the response.  I
> construct the request message and then call my 2nd orchestration.  In the
> parameters property of the CallOrchestration shape, I use the 2 parameters
> I set up in the 'Called' Orchestration.
>
>
>
> In my 'Called' orchestration, I set up 2 Orchestration Parameters that
> have the same 2 message type as above.  The 1st parameter I call 'In' and
> is the request message and the direction is IN.  The 2nd parameter I call
> 'Out' and is the response message and the direction is OUT.
>
>
>
> I've tried a couple different things, but I get errors
>
>
>
> 1) In the 'called' orchestration, my first step is to have a send shape
> perform the request of the web service, the 2nd step is to have a receive
> shape get the response from the web service.  For the receive shape,  I
> assign the message property to a message that I created (named myResponse)
> in this 'Called' orchestration.  It is the same message as the response
> message in my original 'Calling' Orchestration.  I then use a construct
> shape to construct the OUT parameter... I do the following in the Message
> assigment shape in the construct...  Out = myResponse;
>
>
>
> When I compile, I get this error:  'out' parameter must be definitely
> assigned
>
>
>
>
>
> So then I tried this...
>
>
>
> 2)  In the 'Called' Orchestration I remove the construct of the OUT
> parameter and in the Receive shape, I assign the message property directly
> to the OUT parameter...
>
>
>
> When I compile, I get the same error:  'out' parameter must be definitely
> assigned
>
>
>
>
>
> I imagine the #2 above would be the best way to go, but I can't get past
> the error.
>
>
>
>
>
> Any ideas what I'm doing wrong?
>
>
>
>
>
> Thanks in advance, Brian
>
>

[ Post a follow-up to this message ]