Re: [GUMP@vmgump]: Project xml-xmlbeans-v1 (in module xml-xmlbeans) failed
FIG/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/downloadedschemaentry5f6ftype.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/list391felemtype.xsb does not match [java] schema/system/sXMLSCHEMA/localcomplextype6494type.xsb does not match [java] schema/system/sXMLSCHEMA/localelement2ce2type.xsb does not match [java] schema/system/sXMLSCHEMA/localsimpletype410etype.xsb does not match [java] schema/system/sXMLSCHEMA/namedattributegroup2e29type.xsb does not match [java] schema/system/sXMLSCHEMA/namedgroup878dtype.xsb does not match [java] schema/system/sXMLSCHEMA/realgroup1f64type.xsb does not match [java] schema/system/sXMLSCHEMA/redefine9e9felemtype.xsb does not match [java] schema/system/sXMLSCHEMA/restrictionad11elemtype.xsb does not match [java] schema/system/sXMLSCHEMA/restrictiontype939ftype.xsb does not match [java] schema/system/sXMLSCHEMA/schemad77felemtype.xsb does not match [java] schema/system/sXMLSCHEMA/simplecontent9a5belemtype.xsb does not match [java] schema/system/sXMLSCHEMA/simpleexplicitgroup428ctype.xsb does not match [java] schema/system/sXMLSCHEMA/simpleextensiontypee0detype.xsb does not match [java] schema/system/sXMLSCHEMA/simplerestrictiontypeeab1type.xsb does not match [java] schema/system/sXMLSCHEMA/simpletype0707type.xsb does not match [java] schema/system/sXMLSCHEMA/toplevelattributeb338type.xsb does not match [java] schema/system/sXMLSCHEMA/toplevelcomplextypee58atype.xsb does not match [java] schema/system/sXMLSCHEMA/toplevelelement98d8type.xsb does not match [java] schema/system/sXMLSCHEMA/toplevelsimpletypec958type.xsb does not match [java] schema/system/sXMLSCHEMA/union498belemtype.xsb does not match [java] 1749 entries matched [java] 36 entries did not match BUILD FAILED /srv/gump/public/workspace/xml-xmlbeans/build.xml:298: The following error occurred while executing this line: /srv/gump/public/workspace/xml-xmlbeans/build.xml:316: Java returned: 1 Total time: 1 minute 31 seconds - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/xml-xmlbeans/xml-xmlbeans-v1/rss.xml - Atom: http://vmgump.apache.org/gump/public/xml-xmlbeans/xml-xmlbeans-v1/atom.xml == Gump Tracking Only === Produced by Apache Gump(TM) version 2.3. Gump Run 1721092012, vmgump.apache.org:vmgump:1721092012 Gump E-mail Identifier (unique within run) #4. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] - 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 -- Peter Keller Tel.: +44 (0)1223 353033 Global Phasing Ltd., Fax.: +44 (0)1223 366889 Sheraton House, Castle Park, Cambridge CB3 0AX United Kingdom - To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org For additional commands, e-mail: dev-h...@xmlbeans.apache.org
Re: gump failure
On Thu, 2012-08-02 at 11:47 -0700, Cezar Andrei wrote: > Bootstrap works the first time also for me. But I've put in your patch > to run bootstrap twice. Let's see if it fixes Gump. Grrr obviously not :-( I have no more technical suggestions, and it seems to me that it may be something in the gump environment itself that is the problem. According to this page: <http://vmgump.apache.org/gump/public/xml-xmlbeans/xml-xmlbeans-v1/gump_work/build_xml-xmlbeans_xml-xmlbeans-v1.html> the command that is used to do the build is: /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 The "gump.merge" system property suggests to me that there is something non-standard going on. Maybe some sort of state from previous builds is being brought forward and having an effect on the current build. My next suggestion would be to contact Robert Donkin (after everything to do with the 2.6.0 release has been sorted out), and ask him how to reproduce the problem outside the gump environment. Anyone could do this in principle, but maybe it would be better coming from an XMLBeans committer? Regards, Peter. > > Cezar > > On Wed, 2012-08-01 at 03:33 -0700, Peter Keller wrote: > > Still getting these gump messages Is a committer able to apply the > > patch to build.xml on the 1.x branch as I suggested? > > > > I have tried to reproduce the error on an svn checkout of branch/1.x and > > a standard ant invocation of "ant bootstrap", but that works for me with > > just one pass. I guess that the gump failure must be due to some > > character set issue in the gump environment and/or the build of the > > tools that gump is using. > > > > Anyway, doing two bootstrap passes should fix it (or if it doesn't, > > enable us to ask the person who put xmlbeans on gump for help in > > reproducing the error). > > > > Regards, > > Peter. > > > > On Wed, 2012-07-25 at 17:31 +0100, Peter Keller wrote: > > > According to the information at the bottom of this page: > > > > > > <http://vmgump.apache.org/gump/public/xml-xmlbeans/index.html> > > > > > > gump is getting xmlbeans from > > > <http://svn.apache.org/repos/asf/xmlbeans/branches/1.x>. Looking at > > > build.xml at that location, the fix hasn't been applied there. > > > > > > Hope that helps, > > > Peter. > > > > > > P.S. If that doesn't fix it, I would suggest e-mailing Robert Donkin > > > directly for help. > > > > > > On Wed, 2012-07-25 at 09:21 -0700, Cezar Andrei wrote: > > > > It seems that Peter's fix is not picked up, anyone has any idea on how > > > > to make this happen? > > > > > > > > Cezar > > > > > > > > > > > > On Jul 20, 2012, at 12:00 PM, Cezar Andrei wrote: > > > > > > > > > Thank you Peter, I added your suggestion fix. It's not the perfect > > > > > solution but given the circumstances should be fine. > > > > > I'm sorry I forgot to mention your name on the checkin description > > > > > (rev 1363870) since it's your contribution. > > > > > > > > > > Cezar > > > > > > > > > > - Original Message - > > > > > From: pkel...@globalphasing.com > > > > > To: dev@xmlbeans.apache.org > > > > > Sent: Friday, July 20, 2012 5:51:41 AM GMT -06:00 US/Canada Central > > > > > Subject: Re: gump failure > > > > > > > > > > I'm not really an ant expert, but since I was looking at build.xml > > > > > anyway > > > > > > > > > > On Thu, 2012-07-19 at 12:03 -0700, Cezar Andrei wrote: > > > > >> About this email, this is not actually a failure. In order to > > > > >> consider > > > > >> it a failure, the bootstrap needs to run twice and only if it errors > > > > >> second time is it considered a failure. > > > > >> > > > > >> Is there any way to fix this test? > > > > > > > > > > The attached patch to build.xml fixes it in my hands (ant 1.8.2, > > > > > OpenJDK > > > > > 1.6.0.0_b24,
Re: [VOTE] XMLBeans v2.6.0-RC3 to become official release
+0 Regards, Peter. On Wed, 2012-08-08 at 17:33 -0700, Cezar Andrei wrote: > Because I didn't receive any votes, I'm extending the vote period until > end of next Monday, August 13. > > Cezar > > On Wed, 2012-08-08 at 17:07 -0700, Cezar Andrei wrote: > > The files are now up at http://xmlbeans.apache.org/dist/ please do send > > your votes. > > > > Thanks, > > Cezar > > > > On Thu, 2012-08-02 at 11:04 -0700, Cezar Andrei wrote: > > > The files are not here: http://xmlbeans.apache.org/dist/ yet, they > > > should get sync-ed soon. I'll send an update when they're up. > > > > > > In the meantime, you can find the same files here: > > > http://apache.org/~cezar/xmlbeans-2.6.0/ > > > > > > Cezar > > > > > > > > > On Thu, 2012-08-02 at 10:46 -0700, Cezar Andrei wrote: > > > > Please cast your vote for the XMLBeans v2.6.0-RC3, as published at > > > > http://xmlbeans.apache.org/dist/ to become XMLBeans v2.6.0 official > > > > release. > > > > > > > > > > > > > > > > The vote will be open until end of day Monday, August 6. Anyone is > > > > allowed to show support or lack of it, but only XMLBeans committer votes > > > > are binding. > > > > > > > > > > > > > > > > [ ] +1 - I am in favor of this release, and can help > > > > > > > > [ ] +0 - I am in favor of this release, but cannot help > > > > > > > > [ ] -0 - I am not in favor of this release > > > > > > > > [ ] -1 - I am against this proposal (must include a reason) > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > My vote is: > > > > > > > > [X] +1 - I am in favor of this release, and can help > > > > > > > > > > > > > > > > Cezar > > > > > > > > > > > > > > > > - > > > > 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 > > > > > > > > > > > - > > 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 > -- Peter Keller Tel.: +44 (0)1223 353033 Global Phasing Ltd., Fax.: +44 (0)1223 366889 Sheraton House, Castle Park, Cambridge CB3 0AX United Kingdom - To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org For additional commands, e-mail: dev-h...@xmlbeans.apache.org
Re: gump failure
That seems to have fixed it. XMLBeans has disappeared from the gump todo page at <http://vmgump.apache.org/gump/public/project_todos.html> (it was number three before). The build still fails because it needs junit (which is broken on gump), but someone else is getting nagged about that :-) Regards, Peter. On Wed, 2012-08-01 at 11:33 +0100, Peter Keller wrote: > Still getting these gump messages Is a committer able to apply the > patch to build.xml on the 1.x branch as I suggested? > > I have tried to reproduce the error on an svn checkout of branch/1.x and > a standard ant invocation of "ant bootstrap", but that works for me with > just one pass. I guess that the gump failure must be due to some > character set issue in the gump environment and/or the build of the > tools that gump is using. > > Anyway, doing two bootstrap passes should fix it (or if it doesn't, > enable us to ask the person who put xmlbeans on gump for help in > reproducing the error). > > Regards, > Peter. > > On Wed, 2012-07-25 at 17:31 +0100, Peter Keller wrote: > > According to the information at the bottom of this page: > > > > <http://vmgump.apache.org/gump/public/xml-xmlbeans/index.html> > > > > gump is getting xmlbeans from > > <http://svn.apache.org/repos/asf/xmlbeans/branches/1.x>. Looking at > > build.xml at that location, the fix hasn't been applied there. > > > > Hope that helps, > > Peter. > > > > P.S. If that doesn't fix it, I would suggest e-mailing Robert Donkin > > directly for help. > > > > On Wed, 2012-07-25 at 09:21 -0700, Cezar Andrei wrote: > > > It seems that Peter's fix is not picked up, anyone has any idea on how to > > > make this happen? > > > > > > Cezar > > > > > > > > > On Jul 20, 2012, at 12:00 PM, Cezar Andrei wrote: > > > > > > > Thank you Peter, I added your suggestion fix. It's not the perfect > > > > solution but given the circumstances should be fine. > > > > I'm sorry I forgot to mention your name on the checkin description (rev > > > > 1363870) since it's your contribution. > > > > > > > > Cezar > > > > > > > > - Original Message - > > > > From: pkel...@globalphasing.com > > > > To: dev@xmlbeans.apache.org > > > > Sent: Friday, July 20, 2012 5:51:41 AM GMT -06:00 US/Canada Central > > > > Subject: Re: gump failure > > > > > > > > I'm not really an ant expert, but since I was looking at build.xml > > > > anyway > > > > > > > > On Thu, 2012-07-19 at 12:03 -0700, Cezar Andrei wrote: > > > >> About this email, this is not actually a failure. In order to consider > > > >> it a failure, the bootstrap needs to run twice and only if it errors > > > >> second time is it considered a failure. > > > >> > > > >> Is there any way to fix this test? > > > > > > > > The attached patch to build.xml fixes it in my hands (ant 1.8.2, OpenJDK > > > > 1.6.0.0_b24, openSUSE 12.1). This patch is against version 2.6.0-RC2 > > > > (which shows the same failure when building bootstrap for the first time > > > > in a clean working directory), but to fix the gump failure, the same > > > > changes presumably need to be made against this version or a nearby one: > > > > > > > > <http://svn.apache.org/viewvc/xmlbeans/branches/1.x/build.xml?view=log> > > > > > > > >> I don't know how it got on gump. > > > > > > > > Presumably put there by someone involved with one of the dependent > > > > projects: jmeter, rhino or ws-axis2 (which has xml-xmlbeans-v1 as an > > > > optional dependency according to > > > > <http://vmgump.apache.org/gump/public/xml-xmlbeans/xml-xmlbeans-v1/details.html>). > > > > > > > > Regards, > > > > Peter. > > > > > > > >> > > > >> Thanks, > > > >> Cezar > > > >> > > > >> - Original Message - > > > >> From: rdon...@apache.org > > > >> To: xmlbeans-...@xml.apache.org > > > >> Sent: Thursday, July 19, 2012 1:55:19 AM GMT -06:00 US/Canada Central > > > >> Subject: [GUMP@vmgump]: Project xml-xmlbeans-v1 (in module > > > >> xml-xmlbeans) failed > > > >> > > > >> To whom it may engage... &g
Re: bootstrap build of xmlbeans from svn trunk checkout
OK - fair enough. It obviously doesn't interfere with the release of 2.6.0. After the release, I may look into this again. Regards, Peter. On Thu, 2 Aug 2012, Cezar Andrei wrote: Peter, Indeed resolver has been updated to 1.2. Thank you for the patch, but I can't check it in because it will make 7 tests fail. In order to do the update those tests need to be fixed. Inst2XsdCheckinTest.test_examples_cd_catalog Inst2XsdCheckinTest.test_examples_slashdotxml Inst2XsdCheckinTest.test_examples_rss2_vb_contentsmart_4enum Inst2XsdCheckinTest.test_examples_rss2_vb_contentstring_4enum Inst2XsdCheckinTest.test_examples_rss2_vb_contentstring Inst2XsdCheckinTest.test_examples_rss2 Inst2XsdCheckinTest.test_examples_rss091 Run ant checkintest to have a minimal number of tests pass. Cezar On Wed, 2012-08-01 at 03:34 -0700, Peter Keller wrote: I have found that a bootstrap build from an svn checkout of trunk fails because xml-commons-resolver in <http://www.apache.org/dist/xerces/xml-commons/binaries/> has been updated from 1.1 to 1.2. The attached patch to build.xml fixes this in my hands. Regards, Peter. - 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 -- Peter Keller Tel.: +44 (0)1223 353033 Global Phasing Ltd., Fax.: +44 (0)1223 366889 Sheraton House, Castle Park, Cambridge CB3 0AX United Kingdom - To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org For additional commands, e-mail: dev-h...@xmlbeans.apache.org
bootstrap build of xmlbeans from svn trunk checkout
I have found that a bootstrap build from an svn checkout of trunk fails because xml-commons-resolver in <http://www.apache.org/dist/xerces/xml-commons/binaries/> has been updated from 1.1 to 1.2. The attached patch to build.xml fixes this in my hands. Regards, Peter. -- Peter Keller Tel.: +44 (0)1223 353033 Global Phasing Ltd., Fax.: +44 (0)1223 366889 Sheraton House, Castle Park, Cambridge CB3 0AX United Kingdom --- build.xml 2012-08-01 11:02:57.587466431 +0100 +++ ../build.xml-trunk-patched 2012-08-01 10:58:04.449762854 +0100 @@ -170,7 +170,7 @@ http://www.apache.org/dist/xml/commons/binaries/xml-commons-resolver-1.1.zip"; +src="http://www.apache.org/dist/xml/commons/binaries/xml-commons-resolver-1.2.zip"; verbose="true" usetimestamp="true" ignoreerrors="true"/> @@ -186,8 +186,8 @@ - - + + - To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org For additional commands, e-mail: dev-h...@xmlbeans.apache.org
Re: gump failure
Still getting these gump messages Is a committer able to apply the patch to build.xml on the 1.x branch as I suggested? I have tried to reproduce the error on an svn checkout of branch/1.x and a standard ant invocation of "ant bootstrap", but that works for me with just one pass. I guess that the gump failure must be due to some character set issue in the gump environment and/or the build of the tools that gump is using. Anyway, doing two bootstrap passes should fix it (or if it doesn't, enable us to ask the person who put xmlbeans on gump for help in reproducing the error). Regards, Peter. On Wed, 2012-07-25 at 17:31 +0100, Peter Keller wrote: > According to the information at the bottom of this page: > > <http://vmgump.apache.org/gump/public/xml-xmlbeans/index.html> > > gump is getting xmlbeans from > <http://svn.apache.org/repos/asf/xmlbeans/branches/1.x>. Looking at > build.xml at that location, the fix hasn't been applied there. > > Hope that helps, > Peter. > > P.S. If that doesn't fix it, I would suggest e-mailing Robert Donkin > directly for help. > > On Wed, 2012-07-25 at 09:21 -0700, Cezar Andrei wrote: > > It seems that Peter's fix is not picked up, anyone has any idea on how to > > make this happen? > > > > Cezar > > > > > > On Jul 20, 2012, at 12:00 PM, Cezar Andrei wrote: > > > > > Thank you Peter, I added your suggestion fix. It's not the perfect > > > solution but given the circumstances should be fine. > > > I'm sorry I forgot to mention your name on the checkin description (rev > > > 1363870) since it's your contribution. > > > > > > Cezar > > > > > > - Original Message - > > > From: pkel...@globalphasing.com > > > To: dev@xmlbeans.apache.org > > > Sent: Friday, July 20, 2012 5:51:41 AM GMT -06:00 US/Canada Central > > > Subject: Re: gump failure > > > > > > I'm not really an ant expert, but since I was looking at build.xml > > > anyway > > > > > > On Thu, 2012-07-19 at 12:03 -0700, Cezar Andrei wrote: > > >> About this email, this is not actually a failure. In order to consider > > >> it a failure, the bootstrap needs to run twice and only if it errors > > >> second time is it considered a failure. > > >> > > >> Is there any way to fix this test? > > > > > > The attached patch to build.xml fixes it in my hands (ant 1.8.2, OpenJDK > > > 1.6.0.0_b24, openSUSE 12.1). This patch is against version 2.6.0-RC2 > > > (which shows the same failure when building bootstrap for the first time > > > in a clean working directory), but to fix the gump failure, the same > > > changes presumably need to be made against this version or a nearby one: > > > > > > <http://svn.apache.org/viewvc/xmlbeans/branches/1.x/build.xml?view=log> > > > > > >> I don't know how it got on gump. > > > > > > Presumably put there by someone involved with one of the dependent > > > projects: jmeter, rhino or ws-axis2 (which has xml-xmlbeans-v1 as an > > > optional dependency according to > > > <http://vmgump.apache.org/gump/public/xml-xmlbeans/xml-xmlbeans-v1/details.html>). > > > > > > Regards, > > > Peter. > > > > > >> > > >> Thanks, > > >> Cezar > > >> > > >> - Original Message - > > >> From: rdon...@apache.org > > >> To: xmlbeans-...@xml.apache.org > > >> Sent: Thursday, July 19, 2012 1:55:19 AM GMT -06:00 US/Canada Central > > >> Subject: [GUMP@vmgump]: Project xml-xmlbeans-v1 (in module xml-xmlbeans) > > >> failed > > >> > > >> To whom it may engage... > > > ... > > >> Full details are available at: > > >> > > >> http://vmgump.apache.org/gump/public/xml-xmlbeans/xml-xmlbeans-v1/index.html > > >> > > > > > > > > > - > > > 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 > > > -- Peter Keller Tel.: +44 (0)1223 353033 Global Phasing Ltd., Fax.: +44 (0)1223 366889 Sheraton House, Castle Park, Cambridge CB3 0AX United Kingdom - To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org For additional commands, e-mail: dev-h...@xmlbeans.apache.org
Re: [SPAM] relative paths possible bug?
Hi David,
I think that the problem is that you are using "\" characters in
schemaLocation. According to the XSD spec here:
<http://www.w3.org/TR/xmlschema-1/#element-import>
the value of schemaLocation in an import statement must be an anyURI.
anyURI must conform to a URI as defined in RFC3986:
<http://tools.ietf.org/html/rfc3986>
(this RFC obsoletes the older ones referred to in the XSD spec).
Careful reading of section 3.3 of this RFC shows that the path component
of a URI (in this case the whole string) must consist of zero or more
path segments separated by '/' characters. A path segment can contain
characters of the following types:
unreserved (i.e. ALPHA / DIGIT / "-" / "." / "_" / "~" )
%-encoded characters
sub-delims (i.e. "!" / "$" / "&" / "'" / "(" / ")"
/ "*" / "+" / "," / ";" / "=" )
":"
"@"
i.e. '\' characters are not allowed in URI's at all.
I am not familiar with using XMLBeans on Windows systems, but I would
suggest using '/' instead of '\', and relying on XMLBeans to interpret
the string as a filesystem path.
I suppose that using '%1c' instead of '\' and relying on Windows to
interpret the string as a filesystem path might work, but I wouldn't
recommend that.
Remember that even when a URI refers to a path on a local filesystem, it
is still using an abstraction of a path in which '/' is the path element
separator, not a physical path as implemented on particular operating
systems. It is the responsibility of whatever software interprets that
URI to convert it to path strings as required by the underlying
operating system.
Regards,
Peter.
On Tue, 2012-07-31 at 12:50 +0100, david garry wrote:
> Hi there,
>
>
>
> I wondering if I could ask the XMLBeans community about an issue I’ve
> encountered when parsing a schema (exchange-schema.xsd attached).
>
>
>
> When attempting to import the Schema I get the following error:
>
>
>
> “error: Could not find resource – invalid location URL”
>
> The problem is to do with the import of other namespaces. It looks
> like the schemaLocation value on the import statement is not correct.
> The schemaLocation value is a relative path value, e.g.
>
>
>
> namespace="http://doj.ca.gov/niem/SearchWrnt/Extension/1.0";
> schemaLocation="..\SearchWrnt\extension-schema.xsd"/>
>
> I understand that the problem is because the relative path used above
> should probably contain the prefix ‘file://’.
>
> I have followed the email thread between Jacob and another user which
> seems to be closely related.
>
> http://mail-archives.apache.org/mod_mbox/xmlbeans-user/200905.mbox/%
> 3cbb04eb0a0905121445k4c3c8ac1ve5ace62be01d9...@mail.gmail.com%3E
>
> I have followed the suggestions above without any success for a couple
> of days.
>
> In order to progress my issue, I checked-out the trunk
> (http://svn.apache.org/repos/asf/xmlbeans/trunk) and made the
> following code change on line 264 to
> org.apache.xmlbeans.impl.schema.StscImporter
>
> Old:
>
>
>
> URI childUri = new URI(child);
>
>
>
> New:
>
>
>
> URI childUri = null;
>
> try
>
> {
>
> childUri = new URL(base.toURL(),child).toURI();
>
> }
>
> catch(MalformedURLException e)
>
> {
>
> childUri = new URI(child);
>
> }
>
> This has resolved my issue.
>
> Would the XMlbeans community be able to tell me:
>
> 1) – Is the issue I encountered an actual problem that needs
> fixing?
>
> 2) – If so, can you inform of the code modification procedures so
> I may go ahead and make the fix assumming my change is deemed
> appropriate?
>
> 3) – If this is not a problem, can someone suggest ways I can
> resolve my issue. (I’m not permitted to modify the XML Schemas)
>
> Kind Regards
>
> David
>
>
>
> __
> David Garry
> Description: Description: Description: NOMOS-logo-email
> CTO, Nomos Software
> Direct Line: +353-21-4928945
> Mobile: +353-86-1980236
> Skype: david.garry3
> Description: Description: Description:
> cid:image002.gif@01CD6A46.64269EC0 Description: Description:
> Description: cid:image003.gif@01CD6A46.64269EC0
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
> For additional commands, e-mail: dev-h...@xmlbeans.apache.org
--
Peter Keller Tel.: +44 (0)1223 353033
Global Phasing Ltd., Fax.: +44 (0)1223 366889
Sheraton House,
Castle Park,
Cambridge CB3 0AX
United Kingdom
-
To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
For additional commands, e-mail: dev-h...@xmlbeans.apache.org
Re: gump failure
According to the information at the bottom of this page: <http://vmgump.apache.org/gump/public/xml-xmlbeans/index.html> gump is getting xmlbeans from <http://svn.apache.org/repos/asf/xmlbeans/branches/1.x>. Looking at build.xml at that location, the fix hasn't been applied there. Hope that helps, Peter. P.S. If that doesn't fix it, I would suggest e-mailing Robert Donkin directly for help. On Wed, 2012-07-25 at 09:21 -0700, Cezar Andrei wrote: > It seems that Peter's fix is not picked up, anyone has any idea on how to > make this happen? > > Cezar > > > On Jul 20, 2012, at 12:00 PM, Cezar Andrei wrote: > > > Thank you Peter, I added your suggestion fix. It's not the perfect solution > > but given the circumstances should be fine. > > I'm sorry I forgot to mention your name on the checkin description (rev > > 1363870) since it's your contribution. > > > > Cezar > > > > - Original Message - > > From: pkel...@globalphasing.com > > To: dev@xmlbeans.apache.org > > Sent: Friday, July 20, 2012 5:51:41 AM GMT -06:00 US/Canada Central > > Subject: Re: gump failure > > > > I'm not really an ant expert, but since I was looking at build.xml > > anyway > > > > On Thu, 2012-07-19 at 12:03 -0700, Cezar Andrei wrote: > >> About this email, this is not actually a failure. In order to consider > >> it a failure, the bootstrap needs to run twice and only if it errors > >> second time is it considered a failure. > >> > >> Is there any way to fix this test? > > > > The attached patch to build.xml fixes it in my hands (ant 1.8.2, OpenJDK > > 1.6.0.0_b24, openSUSE 12.1). This patch is against version 2.6.0-RC2 > > (which shows the same failure when building bootstrap for the first time > > in a clean working directory), but to fix the gump failure, the same > > changes presumably need to be made against this version or a nearby one: > > > > <http://svn.apache.org/viewvc/xmlbeans/branches/1.x/build.xml?view=log> > > > >> I don't know how it got on gump. > > > > Presumably put there by someone involved with one of the dependent > > projects: jmeter, rhino or ws-axis2 (which has xml-xmlbeans-v1 as an > > optional dependency according to > > <http://vmgump.apache.org/gump/public/xml-xmlbeans/xml-xmlbeans-v1/details.html>). > > > > Regards, > > Peter. > > > >> > >> Thanks, > >> Cezar > >> > >> - Original Message - > >> From: rdon...@apache.org > >> To: xmlbeans-...@xml.apache.org > >> Sent: Thursday, July 19, 2012 1:55:19 AM GMT -06:00 US/Canada Central > >> Subject: [GUMP@vmgump]: Project xml-xmlbeans-v1 (in module xml-xmlbeans) > >> failed > >> > >> To whom it may engage... > > ... > >> Full details are available at: > >> > >> http://vmgump.apache.org/gump/public/xml-xmlbeans/xml-xmlbeans-v1/index.html > >> > > > > > > - > > 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 > -- Peter Keller Tel.: +44 (0)1223 353033 Global Phasing Ltd., Fax.: +44 (0)1223 366889 Sheraton House, Castle Park, Cambridge CB3 0AX United Kingdom - To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org For additional commands, e-mail: dev-h...@xmlbeans.apache.org
Re: gump failure
- > > zipcompare.classes: > [mkdir] Created dir: > /srv/gump/public/workspace/xml-xmlbeans/build/private/classes/zipcompare > [javac] Compiling 1 source file to > /srv/gump/public/workspace/xml-xmlbeans/build/private/classes/zipcompare > [javac] Note: > /srv/gump/public/workspace/xml-xmlbeans/src/zipcompare/zipcompare/ZipCompare.java > uses unchecked or unsafe operations. > [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/extensionconfig2ac2type.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/downloadedschemaentry5f6ftype.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/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/localcomplextype6494type.xsb does not > match > [java] schema/system/sXMLSCHEMA/localelement2ce2type.xsb does not match > [java] schema/system/sXMLSCHEMA/localsimpletype410etype.xsb does not > match > [java] schema/system/sXMLSCHEMA/namedattributegroup2e29type.xsb does not > match > [java] schema/system/sXMLSCHEMA/namedgroup878dtype.xsb does not match > [java] schema/system/sXMLSCHEMA/realgroup1f64type.xsb does not match > [java] schema/system/sXMLSCHEMA/redefine9e9felemtype.xsb does not match > [java] schema/system/sXMLSCHEMA/restrictionad11elemtype.xsb does not > match > [java] schema/system/sXMLSCHEMA/restrictiontype939ftype.xsb does not > match > [java] schema/system/sXMLSCHEMA/schemad77felemtype.xsb does not match > [java] schema/system/sXMLSCHEMA/simplecontent9a5belemtype.xsb does not > match > [java] schema/system/sXMLSCHEMA/simpleexplicitgroup428ctype.xsb does not > match > [java] schema/system/sXMLSCHEMA/simpleextensiontypee0detype.xsb does not > match > [java] schema/system/sXMLSCHEMA/simplerestrictiontypeeab1type.xsb does > not match > [java] schema/system/sXMLSCHEMA/simpletype0707type.xsb does not match > [java] schema/system/sXMLSCHEMA/toplevelcomplextypee58atype.xsb does not > match > [java] schema/system/sXMLSCHEMA/toplevelelement98d8type.xsb does not > match > [java] schema/system/sXMLSCHEMA/toplevelsimpletypec958type.xsb does not > match > [java] 1749 entries matched > [java] 36 entries did not match > > BUILD FAILED > /srv/gump/public/workspace/xml-xmlbeans/build.xml:312: Java returned: 1 > > Total time: 1 minute 0 seconds > - > > To subscribe to this information via syndicated feeds: > - RSS: > http://vmgump.apache.org/gump/public/xml-xmlbeans/xml-xmlbeans-v1/rss.xml > - Atom: > http://vmgump.apache.org/gump/public/xml-xmlbeans/xml-xmlbeans-v1/atom.xml > > == Gump Tracking Only === > Produced by Apache Gump(TM) version 2.3. > Gump Run 06000619072012, vmgump.apache.org:vmgump:06000619072012 > Gump E-mail Identifier (unique within run) #5. > > -- > Apache Gump > http://gump.apache.org/ [Instance: vmgump] > > - > 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 > -- Peter Keller
Re: Which methods are meant to be supported by xmlpublic.jar?
One more observation: applying the attached patch to build.xml produces an xmlpublic.jar that satisfies the simple compilation of samples/Validation in my original message. I can also compile all my own code against it. This may not be the way you would want to actually fix the issue, but just for information Regards, Peter. On Thu, 2012-07-19 at 11:13 +0100, Peter Keller wrote: > On Wed, 2012-07-18 at 15:07 -0700, Cezar Andrei wrote: > > > I think you're right. Peter, do you know if > > org.apache.xmlbeans.xml.stream.* classes are the only ones required or > > do you have a list of missing classes? > > The contents of org.apache.xmlbeans.xml.stream are the only missing ones > that my own code needs, and I have not attempted to find any others. > Perhaps the best thing to do (so as not to hold up the release of 2.6.0 > too much) would be to add org.apache.xmlbeans.xml.stream into > xmlpublic.jar for the 2.6.0 release, now that we know it should be > there. A more comprehensive review of the contents of xmlpublic.jar > could be done for a future (2.6.1?) release. > > On a related note, if we are targetting jdk6, maybe we don't need > jsr173_1.0_api any longer? > > Regards, > Peter. > > > > > Cezar > > > > - Original Message - > > From: pkel...@globalphasing.com > > To: dev@xmlbeans.apache.org > > Sent: Friday, July 13, 2012 8:49:04 AM GMT -06:00 US/Canada Central > > Subject: Which methods are meant to be supported by xmlpublic.jar? > > > > Dear all, > > > > The announcement of 2.6.0-RC1 reminds me that I had meant to ask about > > something that I found in version 2.5.0, but still exists in 2.6.0-RC1, > > namely that xmlpublic.jar does not support at least some of the public > > XmlObject.Factory methods. Is this deliberate? Going by > > <http://wiki.apache.org/xmlbeans/XmlBeansFaq#whatJars> it seems to me that > > compiling code that uses these methods against xmlpublic.jar should succeed. > > > > For example, after building the XMLBeans distribution, the following > > commands: > > > >cd samples/Validation > >ant build > >javac -cp $XMLBEANS_HOME/build/lib/xmlpublic.jar:build/classes \ > > src/org/apache/xmlbeans/samples/validation/Validation.java > > > > output: > > > > src/org/apache/xmlbeans/samples/validation/Validation.java:178: cannot > > access org.apache.xmlbeans.xml.stream.XMLInputStream > > class file for org.apache.xmlbeans.xml.stream.XMLInputStream not found > > xml = XmlObject.Factory.parse(xmlFile, validationOptions); > > ^ > > 1 error > > > > Thanks for any comments/clarification. > > > > Regards, > > Peter. > > > -- Peter Keller Tel.: +44 (0)1223 353033 Global Phasing Ltd., Fax.: +44 (0)1223 366889 Sheraton House, Castle Park, Cambridge CB3 0AX United Kingdom --- build.xml.orig 2012-07-19 13:01:35.335096047 +0100 +++ build.xml 2012-07-19 13:07:34.118842995 +0100 @@ -541,11 +541,10 @@ - + - + - - To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org For additional commands, e-mail: dev-h...@xmlbeans.apache.org
Re: Which methods are meant to be supported by xmlpublic.jar?
On Wed, 2012-07-18 at 15:07 -0700, Cezar Andrei wrote: > I think you're right. Peter, do you know if > org.apache.xmlbeans.xml.stream.* classes are the only ones required or > do you have a list of missing classes? The contents of org.apache.xmlbeans.xml.stream are the only missing ones that my own code needs, and I have not attempted to find any others. Perhaps the best thing to do (so as not to hold up the release of 2.6.0 too much) would be to add org.apache.xmlbeans.xml.stream into xmlpublic.jar for the 2.6.0 release, now that we know it should be there. A more comprehensive review of the contents of xmlpublic.jar could be done for a future (2.6.1?) release. On a related note, if we are targetting jdk6, maybe we don't need jsr173_1.0_api any longer? Regards, Peter. > > Cezar > > - Original Message - > From: pkel...@globalphasing.com > To: dev@xmlbeans.apache.org > Sent: Friday, July 13, 2012 8:49:04 AM GMT -06:00 US/Canada Central > Subject: Which methods are meant to be supported by xmlpublic.jar? > > Dear all, > > The announcement of 2.6.0-RC1 reminds me that I had meant to ask about > something that I found in version 2.5.0, but still exists in 2.6.0-RC1, > namely that xmlpublic.jar does not support at least some of the public > XmlObject.Factory methods. Is this deliberate? Going by > <http://wiki.apache.org/xmlbeans/XmlBeansFaq#whatJars> it seems to me that > compiling code that uses these methods against xmlpublic.jar should succeed. > > For example, after building the XMLBeans distribution, the following > commands: > >cd samples/Validation >ant build >javac -cp $XMLBEANS_HOME/build/lib/xmlpublic.jar:build/classes \ > src/org/apache/xmlbeans/samples/validation/Validation.java > > output: > > src/org/apache/xmlbeans/samples/validation/Validation.java:178: cannot > access org.apache.xmlbeans.xml.stream.XMLInputStream > class file for org.apache.xmlbeans.xml.stream.XMLInputStream not found > xml = XmlObject.Factory.parse(xmlFile, validationOptions); > ^ > 1 error > > Thanks for any comments/clarification. > > Regards, > Peter. > -- Peter Keller Tel.: +44 (0)1223 353033 Global Phasing Ltd., Fax.: +44 (0)1223 366889 Sheraton House, Castle Park, Cambridge CB3 0AX United Kingdom - To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org For additional commands, e-mail: dev-h...@xmlbeans.apache.org
Which methods are meant to be supported by xmlpublic.jar?
Dear all, The announcement of 2.6.0-RC1 reminds me that I had meant to ask about something that I found in version 2.5.0, but still exists in 2.6.0-RC1, namely that xmlpublic.jar does not support at least some of the public XmlObject.Factory methods. Is this deliberate? Going by <http://wiki.apache.org/xmlbeans/XmlBeansFaq#whatJars> it seems to me that compiling code that uses these methods against xmlpublic.jar should succeed. For example, after building the XMLBeans distribution, the following commands: cd samples/Validation ant build javac -cp $XMLBEANS_HOME/build/lib/xmlpublic.jar:build/classes \ src/org/apache/xmlbeans/samples/validation/Validation.java output: src/org/apache/xmlbeans/samples/validation/Validation.java:178: cannot access org.apache.xmlbeans.xml.stream.XMLInputStream class file for org.apache.xmlbeans.xml.stream.XMLInputStream not found xml = XmlObject.Factory.parse(xmlFile, validationOptions); ^ 1 error Thanks for any comments/clarification. Regards, Peter. -- Peter Keller Tel.: +44 (0)1223 353033 Global Phasing Ltd., Fax.: +44 (0)1223 366889 Sheraton House, Castle Park, Cambridge CB3 0AX United Kingdom - To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org For additional commands, e-mail: dev-h...@xmlbeans.apache.org
Re: Reach out
Dear Cezar, On Wed, 2011-03-30 at 11:27 -0500, Cezar Andrei wrote: > Thanks for your suggestions Peter, they show very advanced usage of > XMLBeans and time spent on it to solve your problems. If you think your > changes are general and stable enough for others to make use of them > please send them to us by attaching the patch to JIRA. I obviously didn't explain myself very well. I have made no patches to XMLBeans itself: my three suggestions are merely descriptions of problems that I have encountered. My workarounds for problems (1) and (3) involve things like defining each interface multiple times in different ways, and carefully manipulating the classpath during schema compilation so that the different variants are picked up at different stages. I certainly cannot recommend any of this to other people. The only thing that makes it workable in my case is that most of the Java code and .xsdconfig files involved in this don't have to be maintained by hand because they are emitted by a code generation framework that I have written. If/when I find the time, I could prepare examples that illustrate the problems more specifically, but I'm afraid that at the present time I have no patches to contribute. Problem (2) is a bit different: there I have at least thought about patching XMLBeans itself. What I might do is write a patch for XMLBeans that reads the path to a compiler and its options from a configuration file (which will avoid the number of command-line options to scomp getting out of control). Given the context, that configuration file should be in XML format of course :-) Regards, Peter. > Cezar > > On Wed, 2011-03-23 at 11:55 +, Peter Keller wrote: > > On Tue, 22 Mar 2011, Cezar Andrei wrote: > > > > > I'm sending this email to reach out to people interested in XMLBeans, we > > > the active committers, were wondering if there is anybody actively using > > > XMLBeans that might be interested in adding new features, small fixes or > > > just have new ideas. > > > > > > We made a rough list with things we think they will be useful to have: > > > - add full support for generics, default to JDK 1.5 > > > - finish support for XMLSchema 1.1, many details around 1.1 built-in > > > schema types are already in > > > - better .xsdconfig, add support for different value serialization to > > > support bug XMLBEANS-451. > > > > > > Please don't be shy any response is appreciated, > > > > OK - here goes > > > > (1) Allow interface extensions to override inherited methods while > > specialising the return type (allowed in vanilla JDK 1.5, but getting this > > to work in XMLBeans needs some serious acrobatics). Probably part of the > > generics aspect, but please make sure that this doesn't get overlooked! > > > > (2) Full control of the options given to the Java compiler used internally > > by scomp. For example, I have had to work around the inability to give it > > the -bootclasspath option in various hacky ways. > > > > (3) When one interface extension depends on another, I have to use a > > complex > > multi-stage schema compilation with careful management of the .xsdconfig > > files to get everything to build. It would be fantastic to be able to do > > the > > whole compilation in a single step. > > > > I really appreciate this invitation to contribute ideas like this. I had > > intended to submit these ideas to JIRA, but I haven't found the time to > > prepare test cases. > > > > Regards, > > Peter. > > > > > > - > 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
Re: Reach out
On Tue, 22 Mar 2011, Cezar Andrei wrote: I'm sending this email to reach out to people interested in XMLBeans, we the active committers, were wondering if there is anybody actively using XMLBeans that might be interested in adding new features, small fixes or just have new ideas. We made a rough list with things we think they will be useful to have: - add full support for generics, default to JDK 1.5 - finish support for XMLSchema 1.1, many details around 1.1 built-in schema types are already in - better .xsdconfig, add support for different value serialization to support bug XMLBEANS-451. Please don't be shy any response is appreciated, OK - here goes (1) Allow interface extensions to override inherited methods while specialising the return type (allowed in vanilla JDK 1.5, but getting this to work in XMLBeans needs some serious acrobatics). Probably part of the generics aspect, but please make sure that this doesn't get overlooked! (2) Full control of the options given to the Java compiler used internally by scomp. For example, I have had to work around the inability to give it the -bootclasspath option in various hacky ways. (3) When one interface extension depends on another, I have to use a complex multi-stage schema compilation with careful management of the .xsdconfig files to get everything to build. It would be fantastic to be able to do the whole compilation in a single step. I really appreciate this invitation to contribute ideas like this. I had intended to submit these ideas to JIRA, but I haven't found the time to prepare test cases. Regards, Peter. -- Peter Keller Tel.: +44 (0)1223 353033 Global Phasing Ltd., Fax.: +44 (0)1223 366889 Sheraton House, Castle Park, Cambridge CB3 0AX United Kingdom - To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org For additional commands, e-mail: dev-h...@xmlbeans.apache.org
Controlling scomp's invocation of javac
Dear all, It seems to me that several annoying issues could be dealt with if there was a way to provide an arbitrary set of arguments to the invocation of 'javac' that is used by scomp to compile the generated Java source. Is anyone planing on doing anything along these lines? If not, I'm thinking of having a go myself, maybe sometime in July. What I had in mind was to modify org.apache.xmlbeans.impl.tool.CodeGenUtil.externalCompile so that it reads a properties-format file with arguments for javac, something like this: -sourcepath=/path/to/some/sourcefiles:/path/to/some/more/sourcefiles -bootclasspath=/path/to/some/rt.jar -g= and add these to the local 'args' variable before invoking javac. The path to this file could be provided by an option to SchemaCompiler. Obviously I would need to give some thought to the interaction with the current arguments to externalCompile. Does this sound a reasonable thing to do? I would give my changes back to the XMLBeans project of course. Regards, Peter. -- Peter Keller Tel.: +44 (0)1223 353033 Global Phasing Ltd., Fax.: +44 (0)1223 366889 Sheraton House, Castle Park, Cambridge CB3 0AX United Kingdom - To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org For additional commands, e-mail: dev-h...@xmlbeans.apache.org
[jira] Commented: (XMLBEANS-412) CLONE -Pattern facet regex requires dash - to be escaped
[
https://issues.apache.org/jira/browse/XMLBEANS-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12875549#action_12875549
]
Peter Keller commented on XMLBEANS-412:
---
For additional clarity (I hope):
A positive char group is:
posCharGroup ::= ( charRange | charClassEsc )+
and '\-' is a valid charClassEsc, so using '\-' is valid via the charClassEsc
branch. The following four positive character groups are all valid and
equivalent:
[A-F0-9.+-] ('-' is a valid charRange here)
[-A-F0-9.+] ('-' is a valid charRange here)
[A-F0-9.+\-] ('\-' is a valid charClassEsc)
[\-A-F0-9.+] ('\-' is a valid charClassEsc)
The following two negative character groups are valid and equivalent:
[^A-F0-9.+\-]('\-' is a valid charClassEsc)
[^\-A-F0-9.+]('\-' is a valid charClassEsc)
and the following two are invalid:
[^A-F0-9.+-]('-' is not a valid charRange here)
[^-A-F0-9.+]('-' is not a valid charRange here)
> CLONE -Pattern facet regex requires dash - to be escaped
>
>
> Key: XMLBEANS-412
> URL: https://issues.apache.org/jira/browse/XMLBEANS-412
> Project: XMLBeans
> Issue Type: Bug
> Components: Validator
>Affects Versions: Version 2, Version 2.1, Version 2.2, Version 2.2.1,
> Version 2.3, Version 2.3.1
> Environment: Win 2000, JDK1.5
>Reporter: Radosław Ceszkiel
> Fix For: Version 2
>
>
> Given the following xsd that should allow only a valid email address pattern:
> http://www.w3.org/2001/XMLSchema";>
>
>
>
>value="([\.a-zA-Z0-9_-])+@([a-zA-Z0-9_-])+(([a-zA-Z0-9_-])*\.([a-zA-Z0-9_-])+)+"/>
>
>
>
> Using the following simple xml instance:
> t...@test.com
> Running:
> validate sample.xsd sample.xml
> generates:
> Schema invalid:
> D:\sample.xsd:7: error: pattern-regex: The regular expression
> '([\.a-zA-Z0-9_-])+@([a-zA-Z0-9_-])+(([a-zA-Z0-9_-])*\.([a-zA-Z0-9_-])+)+' is
> malformed: '-' is an invalid character range. Write '\-'.
> A dash at the end or at the beginning of a character range does not have to
> be escaped (see
> http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#nt-charRange
> "The - character is a valid character range only at the beginning or end of
> a - positive character group- .")
> The regular expression in the email example is a valid xsd regexp and should
> be accepted by the XmlBeans validator.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
For additional commands, e-mail: dev-h...@xmlbeans.apache.org
