I am not clear. Seems there are two issues,
1. SOAP encoding (blch!) vs
Literal
2. wrapped or bare arrays
Let's stay away from SOAPENC:arrayType since we all listen to
WS-I.
So, on issue #2, are you
asking, does .NET expect arrays embedded in types to be serialized
as[Example 1]:
Wow, great answer. Thanks! I was actually just asking about issue #2,
wrapped or bare arrays.
I looked over the Axis code again and realized that in
ArraySerializer.java version 1.31, the code I mentioned in my previous
mail was corrected to output wrapped or bare arrays in concordance with
Just one note here.
If you require interoperability, you shouldn't use rpc/literal since .Net
doesn't support it.
You're better off with wrapped/literal which is a flavour of
document/literal.
- Original Message -
From: Dan Hobbs [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday,
Dan,
My suggestion would be to use document / literal style. The data
structure you describe is easy to define as an XML schema (by hand if
you must, but I'd use something like XMLSpy). You can then create the
requisite WSDL file referencing this schema, generate the server side
Java classes
And just to clarify...
The difference between doc/literal and wrapped/literal is in the way
you invoke the service -- the contents on the wire (the structure of
the SOAP message) will be identical.
In doc/literal, you input an object (javabean), and you return an
object (javabean). In
Returning arrays from AXIS to .NET?
Using AXIS v1.1 server, and .NET v1.1 - it works for me.
Here's a working sample with code.
http://dinoch.dyndns.org:7070/axis/AboutBasics.jsp
I know this must be a repeat, but I looked in the archive and did not
see it. . .
Is the arrays issue specific
