Yes, the problem is, however, that that change (while eliminating the
need for DOMSource wrappers which is a good thing) makes Saxon versions
< 8.7 not work anymore. My preference would be to upgrade to the latest
and greatest but at the same time I am a little frustrated about the
lack of backwards-compatibility on Saxon's part. Dan, do you have an
idea of the scope of changes from 8.7.3 to 8.8, it sounds like you are
in a situation in which 8.8 is required.
What do others think?

Radu

-----Original Message-----
From: Dan Kearns [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, November 01, 2006 2:42 PM
To: dev@xmlbeans.apache.org
Subject: Re: saxon 8.8 support

Thanks Radu!

On 10/31/06, Radu Preotiuc-Pietro <[EMAIL PROTECTED]> wrote:
> Actually, I need to make a correction:
> Saxon < 8.7.1 will still work

I don't see the XQuery error you reported, but I do see a similar error
from the XPath tests. The (trivial) change below makes the tests under
samples/XQueryXPath claim success with both 8.7.3 and 8.8 for me.

-d


Index:
src/xpath_xquery/org/apache/xmlbeans/impl/xpath/saxon/XBeansXPath.java
===================================================================
---
src/xpath_xquery/org/apache/xmlbeans/impl/xpath/saxon/XBeansXPath.java
     (revision 470119)
+++ src/xpath_xquery/org/apache/xmlbeans/impl/xpath/saxon/XBeansXPath.ja
+++ va
     (working copy)@@ -101,7 +101,7 @@
             xpe.setStaticContext(sc);

             Variable thisVar = sc.declareVariable(_contextVar);
-            thisVar.setValue(rootNode);
+            thisVar.setValue(node);

             XPathExpression exp = xpe.createExpression(_queryExpr);

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to