On Sep 6, 2007, at 11:52 AM, Anshuk Chinmoy Pal Chaudhuri wrote:

Hi,

One more query on this classloader. As I said earlier, I have already deployed the connector.rar and have mentioned the required classes.jar in the manifest worked fine. Now I was trying to deploy a ejb as well as the next module in the ear, and it required some other jars from the same lib folder in the ear, so I mention those jar (e.g. ejbclasses.jar) in the manifest.mf of the ejbapp.jar, but it gives NoClassDefFound.

I find that very surprising and wonder if you have the right path in the manifest classpath.

But when have I mentioned the same required ejbclasses.jar in the manifest.mf of the first module of connector.rar, it is getting deployed correctly.

Please correct me if I am wrong, as the connector.rar is getting loaded first, and the class for ejb which is not being found is in the parent classloader of the connector.rar and that is the reason why the class not getting found. I checked it †@ http://mail-archives.apache.org/mod_mbox/geronimo-user/200705.mbox/%3C84706160@web.de%3E .


All ejb modules and connector modules and anything reachable in their manifest classpaths (transitively) all gets added to the same classloader and used for all these modules.† Only wars get separate (child) classloaders.

thanks
david jencks

So the way I made it work, is that the correct way, or is there any other workaround?

Warm Regards,
Anshuk Pal Chaudhuri


From: Anshuk Chinmoy Pal Chaudhuri [mailto:Anshuk_PalChaudhuri@infosys.com]
Sent: Thursday, September 06, 2007 9:14 PM
To: user@geronimo.apache.org
Subject: RE: manifest classloader issue

Hi David,

Yeah..you are spot on..it worked in g 1.1.1 by the lib/classes.jar

Thanks a lot.

Warm Regards,
Anshuk Pal Chaudhur
i


From: David Jencks [mailto:david_jencks@yahoo.com]
Sent: Thursday, September 06, 2007 8:54 PM
To: user@geronimo.apache.org
Subject: Re: manifest classloader issue

On Sep 6, 2007, at 8:18 AM, Anshuk Chinmoy Pal Chaudhuri wrote:

Hi Kevin,

I did try on Geronimo 2.0.1, it did work on that, but I have to make it work on 1.1.1. Is there any workaround?

I think it worked on 2.0.1 because anything in the ear lib directory (lib by default) is added to the ear classloader, not because of your manifest classpath entry which I think should be lib/classes.jar.

thanks

david jencks

Warm Regards,
Anshuk Pal Chaudhuri


From: Anshuk Chinmoy Pal Chaudhuri [mailto:Anshuk_PalChaudhuri@infosys.com]
Sent: Thursday, September 06, 2007 8:25 PM
To: user@geronimo.apache.org
Subject: RE: manifest classloader issue

Hi Kevin,

I will definitely take care of your request going further on.

Manifest.mf content

Manifest-Version: 1.0

Class-Path: ../lib/classes.jar

No, I havenít tried on 2.0.1, we have to work on Geronimo 1.1.1, that is what the requirement is.

Thanks.

Warm Regards,
Anshuk Pal Chaudhuri


From: Kevan Miller [mailto:kevan.miller@gmail.com]
Sent: Thursday, September 06, 2007 8:14 PM
To: user@geronimo.apache.org
Subject: Re: manifest classloader issue

Anshuk,

One request -- please use "New Message" to start a new email thread, rather than using "Reply" and editing the subject.

More below...

On Sep 6, 2007, at 9:50 AM, Anshuk Chinmoy Pal Chaudhuri wrote:

Hi,

I am trying to deploy a connector rar from inside the ear on Geronimo 1.1.1. The connector ra.xml file refers to all the classes like the activationspec-class and so on. If I put the jar (containing all these classes), just directly under the connector rar, the the ear is deploying properly, but when †I try to put the jar inside deployable.ear\lib †and mention the jar path in the manifest.mf of the connector.rar (..\lib\classes.jar) ..it gives class not found (which is there in the jar)

Rather that providing your own version of spec classes, I recommend you use Geronimo's supplied specs via dependencies, instead.

What is the contents of your Manifest.mf? Have you tried this on Geronimo 2.0.1?†

--kevan

**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***