I'm attaching a small example:
Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
individual or entity to which this message is addressed, and unless otherwise
expressly indicated, is confidential
Hi all,
I've been playing around with the latest XSD 1.1 branch and ran into the
following. I'm attaching a schema and instance document as a reference.
The first error deals with an assertion going off somewhere out in the XPath 2
implementation.
If I do:
java -cp $CLASSPATH jaxp.SourceV
e 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.
>
>
The following seems to fix:
diff --git a/samples/xs/XSSerializer.java b/samples/xs/XSSerializer.java
index 400d28b..bdf1b6b 100644
--- a/samples/xs/XSSerializer.java
+++ b/samples/xs/XSSerializer.java
@@ -39,7 +39,7 @@ import org.apache.xerces.impl.xs.identity.Field;
import org.apache.xerces.impl
Hi all,
I've been playing around with the latest XSD 1.1 branch and ran into the
following. I'm attaching a schema and instance documents as a reference.
If I do
java -cp $CLASSPATH jaxp.SourceValidator -fx -xsd11 -a usage.xsd -i sample.xml
or
java -cp $CLASSPATH jaxp.SourceValidator -f
Just got around to testing it. Looks good.
Thanks,
-jOrGe W.
On Mar 23, 2012, at 3:02 AM, Mukul Gandhi wrote:
> Hi Jorge,
> It seems you've found a NPE bug. It's now fixed in SVN.
>
> Could you please verify the fix.
>
> On Thu, Mar 22, 2012 at 2:58
te:
>
>> Hi Jorge,
>> It seems you've found a NPE bug. It's now fixed in SVN.
>>
>> Could you please verify the fix.
>>
>> On Thu, Mar 22, 2012 at 2:58 PM, Jorge Williams
>> wrote:
>>>
>>> Hi all,
>>>
&
Looks good.
Thank you,
jOrGe W.
On Mar 31, 2012, at 7:24 AM, Mukul Gandhi wrote:
> Hi Jorge,
> Thanks very much for reporting this error.
>
> This has now been fixed in SVN. You may verify the fix.
>
> On Mon, Mar 26, 2012 at 7:47 PM, Jorge Williams
> wro
Hello again, found another potential bug:
In the latest XSD 1.1 branch, it looks like simple type assertions are not
being enforced when the type is specified via the xsi:type attribute. I'm
attaching a schema and instance documents as a reference.
If I do
java -cp $CLASSPATH jaxp.SourceVa
hmm..attachments didn't seem to go through?
On Apr 2, 2012, at 4:38 PM, Jorge Williams wrote:
Hello again, found another potential bug:
In the latest XSD 1.1 branch, it looks like simple type assertions are not
being enforced when the type is specified via the xsi:type attribute.
nteger" via xsi:type)
>
> I therefore do not think, that xs:assertion within xs:simpleType works
> incorrectly, when such a type is selected via xsi:type from an XML
> instance document.
>
> I'm currently not sure, whether the observation you've shared may be a
> po
Hey Guys,
I'm working off of the latest 1.1 branch. I have the following schema:
http://www.w3.org/2001/XMLSchema";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:tst="http://www.rackspace.com/test/simple";
targetNamespace="http://www.rackspace.com/test/simple";>
On May 17, 2012, at 2:56 PM, Mukul Gandhi wrote:
> Hi Jorge,
> With my quick analysis of your use-case, I can conclude that this
> may be a possible bug (and quite likely in our XSD 1.1 XPath2 engine).
>
> As a workaround, I can find the following expression to be working
> correctly though,
>
feel free to report, if you find anything still incorrect.
>
>
> On Fri, May 18, 2012 at 5:06 AM, Jorge Williams
> wrote:
>>
>> On May 17, 2012, at 2:56 PM, Mukul Gandhi wrote:
>>
>>> Hi Jorge,
>>> With my quick analysis of your use-case, I can co
, we don't need to explicitly
> cast them during XPath expression evaluation.
>
>
> On Tue, May 22, 2012 at 11:30 PM, Jorge Williams
> wrote:
>> Hi Mukul,
>>
>> Just updated. Unfortunately, I'm still getting the same error with the
>> same examp
On May 24, 2012, at 3:45 PM, Mukul Gandhi wrote:
Thanks, Jorge for bringing these issues to the list :)
No problem. Thanks for addressing these issues so quickly!
-jOrGe W.
Hey Guys,
Seems like the last couple of bugs relate to the XPath 2 engine specifically.
If PsycoPath claims full conformance, then the deficiencies are really in the
XPath 2 test suite.
-jOrGe W.
On May 24, 2012, at 4:10 PM, Mukul Gandhi wrote:
> Hi Michael,
>I believe, the W3C's XML Sc
There is a case where handling the cast correctly is critically important:
when you are dealing with an implementation where nodes are not typed. In this
case, you *always* have to do a cast to inform the validator of the type of a
particular value. The Saxon implementation works this way, a
(Inline)
On Jun 15, 2012, at 1:08 AM, Mukul Gandhi wrote:
> Hi Jorge,
>
> On Thu, Jun 14, 2012 at 5:44 PM, Jorge Williams
> wrote:
>
>> I couldn't find anything in the standard that says that implementation must
>> have typed nodes
>
> The XSD 1.1 asse
Just got around to testing. Works!
Thank you,
-jOrGe W
On Jun 16, 2012, at 3:37 AM, Mukul Gandhi wrote:
> Hi Jorge,
> The fixes for this issue are now available on SVN (revision,
> 1350884). You may verify as appropriate.
>
> On Fri, Jun 15, 2012 at 4:56 PM, Jorge Wi
Hey Guys,
Can you give me a hand. I'm getting a weird error that I cannot replicate with
jaxp.SourceValidator so I know I must be doing something wrong, but I can't
tell what.
My code looks like this:
package com.rackspace.xerces;
import javax.xml.validation.*;
import javax.xml.transform.str
nd define a suitable error handler as following,
>
> class ErrHandler implements ErrorHandler {
>...
> }
>
> On Fri, Jun 22, 2012 at 12:48 AM, Jorge Williams
> wrote:
>> Hey Guys,
>>
>> Can you give me a hand. I'm getting a weird error that I cannot rep
Hey guys,
I'm on the latest xml-schema-1.1-dev branch in SVN. Trying to compile with
./build.sh clean jars-schema11
I'm getting all sorts of errors:
compile-schema11:
[copy] Copying 23 files to /Users/jorgew/projects/xercesj/build/classes
[xjavac] Compiling 776 source files to
/Users/
Ah looks, like I need to just do
./build.sh clean jars
right?
On Mar 4, 2013, at 3:30 PM, Jorge Williams wrote:
> Hey guys,
>
> I'm on the latest xml-schema-1.1-dev branch in SVN. Trying to compile with
>
> ./build.sh clean jars-schema11
>
> I'm getting al
Hey Guys,
If we are planning a release of Xerces, may I suggest that we also update
version of PsycoPath that Xerces is currently using. The current version of the
XPath 2 implementation reports over 800 failures in the W3C test suite. Sam
Harwell has been able to reduce this number to about
pecification.
On 24 June 2016 at 02:49, Jorge Williams
mailto:jorge.willi...@rackspace.com>> wrote:
Hey Guys,
If we are planning a release of Xerces, may I suggest that we also update
version of PsycoPath that Xerces is currently using. The current version of the
XPath 2 implementation r
erested in reviewing Sam's fork directly and then merging from
there?
Thanks,
-jOrGe W.
From: Mukul Gandhi
Sent: Tuesday, June 28, 2016 12:15 AM
To: Jorge Williams
Cc: j-users@xerces.apache.org; s...@tunnelvisionlabs.com; Michael Glavassevich
Subject: Re
27 matches
Mail list logo
