The article is spot on when it says that rpc/encoded is the source of significant interoperability challenges. But it's not accurate when it says, "the Document/literal style in which developers have to assume everything, including the serialization and de-serialization of the XML-based SOAP messages".
This is a common misconception -- that if you use document/literal, then the application must programmatically map Java objects to XML and construct the SOAP messages. Axis (and most other JAX-RPC implementations) supports automatic serialization and deserialization of SOAP messages for you when using document/literal -- using either the "WRAPPED" style or the "DOCUMENT" style. For best interoperability, I recommend using "WRAPPED" style. It also simulates the RPC/encoded programming model. Anne On 6/24/05, Carolyn Vo <[EMAIL PROTECTED]> wrote: > > > > http://www.developerfusion.co.uk/show/4694/3/ > > > > Basically, the summation is that RPC SOAP encoding is one of major > roadblocks for Web services interoperability. Is this a valid statement? I > have used rpc/encoded for my web services, and I haven't had problems yet > with Java and .NET interoperability. However, I am also not using complex > types as return types, nor am I passing in any complex types as parameters > to any methods. > > > > Anyone have any thoughts or comments on this article? > > > > Thanks, > > Carolyn
