You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by bu...@apache.org on 2003/03/13 09:11:30 UTC

DO NOT REPLY [Bug 17949] New: - Invalid value constraint value '0'

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17949>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17949

Invalid value constraint value '0'

           Summary: Invalid value constraint value '0'
           Product: Xerces2-J
           Version: 2.3.0
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Other
        AssignedTo: xerces-j-dev@xml.apache.org
        ReportedBy: kevinj@develop.com


I'm validating a SOAP message against my own schema and the soap-env and
soap-enc schemas.

I'm using the soap-envelope and soap-encoding schemas from
http://schemas.xmlsoap.org/soap/ to validate a soap message and I'm
getting an error for each

***********
error: org.xml.sax.SAXParseException: a-props-correct.2: Invalid value
constraint value '0' in attribute 'mustUnderstand'..
SystemId:
file:///D:/home/kevinj/Projects/XMLTools/test/schemas/soap-envelope.xsd
Column: 52
Line: 69
***********
***********
error: org.xml.sax.SAXParseException: a-props-correct.2: Invalid value
constraint value '0' in attribute 'root'..

SystemId:
file:///D:/home/kevinj/Projects/XMLTools/test/schemas/soap-encoding.xsd
Column: 41
Line: 35

The attributes look like this

  <xs:attribute name="mustUnderstand" default="0" >
     <xs:simpleType>
       <xs:restriction base='xs:boolean'>
           <xs:pattern value='0|1' />
         </xs:restriction>
     </xs:simpleType>
  </xs:attribute>

root is similar.

I've used these schemas with other versions of Xerces and with the .Net
Validating reader and everything is works/worked OK. 

If I remove the default values from the global attributes then everything works
OK. Is this a bug in Xerces or are the schemas at fault?

Thanks

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org