Hi Jorge, The below problem has now been fixed into Xerces SVN (commit revision, 1290922).
The offending "JDK assertion" in this file, org.eclipse.wst.xml.xpath2.processor.internal.types.QName.namespace.QName.java in PsychoPath XPath engine was removed to solve this issue. I do recognize, that it's a legitimate use-case to enable "JDK assertions" and then run Xerces XSD 1.1 processor. Other than this fix, if users do encounter such errors at any other code paths in PsychoPath engine, then users would have to report such cases on the list or in a bug report, and we'll have to solve (or keep unsolved if there's failure risk in other parts of PsychoPath XPath engine) each such report on a case by case basis. On Sat, Feb 11, 2012 at 11:01 PM, Jorge Williams <jorge.willi...@rackspace.com> wrote: > If I do: > > java -cp $CLASSPATH jaxp.SourceValidator -fx -xsd11 -a simple.xsd -i > simple.xml > > things validate correctly. However if I enable assertion checks > > java -ea -cp $CLASSPATH jaxp.SourceValidator -fx -xsd11 -a simple.xsd -i > simple.xml > > I get the following: > > Exception in thread "main" java.lang.AssertionError > at > org.eclipse.wst.xml.xpath2.processor.internal.types.QName.namespace(QName.java:236) > at > org.eclipse.wst.xml.xpath2.processor.DefaultEvaluator.name_test(DefaultEvaluator.java:1407) -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org For additional commands, e-mail: j-users-h...@xerces.apache.org
