[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsbpel] new issue - clarification on whether the QName of a faultneeds to be unique across all portTypes and operations
Hi Prasad, so the only *new* limitation with this proposal would be that portTypes and operatins must not contain the "." character when used with BPEL. Right? Best regards/Mit freundlichen Grüßen, Thomas Schulze Prasad Yendluri <pyendluri@webmet hods.com> To Thomas Schulze/Germany/IBM@IBMDE 24.07.2006 13:44 cc Ronald.Ten-Hove@Sun.COM, alex.yiu@oracle.com, wsbpel@lists.oasis-open.org Subject Re: [wsbpel] new issue - clarification on whether the QName of a fault needs to be unique across all portTypes and operations Hi Thomas, Yes, in the proposal I made, the BPEL faultName is always a QName. Instead of the current scheme to derive BPEL faultName QName for WSDL faults that does not result in unique QNames, the proposal uses all components of portType as below: BPEL faultName QName = <PortType-Namespace>:<portType name>.<operationname>.<fault name> The namespace prefix in the QName is WSDL fault's portType Namespace (same as now). The localPart (string after ':') uses all components of the portType of the WSDL fault. So, in the case of Initial Example in section 5.1, for these two portTypes where targetNamespace="http://manufacturing.org/wsdl/purchase" <wsdl:portType name="purchaseOrderPT">