RE: axis finding jar files in lib folder

Yes I can compile my java files, but I put in the classpath as I do it i.e. javac -classpath foo.jar:. *.java I want to run the admin client without having to hard code the classpath though. I have set up two versions of Axis on tomcat one for testing purposes, for this I've renamed the axis fold

RE: axis finding jar files in lib folder

Have you tried adding a classpath to your environment that contains the admin client? Either the CLASSPATH env var in Windows, or your shell profile in *nix? -Mike > Yes I can compile my java files, but I put in the classpath as I do it > i.e. javac -classpath foo.jar:. *.java > > I want to run

RE: axis finding jar files in lib folder

I would prefer not to add any classpaths to the shell seen as I have two axis folders within tomcat one would overwrite the other Is there any other way I can tell the test folder where the adminclient is? -Original Message- From: Michael C. Clark [mailto:[EMAIL PROTECTED] Sent: 08 D

Re: Problem: invalid QName local part

Please open a JIRA bug with a stripped down test case. thanks, dims On Tue, 7 Dec 2004 11:49:14 -0500, Roth, Ide (Mission Systems) <[EMAIL PROTECTED]> wrote: > Hi, > > I'm using Axis 1.2 RC2 soap engine, Castor 0.9.5.3 for the xml binding, > Xerces 2.5.0 parser, and WebLogic 8.1 SP3 and I'm ha

RE: Problem: invalid QName local part

The problem is resolved with the nightly build from 12/07/04. Thanks, Ide -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Wed 12/8/2004 8:34 AM To: [EMAIL PROTECTED] Cc: Subject: Re: Problem: invalid QName loc

Re: Problem: invalid QName local part

Please, before opening another JIRA bug, please test with the latest CVS tree of RC2. Bug #1678 had a similar symptom/problem which was fixed. There is not enough information in this message for me to tell if the problem is identical. Thanks, Tom Gordon Davanum Srinivas wrote: Please open a J

how to add child to SOAPBodyElement

Hi i m newbie. and trying to learn SOAP. I wrote sample messege style service.it gets deployed well but when i try to add a new SOAPBodyElement inside the webservice method the following fault code is return back to client. anybody can please help me learning this part. soapenv:Server.use

Axis backward compatibility to Apache Soap w/ messagerouter

Hi,   I am trying to migrate from soap_2.3 to axis_1.1.   The current apache-soap services are using messagerouter. So, all the methods in the services has similar signature like:  myservice(Envelope, SOAPContentx request, SOAPContext response)   Axis_1.1 does not have these classes

Deploying a simple handler

Hi, I'm trying to put a simple handler on the request flow of a service. My handler extends org.apache.axis.handlers.BasicHandler (implementing invoke() and nothing else). The AdminClient deploys the service OK, but when viewing the list of deployed services, I get a ClassCastException: Exception -

Service(wsdlLoc) and header params (was: wsdl2java: Tweaking what's generated)

On Tuesday 07 December 2004 23:49, Michael Schuerig wrote: > On Tuesday 07 December 2004 10:32, [EMAIL PROTECTED] wrote: > > Have you looked at the Service constructors that take a WSDL? This > > might be the best route for you, rather than using WSDL2Java. You > > can build a client very simply. >

BUG: ArraySerializer throws NPEs when given Interface typed arrays

Lines 143 and 144 of org.apache.axis.encoding.ser.ArraySerializer need to be reversed. When the componentType of the array is an interface rather than a class, the first call to searchCls.getSuperclass() returns null (interfaces have no superclass), which causes an NPE in the bowels of axis. H