RE: RE : Jar files in EAR root.

[Brown, Mike]

Title: Message

Jai,

    The problem is one that pops up a LOT with Websphere and should find it's way into axis' documentation. Websphere includes a (very outdated in version 4.0) copy of saaj.jar. By default it is this copy that gets loaded by your webapp classloader. There is an option when you deploy your ear that tells Websphere that you want the classloader to load your classes first. I'm not quite certain how to do this in version 4.0 but do a search in your documentation for "Classloader mode" and you should find instructions for setting it (you want to set your EAR classloader mode to PARENT_LAST). Let me know if this works for you (it should).

 

Michael

 

---

From: THOMAS, JAI [AG-Contractor/1000] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 09, 2005 4:15 PM
To: '[EMAIL PROTECTED]'
Subject: RE: RE : Jar files in EAR root.

Christian,

We are using WebSphere 4.0 and manifest.mf of all application jar files as well as the web-application have entries for axis jar files. I do not think this is anything to do with application server. In fact it looks like it is able to locate axis.jar but not saaj.jar.

To me it looks more like a classloader problem.

Apparently this problem is present in weblogic also.

See http://www.mail-archive.com/axis-user@xml.apache.org/msg07373.html

 

Thanks

Jai

 

-----Original Message-----
From: Faucher, Christian [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 09, 2005 3:33 PM
To: [EMAIL PROTECTED]
Subject: RE : Jar files in EAR root.

Hi,

 

Depending how close to the specs your app server is, you may have to add a "class-path" entry to the MANIFEST.MF of each JARs that use the axis.jar at the root of your EAR.  Note that the entry is relative to the EAR root, e.g. "axis.jar" should suffice.  If you put it in EAR, in library/, then it would be library/axis.jar.

 

This is actually documented in J2EE spec.  However, some AppServers automatically "add" JARs at the root to the EAR classpath (e.g. to classpath of sub-components, WAR, JAR, etc.), some do not.  We use SunONE, for which we have to add this damned manifest entry to refer to "global" JARs in our EAR.

 

Hope it helps...

 

Christian Faucher

 

 

-----Message d'origine-----
De : THOMAS, JAI [AG-Contractor/1000] [mailto:[EMAIL PROTECTED]]
Envoyé : mercredi, février 9, 2005 15:56
À : [EMAIL PROTECTED]
Objet : Jar files in EAR root.



I have been trying to invoke Axis jar files installed under EAR root (as opposed to webapp/WEB-INF/lib) for the past couple of days but with no success. It does work fine if I keep all files under web-inf/lib but needed to move them to EAR folder since couple of our application jars need to see Axis jars. EAR root is always included in an enterprise app class path and should work, but doesn't.

Instead it gives ClassNotFoundException for javax.xml.soap.SOAPException which is in saaj.jar. I keep getting this error even if I copy saaj.jar to web-inf/lib folder.

I have seen this same problem reported in the past not seen any solution.

Please let me know if anyone has a solution for this.


Jai Thomas
Monsanto

---

"Ce message est confidentiel, à l'usage exclusif du destinataire ci-dessus et son contenu ne représente en aucun cas un engagement de la part de AXA, sauf en cas de stipulation expresse et par écrit de la part de AXA. Toute publication, utilisation ou diffusion, même partielle, doit être autorisée préalablement. Si vous n'êtes pas destinataire de ce message, merci d'en avertir immédiatement l'expéditeur."

"This e-mail message is confidential, for the exclusive use of the addressee and its contents shall not constitute a commitment by AXA, except as otherwise specifically provided in writing by AXA. Any unauthorized disclosure, use or dissemination, either whole or partial, is prohibited. If you are not the intended recipient of the message, please notify the sender immediately."