[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsrf] Base Faults: Originator of a Nested Fault
Katy, my interpretation was the latter but this does imply that in a chain of BFs each BF element would replicate information available in the nested BF. I wonder whether a better pattern would be for outer BFs to (typically) NOT use this element (it is optional) and for it to be used only by the original (inner-most) BF. Regards, Ian Robinson STSM, WebSphere Messaging and Transactions Architect IBM Hursley Lab, UK ian_robinson@uk.ibm.com Katy Warr/UK/IBM@IBMGB To 21/01/2005 12:28 wsrf@lists.oasis-open.org cc Subject [wsrf] Base Faults: Originator of a Nested Fault In the case of a nested Base Fault, should the (outer-most) OriginatorReference refer to the originator of the outer-most fault or to the initial originator of the fault? I assumed the former (and that you would need to burrow into the faultCauses in order to extract the initial originator - and that this would also enable you to extract the complete path of the fault). However, the statement 'The outer-most fault may use this component to reference the actual source of the fault condition' suggests the latter. Can anyone clarify, or is the interpretation of this simply application-dependent? Thanks Katy
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]