Title: Message
|
hi;
the
manifest class path entry work fine with WL7 and that the way to do
it.
thanks.
Hi Rupesh,
I have tried that too. I am begining to believe that the problem is
with WLS 7 and the spec.
Regards
Rohit
Hi Rohit,
Put it in the jar's
manifest and not in ear's manifest.
regards,
rupesh
----- Original Message -----
Sent: Thursday, January 23, 2003 5:43
AM
Subject: Re: How to package utility
classes and third party classes with the EAR
Hi Ritesh,
Thx for the response. As per the EJB 2.0
spec I specified the ClassPath option in the Manifast.mf file of my EAR
file and packaged the jar alongwith the EAR. WLS 7 still complain
NoClassDefFound for the utility class while deploying the session
bean.
Regards
Rohit
Try specifying the JAR(s) in the
manifest.mf file of your EJB JARs.
----- Original Message -----
Sent: Thursday, January
23, 2003 3:26 PM
Subject: How to package
utility classes and third party classes with the EAR
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
|
