Re: soap encoding

I just looked through the ebXML Messaging spec
(http://www.oasis-open.org/committees/ebxml-msg/documents/ebMS_v2_0rev_c.pdf
) and could find no reference to an ebXML SOAP encoding. The only mention of
encoding that I found in the spec referred to the XML encoding (in the
document XML prolog: encoding=UTF-8).

The ebXML Messaging system passes application payload as attachments. As
such, you wouldn't use the SOAP runtime to encode the payload. It's up to
the application to encode the payload. The actual SOAP contents (the ebXML
SOAP headers and the ebXML manifest that gets passed in the SOAP body) are
encoded via doc/literal based on the
http://www.oasis-open.org/committees/ebxml-msg/msg-header-2_0.xsd schema.

Back to the original question:

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
serializers.

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.

Anne

> Date:    Sun, 4 Aug 2002 20:28:24 -0700
> From:    Dick Brooks <[email protected]>
> Subject: Re: soap encoding
>
> I believe the ebXML Message Service specification defines a
> broadly accepted
> doc/literal SOAP encoding.
>
>
>
>
> Dick Brooks
> Systrends, Inc
> 7855 South River Parkway, Suite 111
> Tempe, Arizona 85284
> Web: www.systrends.com <http://www.systrends.com>
> Phone:480.756.6777,Mobile:602-684-1484,eFax:240-352-0714
>
>
> -----Original Message-----
> From: Discussion of implementing SOAP applications today
> [mailto:[email protected]]On Behalf Of Sam
> Sent: Sunday, August 04, 2002 7:51 PM
> To: [email protected]
> Subject: [SOAP] 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
>
> You can read messages from the SOAP archive, unsubscribe from SOAP, or
> subscribe to other
> DevelopMentor lists at http://discuss.develop.com.
>
> You can read messages from the SOAP archive, unsubscribe from
> SOAP, or subscribe to other
> DevelopMentor lists at http://discuss.develop.com.
>

You can read messages from the SOAP archive, unsubscribe from SOAP, or subscribe to other
DevelopMentor lists at http://discuss.develop.com.