Re: soap encoding.

From: Anne Thomas Manes <anne_at_MANES.NET>
Date: Mon, 05 Aug 2002 10:42:57 -0400

You might want to use a customized encoding if the SOAP encoding doesn't
meet your needs (i.e., you have some really complex types that aren't
addressed in the SOAP encoding), although in terms of interoperability, I
think you're better off using SOAP encoding with your own custom

If you want to be able to perform a schema validation on your messages, you
should use literal. As long as your RPC parameters are relatively flat,
there's no reason why you can't use RPC/literal. (But in this case, why not
just use doc/literal?) If you want to pass cyclic object graphs, you'll find
it much easier to use RPC/encoded.

I can't really think of a reason to use document/encoded.


> -----Original Message-----
> From: Public discussion on JAX-RPC
> [mailto:JAXRPC-INTEREST_at_JAVA.SUN.COM]On Behalf Of Sam
> Sent: Sunday, August 04, 2002 10:49 PM
> Subject: soap encoding.
> Can anyone think of a use case where a custom encoding scheme,
> other than teh default SOAP encoding would be requireed
> Where would one use a document/encoded or rpc/literal format , if at all
> Thanks
> /s