Dieter,
Thank you for your response.
After reading your message, I've reached the following
interpretation idea:
A <rethrow> throws the fault from the location of the
corresponding fault handler (<catch> or <catchAll>),
not from the location of <rethrow> itself.
A <rethrow> corresponds to a <catch> or <catchAll>
that enclose the <rethrow> without any intervening
<catch> or <catchAll>.
If we interpret this way, then in the example below
the rethrown fault will not be caught by FH2. We
don't need any additional constraints on the placement
of <rethrow>.
How do you like this?
Yuzo Fujishima
NEC Corporation
Dieter Koenig1 wrote:
>
>
>
> Yuzo, from my point of view, the answer to your questions shoud be as
> follows:
>
>
>>Q1: Is it legal to place the <rethrow> there?
>
> So far, the answer is yes. W.r.t. Q2, we should add a constraint that
> disallows nesting rethrow in a scope local to FH1.
>
>
>>Q2: Assuming the answer to Q1 is yes, will FH2 catch the rethrown fault?
>
> It should not. If FH2 rethrows the fault as well, we reenter FH1 and have a
> loop. With the constraint described in Q1, we would avoid this situation.
>
> Kind Regards
> DK
>
> Yuzo Fujishima <> wrote on 27.08.2004 13:18:26:
>
>
>>Hi,
>>
>>I have a question regarding where we can place <rethrow>.
>>
>>The current specification says:
>> <rethrow> activity can be used ONLY within a fault handler
>> (i.e. <catch> and <catchAll> elements).
>>
>>Therefore, I think the following is legal:
>> <faulthandlers>
>> <catch name="FH1" faultName="x:foo">
>> <sequence>
>> ...
>> <rethrow/>
>> </sequence>
>> </catch>
>> </faultHandlers>
>>
>>But I am not sure about the following:
>>
>> <faulthandlers>
>> <catch name="FH1" faultName="x:foo">
>> <sequence>
>> ...
>> <scope>
>> <faulthandlers>
>> <catch name="FH2" faultName="x:foo">
>> ...
>> </catch>
>> </faultHandlers>
>> <rethrow/>
>> </scope>
>> </sequence>
>> </catch>
>> </faultHandlers>
>>
>>Q1: Is it legal to place the <rethrow> there?
>>
>>Q2: Assuming the answer to Q1 is yes,
>> will FH2 catch the rethrown fault?
>>
>>Yuzo Fujishima
>>NEC Corporation
>>
>>
>>To unsubscribe from this mailing list (and be removed from the
>>roster of the OASIS TC), go to http://www.oasis-open.
>>org/apps/org/workgroup/wsbpel/members/leave_workgroup.php.
>>
>
>
>
> To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/leave_workgroup.php.
>
>
>