WebSphere Portal Server - Sharing libraries between Web Application and Portlet Application

This is Interesting: Free IT Magazines  
Home > Archive > WebSphere Portal Server > May 2004 > Sharing libraries between Web Application and Portlet Application





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Sharing libraries between Web Application and Portlet Application
Fredrik Andersson

2004-05-26, 4:31 pm

Hi,

I need to configure a Web Application and a Portlet Application to share
some libraries for
a project using WAS 5 and WPS 5.
However, I do not want any other part of the server to be able to use these
classes.
If I configure a shared library and allow the server to use this, then the
classes are found (and shared) between the Web Application and the Portlet
Application.
The problem with this solution is that there is a risk of including a
different version of a
library that is already in the WPS classpath, potentially causing some
existing functionality
from operating as intended.
If I configure each of the applications to use the shared library, they both
find the classes,
but they are now in different class loaders (?) since the application
doesn't seem to return the same instance for singletons.
Does anyone have a suggestion of how to solve this problem?

Regards,
Fredrik Andersson


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com