Help coderanch get a
new server
by contributing to the fundraiser
  • 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
  • Ron McLeod
  • Paul Clapham
  • Devaka Cooray
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • paul wheaton
  • Henry Wong
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Tim Moores
  • Carey Brown
  • Mikalai Zaikin
Bartenders:
  • Lou Hamers
  • Piet Souris
  • Frits Walraven

How this classloading settings work ?

 
Ranch Hand
Posts: 548
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
a.ear
-|-------- axis.war (web module)
-|-------- c.jar (ejb module)

say I have below set of jars under axis.war\WEB-INF\lib:

axis-ant.jar, axis.jar, bcel.jar, commons-discovery.jar, commons-logging.jar, jaxrpc.jar, jibx-bind.jar, jibx-extras.jar, jibx-run.jar, log4j-1.2.8.jar, saaj.jar, wsdl4j.jar, xerces.jar, xercesImpl.jar, xml-apis.jar, xpp3-later.jar, xpp3.jar

Now with below settings

a.ear Classloader mode: PARENT_FIRST
a.ear WAR classloader policy: APPLICATION
b.war Classloader mode : PARENT_FIRST or PARENT_LAST

I am successfully able to run AXIS 1.2 RC2 Web Module inside a EAR deployed on WSAD 5.1.2's WebSphere 5.0 Test Environment. Actually I faced a JiBX classloading issue if I keep any other settings other than above. I am not even sure why the above setting works for me. Can anyone please clarify ...
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic