Re: How to package utility classes and third party classes with the EAR

[Johan Eltes]

Title: Re: How to package utility classes and third party classes with the EAR

At runtime, WLS 7 makes all jars of the ear available to all J2EE module classloaders, regardles of whether there is a classpath entry in the module archive manifests. This is a defect of WLS. You problem occurs already at deploy time, but I would suspect that it is not related to the manifests of module archives. I’m not sure I have understood your dependency graph. Would the following description mirror your dependencies?

war
  |-->ejb-jar
  |    |-->dependent-jar
  |-->dependent-jar

with the following archive layout:

ear
  |--war
  |--ejb-jar
  |--dependent-jar

/Johan

Den 2003-01-23 10.56, skrev "Rohit Parik" <[EMAIL PROTECTED]>:

How do i package utility classes / third party classes with my EAR that already contains about 648 session beans. These interfaces of these session beans use those utility classes.

When i try to deploy the EAR after including the utility classes as a simple jar in the EAR WLS 7 is unable to deploy and gives a NoClassDefFoundError.

I understand that one should package these sort of classes using the ejb-client-jar option. But some how even that is not working.

I do not want to keep these in the system class path as any pactch would mean restart of WLS which is highly undesirable.

Any solution is welcome.

Regards
Rohit