[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Fwd: [TC Admin] AS4 EBMS Schema XSD BUG
Hi,
We are trying to validate EBMS messages against the schema that can be found here http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/core/ebms-header-3_0-200704.xsd but we are running into an issue.
In the XSD it mentions the following:
“Note that the eb:Messaging element cannot be empty (at least one of eb:SignalMessage or eb:UserMessage element must present).”
However if I validate a message that contains neither of those against this XSD it counts as valid still which seems like a bug to me. So am I looking at an old XSD for this specification? Perhaps there is a newer version that I should be using that doesn’t have this issue.
<xsd:sequence>
<xsd:element name="SignalMessage" type="SignalMessage" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="UserMessage" type="UserMessage" minOccurs="0" maxOccurs="unbounded"/>
<xsd:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
We thought maybe changing the above which is the current part that defines it to the below might fix the issue but were not sure.
<xsd:sequence>
<xsd:choice minOccurs="1" maxOccurs="unbounded">
<xsd:element name="SignalMessage" type="SignalMessage" maxOccurs="unbounded"/>
<xsd:element name="UserMessage" type="UserMessage" maxOccurs="unbounded"/>
</xsd:choice>
<xsd:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
Any help would be most appreciated.
Regards,
Stephen Law
Godalming College
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]