|
Home > Archive > BizTalk Server Orchestration > October 2005 > Last Send Port of Called Orchestration Skipped
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Last Send Port of Called Orchestration Skipped
|
|
| edsherfick@hotmail.com 2005-10-24, 10:32 am |
| The last send port in a called orchestration is skipped when the called
orchestration is called from a catch shape. The file is not delivered to the
send ports location. If the called orchestration is called from outside of a
try/catch shape block, its last send port will process a message correctly.
In both scenarios, HAT shows the message processed correctly through the
send port.
Should I add an additional send port the the called orchestration, the
previously skipped send port will correctly process its message, but the new
send port places as the last send port will not correctly process its message.
| |
| Ed Sherfick 2005-10-24, 10:32 am |
| Does anyone know if this is a known bug in with BizTalk 2004? I have to put
a "dummy" port at the end of the called orchestartion to insure it works
properly.
Thanks,
Ed
"edsherfick@hotmail.com" wrote:
> The last send port in a called orchestration is skipped when the called
> orchestration is called from a catch shape. The file is not delivered to the
> send ports location. If the called orchestration is called from outside of a
> try/catch shape block, its last send port will process a message correctly.
>
> In both scenarios, HAT shows the message processed correctly through the
> send port.
>
> Should I add an additional send port the the called orchestration, the
> previously skipped send port will correctly process its message, but the new
> send port places as the last send port will not correctly process its message.
>
| |
| Chris Tucker 2005-10-27, 2:47 am |
| Ok, is it a known issue that a flat file disassembler in a pipeline does not
seem to promote FIL.RecevedFilename? This was an excruciatingly painful
three days!
"edsherfick@hotmail.com" wrote:
> The last send port in a called orchestration is skipped when the called
> orchestration is called from a catch shape. The file is not delivered to the
> send ports location. If the called orchestration is called from outside of a
> try/catch shape block, its last send port will process a message correctly.
>
> In both scenarios, HAT shows the message processed correctly through the
> send port.
>
> Should I add an additional send port the the called orchestration, the
> previously skipped send port will correctly process its message, but the new
> send port places as the last send port will not correctly process its message.
>
|
|
|
|
|