• 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:
  • Devaka Cooray
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • Paul Clapham
Sheriffs:
  • Liutauras Vilda
  • Jeanne Boyarsky
  • paul wheaton
Saloon Keepers:
  • Tim Holloway
Bartenders:

Xerces in WebSphere again

 
Ranch Hand
Posts: 264
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
This question has been asked for years but is still bothering me

Environment:
WSAD 5.1.2
Test Environment 5.1

I have a xerces.jar (Xerces 1.4.0) included in my EAR. This xerces is used by an EJB to parse some XML documents. I set the classloading policy of the EAR to be PARENT_LAST and MODULE to make sure my xerces is picked up. This works for the EJB XML parsing part.

However, after I added web services interface based on that EJB, the web service won't work because my xerces is not compatible for the new web services. I switch to PARENT_FIRST, web services work but not my EJB XML parsing.

Articles on this issue alwasy deal with using xerces in WARs, not with EJB cue there is no such setting for EJB (unlike WARS, you can use its own classloader mode).

I think this must be a common issue. Anyway to work around it?

Thanks in advance...
 
And then the flying monkeys attacked. My only defense was this tiny ad:
The new gardening playing cards kickstarter is now live!
https://www.kickstarter.com/projects/paulwheaton/garden-cards
reply
    Bookmark Topic Watch Topic
  • New Topic