Hi, In my WSAD environment, The EAR file contains a two session beans as a part of the EAR. When you expand the Ear in server view, you will see these under the deployed ear.
Locate the Manfest.mf in these session beans and add the full path of the jar files. If these are internal to EAR, when you add, you will see a relative path. If these are external to your EAR, you need to give the complete path. You may be able to do the same on a production environment. Regards sagar -----Original Message----- From: Shashi Rai [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 10:05 AM To: [EMAIL PROTECTED] Subject: RE: Axis1.2 and Websphere 5.1 Sagar, Great ! You might have the solution. One thing I did not try is change the manifest on ear. In order to deal with other class loading issues, I do have manifest entries on the other jars and wars. Could you please elaborate on manifest? Does ear manifest includes axis.jar with complete path i.e. war/lib/axis.jar etc. Thanks --shashi -----Original Message----- From: Sagar Pidaparthi [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 9:07 AM To: [EMAIL PROTECTED] Subject: RE: Axis1.2 and Websphere 5.1 -----Original Message----- From: Vikas Phonsa [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 8:54 AM To: '[EMAIL PROTECTED]' Subject: RE: Axis1.2 and Websphere 5.1 > I don't work with websphere on its own but WSAD, which has >websphere inside. We change class path and it works. >Could you elaborate a little bit on that. I'm using WSAD/WSSD (how they keep >changing names !!!! ) 5.1 and if I chose to run the web services webapp with >apache axis 1.1 run time, all the axis and related jars are automatically put into the lib directory. >I'm creating a doc/literal web service and want to use axis 1.2. What >does it take to do it ? Just copying the right jars into the webapp or what ? >I did not have any conflicts with axis jars while working with wsad. Here is what I did, 1. Created a web project in WSAD. This creates the right hierarcy of folders and adds the web project to EAR file that runs on your app server. 2. unzipped axis 1.2. Copied everything under C:\axis-1_2beta\webapps\axis to webcontent folder. 3. copied the jars to be deployed to classes folder, ( I observe that this step may not be required) 4. I had to change the manifest files of the ear that I deploy to add the axis jars. 5. Started the app server inside the WSAD. This was picking up the right jars since the EAR manifest files were referring to the right jars. >And eventually the app would need to be deployed on a production >Websphere where I would have to worry abt other issues. I am not yet deploying these on the production environment Thanks Vikas -----Original Message----- From: Sagar Pidaparthi [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 8:21 AM To: [EMAIL PROTECTED] Subject: RE: Axis1.2 and Websphere 5.1 I don't think this option will be acceptable if you are shipping your product to a third party or your product needs to work for a large number of customers. We also got around this problem by changing the class paths. I don't work with websphere on its own but WSAD, which has websphere inside. We change class path and it works. Regards Sagar -----Original Message----- From: Shashi Rai [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 7:40 AM To: [EMAIL PROTECTED] Subject: RE: Axis1.2 and Websphere 5.1 Hi Mike, I did change to PARENT_LAST class loading behaviour for EAR as well as WAR file and it still complains. The only option seems to work for me is either remove the webservices.jar supplied by websphere or modify webservices.jar by removing saaj apis and dropping the new saaj.jar supplied with Axis. Since I am not using websphere's webservices, I am not sure how much damage this can cause to other applications who use it. Thanks --shashi -----Original Message----- From: Mike Burati [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 7:20 AM To: '[EMAIL PROTECTED]' Subject: RE: Axis1.2 and Websphere 5.1 Shashi, One means of getting a JAR in your WAR/EAR loaded in preference to a similar but older one packaged with WebSphere 5 is to go into the WAS5 Admin tool and set the Class Loader behavior on your WAR and/or EAR to PARENT_LAST (I believe it defaults to PARENT_FIRST) so that it'll look in your app first to resolve classes rather than in the parent's context first. It may not work in all cases, but we have successfully used it to work around conflicts in jars that WPS5 adds when you install it on WAS5 (where we have similar jars in our WARs)... ..Mike -----Original Message----- From: Shashi Rai [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 2:09 AM To: [EMAIL PROTECTED] Subject: Axis1.2 and Websphere 5.1 Hi All, While going thru the list, I see lots of people are using Axis and Websphere but not sure if anyone is using Axis1.2 beta 3 with WAS 5.1 fixpack1. In my application, I package Axis as a webapplication inside ear. I can not seem to get my webservices working with Websphere unless I remove websphere supplied .jar file. I get the following error because websphere supplied .jar file includes older saaj apis. [8/21/04 14:46:08:292 PDT] 3a289b4e WebGroup E SRVE0026E: [Servlet Error]-[class org.apache.axis.SOAPPart does not implement interface org.w3c.dom.Document]: java.lang.IncompatibleClassChangeError: class org.apache.axis.SOAPPart does not implement interface org.w3c.dom.Document Is there anyone who encountered the similar issue ? Any idea how to resolve this ? Thanks for help. --shashi
