• 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 ...
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Jeanne Boyarsky
  • Tim Cooke
  • Liutauras Vilda
  • paul wheaton
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Frits Walraven
  • Piet Souris
  • Himai Minh

Why Setting classloader policy

Posts: 10
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Can anyone explain me why do we need to change classloader policy for WAS5.0?

When i checked in IBM website it says the following.
"WebSphere Application Server Version 4.0.x had a server-wide configuration setting called Module Visibility Mode.
For Version 5.0 and later, you use application or WAR class-loader policies instead of module visibility modes. The Version 5.x policies provide additional flexibility because you can configure applications running in a server for an application class-loader policy of Single or Multiple and for a WAR class-loader policy of Module or Application."

Can someone explain more about this? Or if you have any pdf or website which has info abt it pls tell me.

Thanks in advance
All of life is a contant education - Eleanor Roosevelt. Tiny ad:
free, earth-friendly heat - a kickstarter for putting coin in your pocket while saving the earth
    Bookmark Topic Watch Topic
  • New Topic