Perhaps you're confusing document style with message style?
These terms get confusing because "document" style has two separate meanings in Axis. From the WSDL perspective (which is a standard terminology), document style refers to the way that a SOAP message is constructed, encoded, and formatted. In essence, it means that the message is constructed according to a specific XML Schema definition. But the WSDL document style does not impose any restrictions on how the SOAP engine delivers the data to the application. In order to achieve the best interoperability, you should always use WSDL document style.
From the WSDD perspective (which is not standard terminology), document style refers to the way that the SOAP engine delivers data to the application. WSDD document style means that Axis will convert the message into a Java object.
Message style is another type of WSDD perspective. In Axis, WSDD message style requires that you also use a WSDL document style. Axis transforms the message into a DOM.
By default .NET uses the equivalent of the WSDD wrapped style. My recommendation it to use Wrapped style by default unless you have a reason not to.
Anne
At 09:22 PM 4/5/2004, you wrote:
Sorry .. since both ends (Client and Server) deals directly with xml documents.
-----Original Message----- From: Pillai, Ranjith Sent: Monday, April 05, 2004 11:42 AM To: [EMAIL PROTECTED] Subject: RE: What are the advantages of Message style web services?
Hi Anne, Thanks for the information. I had the impression (read earlier in Axis User group) that Message Style services are better for interoperability since both deals directly with xml documents.
Thanks, Ranjith Pillai.
-----Original Message----- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Monday, April 05, 2004 10:07 AM To: [EMAIL PROTECTED] Subject: Re: What are the advantages of Message style web services?
If your application prefers to work with the information in it's native XML format, then you want to use the message style. For example, if your application simply wants to process one portion of a large document and then send it along in a workflow, it doesn't make sense to convert the entire document into Java objects, only to convert it back into the XML document again.
You also might want to use the message style for one-way or asynchronous
processing.
Anne
At 04:00 PM 4/5/2004, you wrote: >Hi Axis Community, > Could anyone shed some light on real advantages of Axis Message Style >services compared to passing in and out complex beans? > >Any help will be deeply appreciated, >Ranjith Pillai.
~~~~~~~~~~~~~~~~~~ Anne Thomas Manes VP & Research Director Burton Group
~~~~~~~~~~~~~~~~~~
Anne Thomas Manes
VP & Research Director
Burton Group
