Re: Java2WSDL problem

I figured it out. Thanks anyway Pathuru, Kiran wrote: run it from C:\devWS directory like java -classpath test .. regards, kiran pathuru -Original Message- From: Danko Desancic [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 25, 2004 4:26 PM To: [EMAIL PROTECTED]

RE: Java2WSDL problem

run it from C:\devWS directory like java -classpath test .. regards, kiran pathuru -Original Message- From: Danko Desancic [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 25, 2004 4:26 PM To: [EMAIL PROTECTED] Subject: Java2WSDL problem I am new to the axis and

Re: java2wsdl problem with axis1.2 alfa

Roberto,   The java2WSDL and WSDL2java not always work as one expected. They always work molto bene with those interfaces that contain simple type such as String, int, float and so on. The listUsers() interface seems simple, try to write the deploy.wsdd and the client code yourself and deploy the s

RE: Java2WSDL problem for vandana

y-To: [EMAIL PROTECTED] To: <[EMAIL PROTECTED]> Subject: RE: Java2WSDL problem for vandana Date: Mon, 10 Mar 2003 11:26:21 +0530 Hi, What is the exception that you're getting while deploying the service? rgds, Vandana. -Original Message- From: parmod mehta [mailto:[EMAIL PROTECTED] S

RE: Java2WSDL problem.

Hi, I realised my problem. The "collectionserializer" and "collectiondeserializer" that I am using use the soap.jar provided by Apache and not the AXIS Apis. The current (de)serializer uses the marshall and unmarshall methods while the AXIS APIs do not have such methods. Has anybody written c

RE: Java2WSDL problem for vandana

Hi, What is the exception that you're getting while deploying the service? rgds, Vandana. -Original Message- From: parmod mehta [mailto:[EMAIL PROTECTED] Sent: Saturday, March 08, 2003 9:42 PM To: [EMAIL PROTECTED] Subject: Re: Java2WSDL problem for vandana Hi, Sorry I don&#

Re: Java2WSDL problem for vandana

Hi, Sorry I don't have answer of your question. Can you answer my question? This is the first time I am using axis. I have encountered a problem straight away. I generated a WSDL from an interface with namespace "urn:managerdata". The WSDL2Java tool created a directory named managerdata in my

RE: Java2WSDL problem in namespace for bindings

Hi, I reported the same thing in the axis-dev list but did not get any resolution. There was a bit of discussion on the subject. Look into the thread "[BUG] Beta2 interop (was RE: Interoperability issue with MSVC++.Net)". This seems to have changed in beta2. It was OK in beta1. -Original Me