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.
Assigned: (XERCESJ-1061) Regex "$ " and "^ " characters treated as special

Assigned: (XERCESJ-1061) Regex "$ " and "^ " characters treated as special

2006-10-29       - By Michael Glavassevich (JIRA)

    [ http://issues.apache.org/jira/browse/XERCESJ-1061?page=all ]

Michael Glavassevich reassigned XERCESJ-1061:
---------------------------------------------

   Assignee: Michael Glavassevich

> Regex "$" and "^" characters treated as special chars in conflict with XML
Schema spec
> -----------------------------------------------------------------------------
---------
>
>                 Key: XERCESJ-1061
>                 URL: http://issues.apache.org/jira/browse/XERCESJ-1061
>             Project: Xerces2-J
>          Issue Type: Bug
>          Components: XML Schema datatypes
>    Affects Versions: 2.6.2
>         Environment: Test Environment: Win XP SP1, JDK v1.5.0_02, Xerces v2.6
.2 (manually used; overrides any other, if packaged with the JDK)
>            Reporter: Darien Kindlund
>         Assigned To: Michael Glavassevich
>            Priority: Minor
>         Attachments: RegexParser.diff, regexparser.java
>
>
> Xerces rejects the following schema:
> <xs:schema xmlns:xs='http://www.w3.org/2001/XMLSchema'>
>  <xs:element name="test">
>   <xs:simpleType>
>    <xs:restriction base="xs:string">
>     <xs:pattern value="$?[0-9]+\.[0-9]{2}" />
>    </xs:restriction>
>   </xs:simpleType>
>  </xs:element>
> </xs:schema>
> The code within org.apache.xerces.impl.xpath.regex.RegexParser throws a
parser exception over the use of the "$?" characters, unless the "$" character
is escaped. For example, this works:
>     <xs:pattern value="\$?[0-9]+\.[0-9]{2}" />
> The fundamental problem is that the Xerces RegexParser code does NOT follow
the XML Schema specification, as defined by this URL:
> http://www.w3.org/TR/2000/WD-xmlschema-2-20000407/#dt-metac
> Specifically, the XML Schema specification does NOT give special meaning to
the "$" and "^" characters, whereas the RegexParser code seems to indicate that
these characters have the normal, standard UNIX definitions of "end-of-line"
and "start-of-line" anchors respectively.
> Regards,
> --
> Darien Kindlund
> The MITRE Corporation
> InfoSec Engr / Scientist, Sr.
> kindlund@(protected)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http:/
/issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

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