-Erik
--- Begin Message ---Horst,
A general comment regarding JAR versions:
Unfortunately, many third-party JAR files we are using require fixes or specific versions. In many cases, you will have difficulties using older versions of JAR files, and there is also a risk that upgrading to a new JAR version could cause problems as well. Only testing can tell!
In addition, conflicts can happen (and do happen) with libraries included in application servers. This is why several third-party libraries in Presentation Server have been "re-rooted", e.g. put in a new package like org.orbeon.libraryname. Such libraries are Xerces, Xalan, Saxon, ANTLR, and eXist. This strategy appears to be the safest way to ensure that the software works out of the box cross-application servers (mainly Tomcat, WebLogic, WebSphere).
At the moment this is not the case for Jaxen. For now it would be best if you could manage to use the version that comes with Presentation Server.
-Erik
[EMAIL PROTECTED] wrote: > Hello, > > i have a problem with the jaxen version used by the xml server of oxf. In > our current Project we have to use the lastest version "1.0-FCS" > of jaxen (xpath) . But using this version in alliance with oxf we get an > exception out of the RequestGenerator. > We located the following lines of code: > > private Document filterRequestDocument(Document requestDocument, Node > config) { > // We always want to keep the root element (even if nothing is selected) > requestDocument.getRootElement().addAttribute(MARK_ATTRIBUTE, > MARK_ATTRIBUTE_VALUE); > for (Iterator i = XPathUtils.selectIterator(config, "/config/*"); > i.hasNext();) { > Object obj = i.next(); > // here a ClassCastException is produced because the new version > of jaxen gives us all the namespace nodes > // and namespace nodes are not elements ! > // maybe there is a possibility to change the XPathUtils > Element includeExcludeElement = (Element)i.next; > > Any help or hints ... > > Horst
--- End Message ---
