I am following the same migration path as you and I got the same problem. I assumed this is because operation overloading is not supported (WSDL 1.1 supported operation overloading and WSDL 2.0 removes it - http://www.w3.org/TR/wsdl20/#mig_ops).
I would just like to ask whether your wrapped/literal web service worked correctly once you resolved this issue.
When I invoked the wrapped/literal version of an operation which returned a JavaBean, the .NET client didn't make a call to the Java service (I used tcpMon to verify) but constructed an object on the .NET side - when I inspected it all the values were set to the default.
The RPC/Encoded version was successfully invoked and the response correctly deserialized.
If you have any suggestions on why this is happening or similar experiences, I would be interested to hear.
Thanks.
-----Original Message-----
From: Murad [mailto:[EMAIL PROTECTED]]
Sent: 18 January 2005 11:58
To: [EMAIL PROTECTED]
Subject: Wrapped/Literal :: Overlaoded method at Service Class
Hello All,
I was using Axis1.1 for SOAP server for my ongoing project with RPC
style using encoding model(as it is simplest undoubtly). I have seen
many documents and comments over web about poor performance of RPC
encoding. So I like to migrate RPC encoding model to wrapped literal
model with minimum code change.With Axis1.1 it wasnt possible
easily...and I already have a significant code base.....Currently I am
using Axis 1.2 RC2... And found with minimum change(only at the
configuration file and not touching codebase) I could convert RPC
style using encoded model into wrapped literal model....One thing I
noticed .... when In my service class contains overloaded methods(Same
method name with different parameters) it generates error while
creating client proxy(giving error of producing methods with same
name)..... Can anyone give me reasons for this or it is bug?....By the
way I am using .NET wsdl exe for generating proxy classes.
Regards,
Abdul Ahad
Lead Design Engineer
Sikraft Solution Ltd.
------------------------------------------------------------
This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately.
Ce courrier électronique est confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez ce courrier électronique par erreur, veuillez m'en aviser immédiatement, par retour de courrier électronique ou par un autre moyen.
============================================================
