Axis WSDD RPC style generates a WSDL RPC/encoded style service.
Axis WSDD Wrapped, Document, and Message styles generate a WSDL Document/Literal service.
Hence you can use Wrapped, Document, or Message style to improve .NET interop.
Wrapped and Document styles let Axis perform the serialization and deserialization of messages. Message style leaves the serialization process to the application. (Axis just hands your application the raw XML).
To summarize:
RPC:
- produces a parameterized RMI interface
- performs automatic serialization
- uses RPC/encoded
WRAPPED:
- produces a parameterized RMI interface
- performs automatic serialization
- uses doc/literal
DOCUMENT:
- produces a non-parameterized RMI interface (client must wrap parameters in a JavaBean) - performs automatic serialization
- uses doc/literal
MESSAGE:
- uses a call interface passing XML
- applications must process XML
- uses doc/literal
Anne
At 09:46 PM 10/6/2003 -0400, you wrote:
IIRC, message style is an artifact of the wsdd not wsdl. You can (and should) use document style with axis to achieve interop with .NET but its not guaranteed. You'll have to craft the schema types to make things friendly to both code generators which means you'll have to write the wsdl (at least tweak a generated copy) yourself.
Jim Murphy Mindreef, Inc.
atul wrote:
Is "message" style specific to Axis? If not, what can we specify in binding style in wsdl (since wsdl specs let's you specify only rpc or document)? Also, can we achieve interoperability (for instance with a .Net client understanding wsdl) by hosting my service as 'message' style in axis? tia atul.
__________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com
