> Should we stick with Axis 1.1 and rpc/encoded style for a while longer, > or should we make the jump to Axis 1.2 and doc/literal? Or should we > make the jump to Axis 1.2 but stick with rpc/encoded style?
I was confused for a time regarding what implementation differences would exist between rpc/encoded and doc/literal. I had assumed that moving to doc/literal would require we abandon usage of Axis's internal marshalling capabilities. It is admittedly very handy to write server and client code in java that simply prepares data objects (generated from the wsdl) and submits those objects to stub/skeletons. I was pleased to learn that parameter marshalling does not HAVE to go away when one switches to doc/literal. So while that may be perfectly clear to you, it wasn't to me, and I wanted to cover that first in case that was part of the hesitation about moving to doc/literal. I believe where this issue becomes a no-brainer is where your system or domain already utilizes a well-understood xml message as input. Forms of Doc/literal allow you to essentially embed that xml message in the SOAP message. I've seen implementations that use doc/literal primarily because there was already a generally agreed-upon xml message for the transaction the web service was exposing. See the following, which I found somewhat useful in sorting this out: http://www-106.ibm.com/developerworks/webservices/library/ws-docstyle.html http://java.sun.com/developer/technicalArticles/xml/jaxrpcpatterns/ http://www.devchannel.org/webserviceschannel/03/07/11/2122220.shtml?tid=25&t id=38 http://www-106.ibm.com/developerworks/webservices/library/ws-soapenc/ **************************************************************************** This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. ****************************************************************************
