Re: [jaxen-dev] Re: [dom4j-dev] XPath-changes in 1.6

2005-04-19 Thread Elliotte Harold
David J. M. Karlsen wrote: Can I just swap the 1.1b4 with a b5 or a b6 - will dom4j 1.6 be compatible? Should be, unless maybe dom4j is depending on the IdentityHashMap class I deleted over the weekend for licensing reasons. Otherwise, I don't think there are any API level changes, just bug fixes

Re: [jaxen-dev] Re: [dom4j-dev] XPath-changes in 1.6

2005-04-19 Thread Elliotte Harold
A fix for this is now in Jaxen's CVS. Can you check this out and see if it solves your problem? Thanks. -- Elliotte Rusty Harold [EMAIL PROTECTED] XML in a Nutshell 3rd Edition Just Published! http://www.cafeconleche.org/books/xian3/ http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/

Re: [jaxen-dev] Re: [dom4j-dev] XPath-changes in 1.6

2005-04-19 Thread David J. M. Karlsen
Elliotte Harold wrote: David J. M. Karlsen wrote: org.jaxen.BaseXPath.(BaseXPath.java:143) org.jaxen.BaseXPath.(BaseXPath.java:158) org.jaxen.dom4j.Dom4jXPath. java version 1.3.1 on windows IBM build cn131-20031021 Never mind. I found the offending line of code. It's definitely our mistake, and do

Re: [jaxen-dev] Re: [dom4j-dev] XPath-changes in 1.6

2005-04-19 Thread Elliotte Harold
David J. M. Karlsen wrote: org.jaxen.BaseXPath.(BaseXPath.java:143) org.jaxen.BaseXPath.(BaseXPath.java:158) org.jaxen.dom4j.Dom4jXPath. java version 1.3.1 on windows IBM build cn131-20031021 Never mind. I found the offending line of code. It's definitely our mistake, and does tie Jaxen to 1.4 un

Re: [jaxen-dev] Re: [dom4j-dev] XPath-changes in 1.6

2005-04-19 Thread Elliotte Harold
David J. M. Karlsen wrote: java version 1.3.1 on windows IBM build cn131-20031021 OK. That makes me more suspicious. I'll have to look harder to see if we unintentionally tied Jaxen to 1.4. Any chance you could try this code in a 1.4 VM and see if the bug goes away? -- Elliotte Rusty Harold [EM

Re: [jaxen-dev] Re: [dom4j-dev] XPath-changes in 1.6

2005-04-19 Thread David J. M. Karlsen
Elliotte Harold wrote: 2) this expression is no longer valid, and fails: [EMAIL PROTECTED]'B']/row/[some_node='val1']|[some_node='val2'] java.lang.NoSuchMethodError: org.jaxen.XPathSyntaxException: method initCause(Throwable) Throwable: not found (BaseXpath: 143 and 158) Could we get a full stack

Re: [jaxen-dev] Re: [dom4j-dev] XPath-changes in 1.6

2005-04-19 Thread Elliotte Harold
Maarten Coene wrote: 2) this expression is no longer valid, and fails: [EMAIL PROTECTED]'B']/row/[some_node='val1']|[some_node='val2'] java.lang.NoSuchMethodError: org.jaxen.XPathSyntaxException: method initCause(Throwable) Throwable: not found (BaseXpath: 143 and 158) Could we get a full stack t

Re: [dom4j-dev] XPath-changes in 1.6

2005-04-18 Thread Maarten Coene
David, I'm forwarding this to the jaxen mailinglist, I hope they can answer question 2 and 3 regards, Maarten David J. M. Karlsen wrote: While upgrading from 1.52 to 1.6 I've discovered these changes: 1) Document doc2 = document.selectSingleNode("/some/xpath").getDocument(); now returnes the whol

[dom4j-dev] XPath-changes in 1.6

2005-04-18 Thread David J. M. Karlsen
While upgrading from 1.52 to 1.6 I've discovered these changes: 1) Document doc2 = document.selectSingleNode("/some/xpath").getDocument(); now returnes the whole document, and not the nodes under /some/xpath like it did before. 2) this expression is no longer valid, and fails: [EMAIL PROTECTED]'B