Proposed Text: WSN2.56: Schema validation error for fault types extended from WSRF BaseFaultType

["Patil, Sanjay" <sanjay.patil@sap.com>]

Here is proposed text for the new issue against BaseN discussed on the call today. I borrowed bulk of the issue text from the email discussions. A similar issue will also be raised for BrokeredN.
Thanks,
Sanjay

WSN2.56: Schema validation error for fault types extended from WSRF BaseFaultType

If you extend the WSRF BaseFaultType in another namespace (as done by WSN) and add extra

elements in that extension, then the schema that does the extension (e.g.

WSN)  violates the Unique Particle Attribution constraint as it becomes

non-deterministic. This is because BaseFaultType ends with <xs:any

namespace="##other" minOccurs="0">. So in the extended fault type you can't

tell whether elements in an extended instance are to be validated by this

<any> or by the elements in the extended type

 

Specifications

• WS-BaseNotification

Proposed Recommendations

Comment out and exclude the extensions to WSRF BaseFaultType in the BaseN schema. This is a temporary solution to avoid the issue until a cleaner resolution is identified by WSRF.

Notes

Jun 20, 2005: This issue was raised and an approach was agreed.

Status:   Open – approach agreed

Date: Jun 20, 2005

Agreed Approach: See Proposed Recommendations.

Contact:

Peter Niblett

Cross Reference: