Hello,
We are trying to work with our web service, which is publishedas RPC-Literal. In all the simple cases, it is working very fine. But in some of the cases, we are facing problems; like:
a). If an operation has a parameter with a schema like 'A user defined type having a array of User
gest you use Wrapped Document/Literal instead.(Note that .NET does not support RPC/Literal, either.)AnneOn Mon, 20 Dec 2004 03:48:27 -0800 (PST), Adaptive Protocols<[EMAIL PROTECTED]>wrote: Hello, We are trying to work with our web service, which is published as RPC-Literal. In all the simple
Hello Everybody,
I have an issue with Axis Client side API. The requirement is that:
I want to invoke web services using Axis Client. Now here I don't have parameters as java objects rather I do have XML structure ( as required for soap message ) for these objects. So is there any way to
Hi Renuka,
I think, you need to register a type mapping on server side wsdd for this. i.e. define a type mapping in server-config.wsdd with xml type as xsd:int, java type as int class and you custom deserializer factory, which will return custom deserializer.
This should solve the purpose.
Mohit,
Can you provide specifics of the service your client is consuming.
Looks like what you need is amessage style method. If your server supports it you should be able to supply an xml doc.
Jai
-Original Message-From: Adaptive Protocols [mailto:[EMAIL PROTECTED]Sent: Monday, December 20,
Hi Russell,
Check the log4j. properties file inaxis classpath. It should be there with proper settings.
Thanks,
MohitRussell Lane [EMAIL PROTECTED] wrote:
I'm running Java Axis v.1.2 RC 2 on Tomcat v.4.1.31. I followed the install instructions correctly (I think), and am now deploying some
Hi All,
I am waiting for a kind response for this problem. I am just stuck with this one. Any clue would be a great help for me.
Thanks,
Mohit
Adaptive Protocols [EMAIL PROTECTED] wrote:
Thanks Anne. I am trying with Wrapped Document/Literal.
But here also, I am facing the same problem. I
This is just due to classes mismatch. You have both new and old axis library in your classpath. Better to clean classpath completely and populate it with jars again.
This could certainly make axis happy.
Thanks
MohitDeivanai [EMAIL PROTECTED] wrote:
Hi,
I am using axis version 1.2 and