• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

3rd Party Jars in MDB's

 
Ranch Hand
Posts: 33
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Seems like this problem kills me every time I need utility JAR's in a J2EE app and I don't know how to fix it. I am writing another MDB that is being deployed into WebSphere 5.1. I need to do some XML parsing. I am using dom4j. It seems that dom4j requires Jaxen for XPath queries.

I have written the code to do the parsing in a small console application (with a main method) for testing. Everything is wonderful there. However, when I put this same code into an EJB Project (using WSAD), and deploy it to the server, it fails. There are no exceptions that I can find; it just fails.

I have included the JAR files (dom4j and jaxen) in the EAR project and set the dependencies in the MDB's project. The strange thing is, the dom4j calls work but the Jaxen XPath calls fail. This tells me the dom4j jar file is deployed correctly but the jaxen jar isn't.

I don't understand what I am missing.

Any help would be GREATLY appreciated!
Andrew
 
andrew pierce
Ranch Hand
Posts: 33
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
OK. This has nothing to do with WebSphere and everything to do with the dom4j API which I was using improperly for an XML document that has an associated namespace.

Sorry for the confusion. I've got enough of that to go around

Andrew
reply
    Bookmark Topic Watch Topic
  • New Topic