wrapped style

["DZIEMBOWSKI,KINGA (HP-NewJersey,ex2)" <ki...@hp.com>]

Hi,
I like to get more info on the "rapped style" Axis is supporting.
I scanned mailing list, and docs and still looking for more details. 
What is the origin of this style? Microsoft and compatibility with .NET?
WS-I? Recommendation from any other standards? Is "wrapped style" axis idea
or it is considered by other Web Services Platform providers?

What is the wsdl definition for the "wrapped style" service in respect for
the result of the operation invocation?
Should the result be wrapped this same way the rpc result is wrapped?
Is there any example of "perfect" wsdl for wrapped style service
demonstrating the definition for input and output messages?

Lets assume somebody would defines the WSDL describing the service. Follows
the WS-I recommendation to use document/lit style rather that rpc. The
nature of the service is to invoke remotely the operations.
What will be the set of rules to define wsdl for such service to be consider
"wrapped" style. The assumption is that implementation do not exist. We are
dealing with top-down web services creation: wsdl is defined first as a
contract interface.

I will appreciate to have as much info on this subject as possible, the best
with the WS-I context and the industry trends in solving those problems. Any
links pointing for more info will be great help.

Regards,
Kinga Dziembowski

------------------------------------

Kinga Dziembowski
Web Services Management Operation
HP OpenView Division
856.638.6065
kinga.dziembowski@hp.com

RE: wrapped style

[Wes Moulder <we...@themindelectric.com>]

"wrapped" style doc/lit is the greatest bugaboo of WSDL.  In the
beginning, the folks over at Microsoft wanted messages to take the form
of document/literal, but offer the binding between SOAP and c# in terms
of c# classes/objects.  Thus, they "wrapped" rpc into a document, and
followed a specific format for detecting that the server had done this,
allowing the client to "unwrap" the rpc call.  This allows you to use
intermediaries that don't care about the object orientedness of the
message to apply strict schema rules to validate and process the data
where required.  The utility of doing this is the impetus behind the
WS-I drive toward doc/lit and the removal of rpc/enc (specifically, the
encoded part).

Well, in keeping with .NET's view on language binding, WhiteMesa, TME,
Axis, PocketSOAP and others reverse engineered what .NET was doing and
offered the same form of language binding for their services and
clients.  This allows you to publish a method "add( int arg1, int arg2
)" in C# and consume it as the same in Java, or perl or COM, without
really bothering with the SOAPy abstraction of the service.  (without
this, the same call would end up as add( AddObject arg ) or add( Element
input ))

The secret behind what is and isn't wrapped is a) the message has 1 part
which has an element which is defined as an anonymous complex type and
b) the part's name is generally "parameters".

Hope that helps,
--Wes

-----Original Message-----
From: DZIEMBOWSKI,KINGA (HP-NewJersey,ex2)
[mailto:kinga.dziembowski@hp.com] 
Sent: Tuesday, April 29, 2003 2:53 PM
To: 'axis-dev@ws.apache.org'
Subject: wrapped style

Hi,
I like to get more info on the "rapped style" Axis is supporting.
I scanned mailing list, and docs and still looking for more details. 
What is the origin of this style? Microsoft and compatibility with .NET?
WS-I? Recommendation from any other standards? Is "wrapped style" axis
idea
or it is considered by other Web Services Platform providers?

What is the wsdl definition for the "wrapped style" service in respect
for
the result of the operation invocation?
Should the result be wrapped this same way the rpc result is wrapped?
Is there any example of "perfect" wsdl for wrapped style service
demonstrating the definition for input and output messages?

Lets assume somebody would defines the WSDL describing the service.
Follows
the WS-I recommendation to use document/lit style rather that rpc. The
nature of the service is to invoke remotely the operations.
What will be the set of rules to define wsdl for such service to be
consider
"wrapped" style. The assumption is that implementation do not exist. We
are
dealing with top-down web services creation: wsdl is defined first as a
contract interface.

I will appreciate to have as much info on this subject as possible, the
best
with the WS-I context and the industry trends in solving those problems.
Any
links pointing for more info will be great help.

Regards,
Kinga Dziembowski

------------------------------------

Kinga Dziembowski
Web Services Management Operation
HP OpenView Division
856.638.6065
kinga.dziembowski@hp.com