[jira] [Updated] (XMLBEANS-495) StackOverflowError when parsing a large number of characters in an XML element

2012-12-10 Thread Mandy Warren (JIRA)

 [ 
https://issues.apache.org/jira/browse/XMLBEANS-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mandy Warren updated XMLBEANS-495:
--

Description: 
When XMLBeans validates a very long XML String (4000 or so chars), it generates 
a StackOverFlowError as shown below. In the schema for this element I have 
defined a pattern and a min/max length but XMLBeans is applying the pattern 
first before checking the length. The solution is the fix applied to the class 
RegularExpression in xerces - see 
https://issues.apache.org/jira/browse/XERCESJ-589 which went into version 2.11. 

xs:simpleType name=info
xs:restriction base=xs:string
xs:maxLength value=3/
xs:minLength value=2/
xs:pattern value=[A-Z0-9]+/
/xs:restriction
/xs:simpleType


Exception in thread main java.lang.StackOverflowError
at 
org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1662)
at 
org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)
at 
org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)
at 
org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)
at 
org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)
at 
org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)

  was:
When XMLBeans validates a very long XML String (1000 or more chars), it 
generates a StackOverFlowException as shown below. In the schema for this 
element I have defined a pattern and a min/max length but XMLBeans is applying 
the pattern first before checking the length. The solution is the fix applied 
to the class RegularExpression in xerces - see 
https://issues.apache.org/jira/browse/XERCESJ-589 which went into version 2.11. 

xs:simpleType name=info
xs:restriction base=xs:string
xs:maxLength value=3/
xs:minLength value=2/
xs:pattern value=[A-Z0-9]+/
/xs:restriction
/xs:simpleType


Exception in thread main java.lang.StackOverflowError
at 
org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1662)
at 
org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)
at 
org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)
at 
org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)
at 
org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)
at 
org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)


 StackOverflowError when parsing a large number of characters in an XML element
 --

 Key: XMLBEANS-495
 URL: https://issues.apache.org/jira/browse/XMLBEANS-495
 Project: XMLBeans
  Issue Type: Bug
  Components: Validator
Affects Versions: Version 2.6
 Environment: All
Reporter: Mandy Warren

 When XMLBeans validates a very long XML String (4000 or so chars), it 
 generates a StackOverFlowError as shown below. In the schema for this element 
 I have defined a pattern and a min/max length but XMLBeans is applying the 
 pattern first before checking the length. The solution is the fix applied to 
 the class RegularExpression in xerces - see 
 https://issues.apache.org/jira/browse/XERCESJ-589 which went into version 
 2.11. 
   xs:simpleType name=info
   xs:restriction base=xs:string
   xs:maxLength value=3/
   xs:minLength value=2/
   xs:pattern value=[A-Z0-9]+/
   /xs:restriction
   /xs:simpleType
 Exception in thread main java.lang.StackOverflowError
   at 
 org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1662)
   at 
 org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)
   at 
 org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)
   at 
 org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)
   at 
 org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)
   at 
 org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: 

Re: Single xsdconfig for multiple XML schema

2012-12-10 Thread Chun Tat David Chu
Yea, the problem I have seems like the scomp tool is not recognizing my
xsdconfig.  Is there a way to verify that it is indeed reading it?

