You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@xml.apache.org by Kailash Aynor <ak...@hotmail.com> on 2000/07/20 21:40:44 UTC
hi
Hi,
I have just got included in this soap-dev list. However i would like to test and try the xml-soap code. Would u able to tell me what is the environment that i need to setup and also which is the zip file i should download to be able to remain consistent with this list.
Kailash.
----- Original Message -----
From: tamminga@us.ibm.com
To: soap-dev@xml.apache.org
Cc: Wouter Cloetens ; pzf@uk.ibm.com
Sent: Thursday, July 20, 2000 3:11 PM
Subject: Re: IBM WebSphere patches to apache-soap
I too have gotten xml-soap to work with WAS 3.0.2 by putting the jars on
the application server classpath (using a -classpath command line
argument)rather than on the webapp classpath. I have been told that the
webapp classpath should ONLY contain servlets as it is connected to a
special class loader that reloads everything whenever any servlet changes.
Apparently this classloader has some other characteristics (such as trying
to load the XMI stuff before the class is referenced at run time and/or not
working for dynamically loaded classes).
>Paul Freemantle wrote:
>
>Are you sure you need to patch the registry. I found that if I put it in
the
>System classloader instead of the WebApp classloader, then it didn't try
to
>load the 1.2 stuff and worked unmodified. Admittedly it was the old
IBM-SOAP
>stuff I tried. I've since moved to the 3.5 beta and it seems to work fine.
Paul W. Tamminga
Dept. DXS -- WebSphere Business Components
Phone: 507-253-4270 Tie: 553-4270
Notes: Paul Tamminga/Rochester/IBM
Internet: tamminga@us.ibm.com