05-04-06 12:13 AM
Are you receiving the same message type on every listen shape? If not, if yo
u
could run into a lot of compilation and runtime problems that way..
Are you using any Scope shapes anywhere? If you try to receive a message
within a Scope shape, you'll get compilation errors because of Scope
limitations.
Direct binding should not be a problem in sequential convoys.
Lucas
--
===========
Lucas R. Vogel
"MS" wrote:
> Hi,
>
> I have a sequential convoy that gets message from other orchestrations. I
> have set up few receive shapes inside a listen shape and established a
> correlation.
>
> If I need to use the received messages later in my orchestration I get
> unconstructed message error on compile.
>
> My question:
> Is there any way I can use my received messages later on?
>
> Right now what I am doing is Creating temp messages manually for each type
> and initialinzing with some values.
>
> Then I use message construct after the receive shape inside Listen block a
nd
> assign it to the temp messages created earlier.
>
> It seems to work fine. Just curious to know If there is any other way of
> doing it?
>
> My other question is
>
> In sequential convoy is there any things I should be aware of, If, I decid
e
> to use Direct binding. any pros or cons. That will help me choose my appro
ach
>
> Currently I have One Receive port with several Receive locations.
> Other orchestrations sends message to these locations.
> My Main Processing orchestration is listening to this port.
> Once all the messages are received. It implements my business rules.
>
> Any suggestions will really help me.
>
> Thanks
>
>
[ Post a follow-up to this message ]
|