On 3/18/03 11:17 AM Jaspreet Singh <[EMAIL PROTECTED]> wrote: > Hi, > > I have a war file, ejb-jar file and a common jar file inside an ear that I am > trying to deploy using axis. > > The common jar file contains common file require by both ejb-jar and war > files, these are essentially the complex types exposed by the web service, > these complex types are passed onto the ejb in the ejb-jar that provides the > business functionality required. Note that eventually it is envisaged that the > EJB will act as the endpoint to the service. > > The Class-Path entry in Manifest.mf of the war and ejb-jar files both point to > the common jar. Now the problem is that whenever I deploy this inside Weblogic > 7 sp2 I get the following exception thrown. Note that if I stub the code in > the war file and move the common files into that war then I recieve no errors. > .. >
If have started a discussion on this topic on axis-dev, and as far I can tell the current resource/classloader implementation in axis will always create those problems. The problem your are running into is the bea classloader hierarchy, where EJB-JAR Classloaders are used to load war archives (in EAR mode) or separate classloaders will be used for war/ear loading. For now you can only work around the issue: Either put your resources in both the war and ejb-jar file or test EAR deployment. If you don't use Axis classes on EJB level disabling auto start for the AxisServlet may help too. (Because then there is a high chance that the war classloader will be used to load all classes instead of the ejb-jar classloader). I did not have the time to review the Axis resource/classloading issues, hopefully I can come up with some ideas next week ... Jens
