Comments on: “Wrapper”/”Non-wrapper” Web Service Styles – Things You Need to Know

By: Mike M. Lin

Mike M. Lin — Thu, 19 May 2011 16:12:27 +0000

Super explanation. I was really confused about this while reading Java Web Services Up and Running. The first example introducing wrapped styles shows the difference in SOAP request message. That threw me off, because later they show a detailed example creating a wrapped style client and an unwrapped style client from the same WSDL! Naturally, both clients produced the identically structured request messages. So if the difference between wrapped and unwrapped styles isn’t necessarily in the WSDL and isn’t in the request or response messages, then where is it? This article cleared it all up for me, so thanks.

By: alily

alily — Mon, 25 Oct 2010 12:27:10 +0000

hiphop alily……………………

By: aduket

aduket — Fri, 28 May 2010 10:05:38 +0000

@”RPC style message definitions in WSDL have to use schema types”

This is wrong; Document style message definitions have to use XSD types.

By: Francesco

Francesco — Wed, 11 Nov 2009 22:52:43 +0000

This is a very interesting article… and also very useful to me, thanks. :-)

By: Watch Year One Online Free

Watch Year One Online Free — Sat, 20 Jun 2009 20:00:48 +0000

This is quite a up-to-date information. I think I’ll share it on Twitter.
p.s. Year One is already on the Internet and you can watch it for free.

By: Alexander Ananiev

Alexander Ananiev — Tue, 28 Nov 2006 15:40:01 +0000

Tom, I don’t use Axis2 myself, but judging from the documentation, “-uw” will force the “non-wrapper” style. “wrapper” can’t be forced since it should be generated automatically based on the criteria defined in JAX-RPC/JAX-WS specs. In fact, forcing it would not be a good idea since in this case you would have to explicitly map the wrapper element to the operation name. The idea of the “wrapper” is that a SOAP engine can rely on a simple naming convention for un-marshalling.

Regards,
Alexander.

By: Tom Nguyen

Tom Nguyen — Mon, 27 Nov 2006 01:30:16 +0000

That’s a great article! We are using axis 2, by default the wsdl2Java generate the document literal if the operation name different from element name, Do you know which option that I can force axis 2 to generate wrapped style?
Thanks

By: MyArch » Schema Compliance is the Key to Interoperability

MyArch » Schema Compliance is the Key to Interoperability — Thu, 23 Nov 2006 22:35:39 +0000

[...] Many “wrapper” service implementations use positional parameter binding, as I described in my previous post. This allows a service provider to accept messages will never validate against the schema. Then, certain changes in implementation (a different binding mechanism, switching from “wrapper” to “non-wrapper”), could all of a sudden start causing issues for clients that have never had any problems before. [...]