On Sun, Dec 9, 2012 at 4:35 PM, Jacob Danner jacob.dan...@gmail.com wrote:

 It's been a while since I've done anything with xsdconfig's but I think
 adding a dirname/*.xsdconfig should be enough to include it during
 compilation.
 HTH,
 -jacobd
 On Dec 9, 2012 10:09 AM, Chun Tat David Chu beyonddc.stor...@gmail.com
 wrote:

 Hi All,

 I am new to XMLBeans.  I would like to append a prefix to all the
 generated JAVA bindings.  I am generating bindings for about 25 XML schema,
 and they are:
 apache-definitions-schema.xsd

 apache-system-characteristics-schema.xsd
 freebsd-definitions-schema.xsd
 freebsd-system-characteristics-schema.xsd
 ... (I am not listing all here, but these XML schema are obtained from
 http://oval.mitre.org/language/version5.3/index.html)

 I specified a xsdconfig named oval53.xsdconfig and placed within the same
 directory where the rest of the schema are located.  I use the following
 arguments when running with scomp.  I don't believe scomp takes any special
 argument to specify the location of the xsdconfig.
 scomp -src ${BINDING_DIR} \
   -srconly \
   -verbose \
   ${OVAL53_XML_SCHEMA_DIR}/*.xsd

 My problem is it seems like scomp didn't read in my xsdconfig because
 none of the generated bindings are using the prefix that I specified.  I
 believe I have the XML syntax set correctly (see attachment for the whole
 xsdconfig).
 xb:namespace uriprefix=
 http://oval.mitre.org/XMLSchema/oval-definitions-5#windows;
 xb:prefixxmlbeans_oval53/xb:prefix
 /xb:namespace
 xb:namespace uriprefix=
 http://oval.mitre.org/XMLSchema/oval-system-characteristics-5#windows;
 xb:prefixxmlbeans_oval53/xb:prefix
 /xb:namespace

 Can someone please point me what is my problem?

 Thanks in advance!

 David


 -
 To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
 For additional commands, e-mail: dev-h...@xmlbeans.apache.org




Re: Single xsdconfig for multiple XML schema

2012-12-10 Thread Jacob Danner
Why not try a simple package rename like noted in
http://wiki.apache.org/xmlbeans/XmlBeansFaq#configPackageName
of course, replace with your package name as appropriate

You can use that to verify the xsdconfig is getting processed and
begin tinkering from there.
-jacobd

On Mon, Dec 10, 2012 at 7:23 AM, Chun Tat David Chu
beyonddc.stor...@gmail.com wrote:
 Yea, the problem I have seems like the scomp tool is not recognizing my
 xsdconfig.  Is there a way to verify that it is indeed reading it?

 On Sun, Dec 9, 2012 at 4:35 PM, Jacob Danner jacob.dan...@gmail.com wrote:

 It's been a while since I've done anything with xsdconfig's but I think
 adding a dirname/*.xsdconfig should be enough to include it during
 compilation.
 HTH,
 -jacobd

 On Dec 9, 2012 10:09 AM, Chun Tat David Chu beyonddc.stor...@gmail.com
 wrote:

 Hi All,

 I am new to XMLBeans.  I would like to append a prefix to all the
 generated JAVA bindings.  I am generating bindings for about 25 XML schema,
 and they are:
 apache-definitions-schema.xsd

 apache-system-characteristics-schema.xsd
 freebsd-definitions-schema.xsd
 freebsd-system-characteristics-schema.xsd
 ... (I am not listing all here, but these XML schema are obtained from
 http://oval.mitre.org/language/version5.3/index.html)

 I specified a xsdconfig named oval53.xsdconfig and placed within the same
 directory where the rest of the schema are located.  I use the following
 arguments when running with scomp.  I don't believe scomp takes any special
 argument to specify the location of the xsdconfig.
 scomp -src ${BINDING_DIR} \
   -srconly \
   -verbose \
   ${OVAL53_XML_SCHEMA_DIR}/*.xsd

 My problem is it seems like scomp didn't read in my xsdconfig because
 none of the generated bindings are using the prefix that I specified.  I
 believe I have the XML syntax set correctly (see attachment for the whole
 xsdconfig).
 xb:namespace
 uriprefix=http://oval.mitre.org/XMLSchema/oval-definitions-5#windows;
 xb:prefixxmlbeans_oval53/xb:prefix
 /xb:namespace
 xb:namespace
 uriprefix=http://oval.mitre.org/XMLSchema/oval-system-characteristics-5#windows;
 xb:prefixxmlbeans_oval53/xb:prefix
 /xb:namespace

 Can someone please point me what is my problem?

 Thanks in advance!

 David


 -
 To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
 For additional commands, e-mail: dev-h...@xmlbeans.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
For additional commands, e-mail: dev-h...@xmlbeans.apache.org



[GUMP@vmgump]: Project xml-xmlbeans-v1 (in module xml-xmlbeans) failed

2012-12-10 Thread Robert Burrell Donkin
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at gene...@gump.apache.org.

Project xml-xmlbeans-v1 has an issue affecting its community integration.
This issue affects 4 projects,
 and has been outstanding for 241 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jmeter-svn :  Pure Java load testing and performance measurement tool.
   ...
- jmeter-test :  Pure Java load testing and performance measurement tool.
   ...
- rhino :  JavaScript for Java
- xml-xmlbeans-v1 :  XML Beans Object - Java Binding Tool


Full details are available at:
http://vmgump.apache.org/gump/public/xml-xmlbeans/xml-xmlbeans-v1/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/xml-xmlbeans/xml-xmlbeans-v1/gump_work/build_xml-xmlbeans_xml-xmlbeans-v1.html
Work Name: build_xml-xmlbeans_xml-xmlbeans-v1 (Type: Build)
Work ended in a state of : Failed
Elapsed: 1 min 34 secs
Command Line: /usr/lib/jvm/java-7-oracle/bin/java -Djava.awt.headless=true 
-Dbuild.sysclasspath=only 
-Xbootclasspath/p:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar
 org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -f 
build.xml bootstrap 
[Working Directory: /srv/gump/public/workspace/xml-xmlbeans]
CLASSPATH: 
/usr/lib/jvm/java-7-oracle/lib/tools.jar:/srv/gump/public/workspace/xml-xmlbeans/build/classes/common:/srv/gump/public/workspace/xml-xmlbeans/build/classes/xmlinputstream:/srv/gump/public/workspace/xml-xmlbeans/build/classes/xmlpublic:/srv/gump/public/workspace/xml-xmlbeans/external/lib/oldxbean.jar:/srv/gump/public/workspace/xml-xmlbeans/build/private/classes/zipcompare:/srv/gump/public/workspace/xml-xmlbeans/build/private/lib/easypo.jar:/srv/gump/public/workspace/xml-xmlbeans/build/private/lib/schemas.jar:/srv/gump/public/workspace/xml-xmlbeans/build/private/lib/enumtest.jar:/srv/gump/public/workspace/xml-xmlbeans/build/private/lib/drt.jar:/srv/gump/public/workspace/xml-xmlbeans/build/private/lib/xstypes.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swin
 
g.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/srv/gump/packages/jaxen-1.1-beta-6/jaxen-1.1-beta-6.jar:/srv/gump/public/workspace/junit/dist/junit-11122012.jar:/srv/gump/public/workspace/junit/dist/junit-dep-11122012.jar
-
[javac] Note: Recompile with -Xlint:unchecked for details.
 [java] Comparing build/ar/xbean.jar with build/private/lib/oldxbean.jar:
 [java] schema/system/sXMLCONFIG/configf467elemtype.xsb does not match
 [java] schema/system/sXMLCONFIG/nsconfigaebatype.xsb does not match
 [java] schema/system/sXMLTOOLS/definitions05ddelemtype.xsb does not match
 [java] schema/system/sXMLTOOLS/testcase9599type.xsb does not match
 [java] schema/system/sXMLSCHEMA/all3c04type.xsb does not match
 [java] schema/system/sXMLSCHEMA/all82daelemtype.xsb does not match
 [java] schema/system/sXMLSCHEMA/annotation5abfelemtype.xsb does not match
 [java] schema/system/sXMLSCHEMA/attribute83a9type.xsb does not match
 [java] schema/system/sXMLSCHEMA/attributegroupe530type.xsb does not match
 [java] schema/system/sXMLSCHEMA/complexcontentaa7felemtype.xsb does not 
match
 [java] schema/system/sXMLSCHEMA/complexrestrictiontype1b7dtype.xsb does 
not match
 [java] schema/system/sXMLSCHEMA/complextype5dbbtype.xsb does not match
 [java] schema/system/sXMLSCHEMA/elementd189type.xsb does not match
 [java] schema/system/sXMLSCHEMA/elementinall3f33type.xsb does not match
 [java] schema/system/sXMLSCHEMA/explicitgroup4efatype.xsb does not match
 [java] schema/system/sXMLSCHEMA/extensiontypeed4ctype.xsb does not match
 [java] schema/system/sXMLSCHEMA/group7ca6type.xsb does not match
 [java] schema/system/sXMLSCHEMA/keybase3955type.xsb does not match
 [java] schema/system/sXMLSCHEMA/keyref7a1felemtype.xsb does not match
 [java] schema/system/sXMLSCHEMA/list391felemtype.xsb does not match
 [java]