Is "wrapped" supposed to have meaning only on the server side (where it
determines how arguments are passed to the implementation method for the
operation), or also on the client side (where it would determine whether the
document that makes up the soap body of a doc/lit operation must be
supplied, or whether Axis will assemble one from the child components of
that document)?
Also, if "wrapped" has meaning on the client side, is its usage completely
independent of what is done on the server side, since what is transmitted
over the wire is the same? That is, the client could set the style to be
wrapped in a deployment descriptor in order to be able to supply primitive
data types and have them assembled into the request document, even if the
service implementation is processing that document as a whole (and vice
versa)?
Axis currently supports use of wrapped on the client. I noticed recently
using the Axis samples.client.DynamicInvoker with a doc/lit web service
looking like (namespace stuff omitted):
<types>
<schema ...>
<element name="x" type="X"/>
<complexType name="X">
<sequence>
<element name="a" type="anyURI"/>
</sequence>
</complexType>
<element name="xResponse" type="XResponse"/>
<complexType name="XResponse">
<sequence>
<element name="b" type="string"/>
</sequence>
</complexType>
</schema>
</types>
<message name="xRequest">
<part name="parameters" element="x"/>
</message>
<message name="xResponse">
<part name="parameters" element="xResponse"/>
</message>
<portType name="xPT">
<operation name="x">
<input message="xRequest"/>
<output message="xResponse"/>
</operation>
</portType>
that I could pass the single WS argument "urn:foo" to the DynamicInvoker
client command line, and it would use this to construct the content for the
request's soap body:
<x><a>urn:foo</a></x>
under the assumption that this operation is wrapped (verified by the traces
emitted with debug logging enabled for Axis).
Jeff
----- Original Message -----
From: "Anne Thomas Manes" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, December 20, 2004 9:14 AM
Subject: Re: Problem with {User defined type} having array of {User defined
type} with RPC-Literal
Note that Axis doesn't really support RPC/Literal. It kinda supports
it from a client perspective, but there's no Axis WSDD "style"
attribute value that corresponds to RPC/Literal.
I suggest you use Wrapped Document/Literal instead.
(Note that .NET does not support RPC/Literal, either.)
Anne
