|
Home > Archive > BizTalk Server Orchestration > August 2004 > Call orchestration - exceptions
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 |
Call orchestration - exceptions
|
|
| ctaranto 2004-08-19, 5:52 pm |
| I am using the call orchestration shape to execute several
"sub-orchestrations" from within a long-running scope in a "main
orchestration". Subs all have orchestration-level long-running transactions.
When one of the "subs" throws an exception, it doesn't appear to be caught in
the exception handler in "main".
Am I correct that the exception won't be bubbled back up from the called
orchestration to the caller?
Thanks.
| |
| Enrico Zerilli 2004-08-22, 5:58 pm |
| Hi, you must put a scope's shape also inside the sons orchestrations if you
want catch the exceptions in the main orchestration.
Bye
"ctaranto" wrote:
> I am using the call orchestration shape to execute several
> "sub-orchestrations" from within a long-running scope in a "main
> orchestration". Subs all have orchestration-level long-running transactions.
> When one of the "subs" throws an exception, it doesn't appear to be caught in
> the exception handler in "main".
>
> Am I correct that the exception won't be bubbled back up from the called
> orchestration to the caller?
>
> Thanks.
| |
| ctaranto 2004-08-23, 5:50 pm |
| Enrico,
Thanks for the reply. Turns out that the problem was because I was
referencing an empty InnerException member on the caught exception. After
resolving that issue, exceptions are work properly without the need for an
additional scope on the child orchestration.
-Chris
"Enrico Zerilli" wrote:
[vbcol=seagreen]
> Hi, you must put a scope's shape also inside the sons orchestrations if you
> want catch the exceptions in the main orchestration.
>
> Bye
>
> "ctaranto" wrote:
>
|
|
|
|
|