J2EE packaging 2003-12-19 - By J=?ISO-8859-1?Q?=F8rn_=D8lmheim?=
Back
Sachin,
Your problem can be solved by modifying your EAR settings in WSAD. Like you
say, each war module has by default its own classloader and is isolated from
the rest of the application. This means that calling ejb modules from the
war is ok but calling one war from another is not possible.
To allow calls into the war from another war, you need to change the War
classloader policy from MODULE to APPLICATION in the Server (WebSphere Test
environment) configuration.
You find this in the server perspective (I assume you use WSAD 5.x), from
the Server Configuration view, select the test server you are running on and
open it. In the Applications tab at the far right of the configuration you
will find the Application Options. Select the EAR you are running and change
the War classloader policy.
Hope this solves your problem.
Best regards,
J�rn �lmheim
SCEA
Statoil ASA
===================================================================Companion
Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
|
|
