Ouch!. This would prevent me or other users of SOAP from using Xerces 2.3.0 ..... even though its a bug in the SOAP schema, specially if the schema is retrieved from the w3c's website.
... unless:
1) I modify the SOAP schema to make it correct 2) An ErrorHandler is used to specifically ignore this bug
[EMAIL PROTECTED] wrote:
It's a bug in SOAP schema. Xerces 2.2.1 and earlier versions didn't complain about it because they had a bug too. :-(
3.2.6 of the structure spec:
"2 if there is a {value constraint}, the canonical lexical representation of its value must be �valid� with respect to the {type definition} as defined in String Valid (�3.14.4)."
In the schema, the default is "0", with canonical rep "false", which is not valid wrt the pattern.
Cheers, Sandy Gao Software Developer, IBM Canada (1-905) 413-3255 [EMAIL PROTECTED]
"Jesus M. Salvo Jr." To: Xerces mailing list <[EMAIL PROTECTED]> <[EMAIL PROTECTED] cc: sia.com> Subject: Bug in 2.3.0 ... or bug in SOAP schema? 02/20/2003 11:22 PM Please respond to xerces-j-user
Currently using 2.2.1 and trying out 2.3.0.
When I was validating a SOAP envelope using Xerces 2.3.0, it complained with the following:
Error: URI=file:///c:/workarea/schemas.xmlsoap.org.xsd Line=70: a-props-correct.2: Invalid value constraint value '0' in attribute 'mustUnderstand'.. Error: URI=file:///c:/workarea/schemas.xmlsoap.org.xsd Line=70: a-props-correct.2: Invalid value constraint value '0' in attribute 'mustUnderstand'..
It seems to be complaining about the SOAP schema definition from w3c ( available at http://schemas.xmlsoap.org/soap/envelope/ ), which has the following for "mustUnderstand" ( which is line 70 just like the above error says ):
<!-- Global Attributes. The following attributes are intended to be
usable via qualified attribute names on any complex type referencing them.
-->
<xs:attribute name="mustUnderstand" default="0" >
<xs:simpleType>
<xs:restriction base='xs:boolean'>
<xs:pattern value='0|1' />
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="actor" type="xs:anyURI" />
Xerces 2.2.1 was not complaining about the above
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
