Wrapped doc/literal should work -- although you will probably do better using Axis 1.4 rather than Axis 1.3. There still are some problems with arrays, but you shouldn't have a problem with the bean. Please post some sample WSDLs and SOAP messages.
Anne On 9/20/06, Brian Moffatt <[EMAIL PROTECTED]> wrote:
I've seen this exact problem addressed in the archives but never with any clear solution. I was wondering if this was something for which there is a known solution and I'm just not finding it. Basically, I have an Axis based web service with 5 available methods. One returns a simple Java bean (made up of three Strings and an int) and one returns an array of said beans. The others return nothing. I am using Axis 1.3 and Apache Tomcat 5.0. I used the document/literal wrapped mode. I got the service deployed fine and can call it successfully from the generated Java client proxy code. My problem is when I try to call it from .NET. I ran the WSDL through the wsdl.exe tool included with Visual Studio 2005 and wrote a simple driver console app to call the generated code. It works. . . sort of. The method that returns a bean, returns a bean but all the fields are nulled out or zero. The method that returns an array of beans, returns an array of beans of the appropriate length, but all the attributes of the beans in the array are null / zero. I did some testing and can get a method that just returns a String or primitive to interoperate correctly using Doc/Literal wrapped. One last thing. I did get the Axis -.NET communication to work completely with the complex types / arrays of complex types but had to use RPC/Encoded when creating my service with Axis to achieve success. Ironically, this is the only way that makes .NET yell at me for being WS-I non-compliant when I run wsdl.exe. Does this sound familiar to anyone? Is it a common problem? Is there a known solution? I've read that Doc/Literal wrapped is THE way to go if you want Axis - .NET interop, but my experience has been that RPC/Encoded is the only way that works. I'd rather use whatever is WS-I compliant. Any feedback is greatly appreciated. I'll gladly supply a WSDL, SOAP messages, or other data from my test case anyone wishes to see. Thanks, Brian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
