Subjects
Home
VOTE Move XML Commons to Xerces
Commented: (XERCESJ 589) Bug with pattern restriction on long strings
: Xerces J 2 8 1 Release on Wednesday, September 13th
: Xerces J 2 9 0 Release on Wednesday, November 22nd
Commented: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1178) Error getting prefix for an attribute with no n
Updated: (XERCESJ 1244) XMLSchemaValidator does not contribute element 's
Some consideration about the xerces DOM implementation
Updated: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1227) Poor performance / OutOfMemoryError for sequenc
retain exception stack traces
Updated: (XERCESJ 1193) NPE or hang when parsing using the "continue afte
Future of NekoHTML
Commented: (XERCESJ 1203) NPE in XMLDTDProcessor
DOM Level 3 APIs for Xalan J and a new Xalan release (2 7 1)
: xml commons external 1 3 04 Release on Wednesday, November 22nd
Commented: (XERCESJ 1247) Incorrect location information on SAX when usin
XInclude exceptions how to mirror Xerces J functionality into Xerces C++?
First proposal on SoC project "Add support for the StAX (JSR 173) cursor API
: xml commons resolver 1 2 Release on Wednesday, November 22nd
Typo in RangeToken java Please check
Validator features
java lang ClassCastException when adopting Node
using the org apache xerces impl xs identity package
Updated: (XERCESJ 1257) buffer overflow in UTF8Reader for characters out
Problem with ref attributes and schema validation
Updated: (XERCESJ 122) XMLSchemaValidator does not contribute element 's d
Performance problem under load Xerces with Weblogic 9 x
remove ignored memory allocation
Commented: (XERCESJ 1177) SAXXMLStreamReader doesn 't always report namesp
Commented: (XERCESJ 977) Null pointer exception during DOM parsing
Commented: (XERCESJ 1197) Code cleanup for org apache xml serialize
Commented: (XERCESJ 1201) Initial contribution for StAX Event API
Updated: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special c
Commented: (XERCESJ 1199) SAXXMLStreamReader should attempt to register a
Commented: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special
Updated: (XERCESJ 589) Bug with pattern restriction on long strings
StackOverflow
xerces Range unnecessarily not garbage collectable if not detached
Updated: (XERCESJ 1178) Error getting prefix for an attribute with no nam
Bug in xs:redefine
Commented: (XERCESJ 1204) Can not set XMLEntityResolver for LSParser
Updated: (XERCESJ 1253) Prototype for SoC2007 project "Add support for th
Updated: (XERCESJ 1259) Add SteamFilter Function to SoC2007 project "Add
Assigned: (XERCESJ 444) SAXException thrown by EntityResolver is reported
Google Summer of Code 2007
Xerces J and XInclude relative path issue
Assigned: (XERCESJ 206) Stack overflow when using a schema validation
Commented: (XERCESJ 1215) Restrictions involving two levels of substituti
Closed: (XERCESJ 1203) NPE in XMLDTDProcessor
non overriding equals methoda
Resolved: (XERCESJ 1079) invalid value returned for TOTALDIGITS facet in
Xerces AS3 port
Updated: (XERCESJ 325) Regular Expression; Pattern "| " clause order de
Updated: (XERCESJ 1196) Javadoc generation fails on Java SE 5 0
Closed: (XERCESJ 1202) DTD validation on XIncluded documents when the sch
Created: (XERCESJ 1124) Nonspecific schema error message
a bug in xerces
Updated: (XERCESJ 1201) Initial contribution for StAX Event API
Closed: (XERCESJ 1254) Empty uris in targetNamespace attribute not report
Links
Home
Oracle database error code
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Bug in 2.3.0 ... or bug in SOAP schema?

Bug in 2.3.0 ... or bug in SOAP schema?

2003-02-21       - By sandygao@(protected)
Reply:     1     2     3  

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
sandygao@(protected)




                     "Jesus M. Salvo
                     Jr."                     To:       Xerces mailing list
<xerces-j-user@(protected)>
                     <jesus.salvo@(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 Linep:
a-props-correct.2: Invalid value constraint value '0' in attribute
'mustUnderstand'..
Error: URI=file:///c:/workarea/schemas.xmlsoap.org.xsd Linep:
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: xerces-j-user-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-user-help@(protected)





---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-user-help@(protected)