The better approach is to set the classloader policy for your web module in the Enterprise Application to Parent last. This tells WebSphere that for your application, you want it to favor the libraries in the WAR over those bundled with WebSphere.
We've run into this problem with several JARs
Van: [EMAIL PROTECTED] namens Eric Hedström
Verzonden: wo 26-4-2006 21:36
Aan: MyFaces Development
Onderwerp: Re: Myfaces running on WebSphere Application Server v6.1
The better approach is to set the classloader policy for your web module in the
Enterprise Application to Parent last
to find anything on the IBM site ;-)
Regards,
Erik-Berndt Scheper
Van: Scheper, Erik-Berndt [mailto:[EMAIL PROTECTED]
Verzonden: wo 26-4-2006 21:43
Aan: MyFaces Development
Onderwerp: RE: Myfaces running on WebSphere Application Server v6.1
Yes, this should work
You may find this helpful
http://wiki.apache.org/myfaces/Websphere_Installation
On 4/20/06, Graham Crooks [EMAIL PROTECTED] wrote:
I am porting on behalf of a software house, an application that is currenly
running on Tomcat Server under Redhat Linux.
The developer has made extensive use of
