Hmm, Christopher, a while back, another user had a problem just like you - http://www.mail-archive.com/[email protected]/msg03687.html - everything works fine not using maven, but it doesn't work when using maven, and the problem as with your case is using incompatible versions of xbean.jar and xbean_xpath.jar (however they are renamed in maven). Seems to me maven must make it easy for users to make mistakes like that, which doesn't speak in its favor. But I speak out of ignorance, since I don't use maven. - Wing Yew
_____ From: Christopher Hunt [mailto:[email protected]] Sent: Monday, June 15, 2009 4:26 PM To: Wing Yew Poon Cc: [email protected] Subject: RE: Xpath/Saxon classpath issue? Hi Wing Yew, On 16/06/2009, at 3:42 AM, HYPERLINK "mailto:[email protected]"[email protected] wrote: I don't use maven and it's too hard for me to read the classpath you include, but you not only need saxon9.jar and saxon9-dom.jar, you need xbean_xpath.jar. The xbean_xpath.jar comes with the XMLBeans 2.4.0 binary distribution. And yes, it is a classpath issue. Thanks for your reply. I have also tried using xbean_xpath.jar but with the same result. Please note that I'm using xmlbeans-xpath-2.4.0.jar which contains the same classes as xbean_xpath.jar - I think though that xmlbeans-xpath-2.4.0.jar is provided as a convenience for us Maven users. Please note that all works well when running under jUnit and Eclipse, but not Maven and Surefire. Perhaps this is more of a Maven issue. Nonetheless, any help appreciated before I give up on using the xpath of xmlbeans. Kind regards, Christopher P.S. I find it a little bewildering that xmlbeans doesn't utilise Maven given its Apache status.
