RE: Axis1.2 and Websphere 5.1

2004-08-31 Thread Sagar Pidaparthi
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

RE: Axis1.2 and Websphere 5.1

2004-08-31 Thread Shashi Rai
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

RE: Axis1.2 and Websphere 5.1

2004-08-31 Thread Sagar Pidaparthi
-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 cl

RE: Axis1.2 and Websphere 5.1

2004-08-31 Thread Vikas Phonsa
loyed on a production websphere where I would have to worry abt other issues. 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 wil

RE: Axis1.2 and Websphere 5.1

2004-08-31 Thread Sagar Pidaparthi
ere 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

RE: Axis1.2 and Websphere 5.1

2004-08-31 Thread Shashi Rai
-Original Message- From: Mahen Perera [mailto:[EMAIL PROTECTED] Sent: Monday, August 30, 2004 11:21 PM To: [EMAIL PROTECTED] Subject: Re: Axis1.2 and Websphere 5.1 use the jars suppiled in the Axis 1.2 distribution. Since ur using Axis as the SOAP engine instead of the one provided in

RE: Axis1.2 and Websphere 5.1

2004-08-31 Thread Shashi Rai
]' 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

RE: Axis1.2 and Websphere 5.1

2004-08-31 Thread Mike Burati
al 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.

Re: Axis1.2 and Websphere 5.1

2004-08-30 Thread Mahen Perera
info,, since I am also using Axis inside WebSphere Mahen - Original Message - From: Shashi Rai <[EMAIL PROTECTED]> Date: Mon, 30 Aug 2004 23:09:10 -0700 Subject: Axis1.2 and Websphere 5.1 To: [EMAIL PROTECTED] Hi All, While going thru the list, I see lots of people are using Ax

Axis1.2 and Websphere 5.1

2004-08-30 Thread Shashi Rai
Title: Message 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 wit