Hi Mukul,
Thank you for looking into this and responding so quickly. We'll go back to
enabling assertions as we run tests on the XSD 1.1 processor to see if we spot
any new issues. We'll make sure to turn JDK assertions off when we hit
production :-)
Thanks,
-jOrGe W.
On Feb 18, 2012, at 8
On Sun, Feb 19, 2012 at 7:30 AM, Mukul Gandhi wrote:
> org.eclipse.wst.xml.xpath2.processor.internal.types.QName.namespace.QName.java
my apologies for wrong typing.
the file corrected was,
org.eclipse.wst.xml.xpath2.processor.internal.types.QName.java (the
method was namespace()).
--
Regard
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, tha
Hi Jorge,
Kindly read few answers below please,
On Sat, Feb 11, 2012 at 11:01 PM, Jorge Williams
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 $CLASS
