• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

XPath functions and WebSphere

 
Jon Bricker
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am having trouble getting XPath functions to work properly in WS 4.0.5. We are using JDom and Jaxen as our Java and XPath APIs. We are loading the Xalan, JDom, Jaxen and Xerces with our ear file in the top lib ( because they are being used in both the EJB and the Web layer).
In this first set of code without a XPath function we can get the element and then the text to get the result:

This second one will return a null;

jdoc is our JDom Document.
I suspect that WS is calling an older version of Xalan that does not have the functions. Any suggestions on what to look for?
thanks
 
Kyle Brown
author
Ranch Hand
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Try changing your classloader policy to PARENT_LAST.
Kyle
 
Jon Bricker
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
that would work if we were using WS 5.0. How can we do the same thing with WS 4?
 
Kyle Brown
author
Ranch Hand
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Check section 6.4.1 of the WAS 4.0 infocenter. I think you want to change your ejbDelegationMode to false to make this work within your EJB's. I'm guessing that it should be working correctly already within your JAR's.
Kyle
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic