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.
Updated: (XERCESJ-589) Bug with pattern restriction on long strings

Updated: (XERCESJ-589) Bug with pattern restriction on long strings

2005-03-18       - By Andy O'Brien (JIRA)
Reply:     1     2     3     4  

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

Andy O'Brien updated XERCESJ-589:
---------------------------------

   Attachment: test.zip

I'm also getting StackOverflow exceptions for this issue.  I'm using Xerces 2.6
.2, Java 1.3.1_06

Here's my element definition, where large values cause stack problems:

<!-- Test digit tokens w/o beginning, trailing, or adjacent spaces -->

<xsd:element name="foo">
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
       <xsd:pattern value="([0-9] ?)*[0-9]" />
     </xsd:restriction>
  </xsd:simpleType>
</xsd:element>

With 10,000 digits for <foo> above, I get a StackOverflow:

Exception in thread "main" java.lang.StackOverflowError
       at org.apache.xerces.impl.xpath.regex.Op$UnionOp.elementAt(Unknown Sourc
e)
       at org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unkn
own Source)
       at org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unkn
own Source)
       . . . . . .

My attachment has a simple instance (10,000 digits for <foo> above) and its
schema.

A variable size causes exceptions.

Note that another very popular GUI XML tool has problems here too.  In their
case, they seem to limit the data to 1000 chars. (for <foo> above).  Maybe they
're avoiding stack issues with such a static value?

In another XML parser though, I get no stack overflow exceptions, nor am I
limited in size (at least I haven't seen a problem with it yet).

Sounds like this is still an issue.


> Bug with pattern restriction on long strings
> --------------------------------------------
>
>          Key: XERCESJ-589
>          URL: http://issues.apache.org/jira/browse/XERCESJ-589
>      Project: Xerces2-J
>         Type: Bug
>   Components: XML Schema Structures
>     Versions: 2.3.0
>  Environment: Operating System: All
> Platform: All
>     Reporter: Mark Woon
>     Assignee: Xerces-J Developers Mailing List
>  Attachments: test.xml, test.xsd, test.zip
>
> There is a bug with applying a pattern restriction on long strings while
trying
> to validate an XML file against a schema.  I'm including an xml file and xsd
> file that demonstrates this problem.  One character less in <sequence> and the
> problem does not occur.
> As it is, I'm getting
> java.lang.StackOverflowError
>         at
> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
Source)
>         at
> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
Source)
>         at
> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
Source)
>         at
> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
Source)
>         at
> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
Source)
>         at
> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
Source)
>         at
> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
Source)
>         at
> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
Source)
>         at
> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
Source)
>         at
> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
Source)
>         at
> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
Source)
>         at
> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
Source)
>         at
> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
Source)
>         at
> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
Source)
>         at
> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
Source)
>         at
> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
Source)
>         at
> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
Source)
> ...

--
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
-
If you want more information on JIRA, or have a bug to report see:
  http://www.atlassian.com/software/jira


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