Hi,
This is a classloader problem. As far as I'm aware, each WAR will have a separate classloader and consequently be unable to load classes in another WAR - even if it is in the same application (EAR). The way around this is to create a jar of 'common' classes that all the EJBs and WARs in an application use. As long as your scope (module visibility of the application server)is set to 'Application' the other modules should be able to see all files in the common jar. We've used this approach to share common classes between the
EJB modules and a single WAR module - though I suspect that its the same principal if there are multiple WARs.
Its probably worth investigating how WAS loads classes - look in the WAS 4.0 Handbook from RedBooks.
Also, there is a recent article here that may shed some light on it:
http://www.theserverside.com/resources/article.jsp?l=ClassLoading I hope this helps.
Cheers,
Steve
[ May 29, 2002: Message edited by: Steve Granton ]
[ May 29, 2002: Message edited by: Steve Granton ]