Re: transaction identifier in method call/response

From: Anne Thomas Manes <anne_at_MANES.NET>
Date: Tue, 17 Sep 2002 10:06:21 -0400


You can place identifiers/signatures/etc wherever you think it's most
convenient to do so, but according to the SOAP spec, the SOAP Body SHOULD
contain your application payload and the SOAP Header SHOULD contain
information that the application (or the SOAP runtime) needs to process the

You might find these references interesting:

- WS-Security (see
defines a SOAP extension that you can use to pass security information (user
tokens, signatures, keys, etc.) in a SOAP header. It also specifies how to
encode signed or encrypted data in the SOAP Body.

And this group of three:
BPEL4WS: Business Process Execution Language for Web Services
    (represents the merging of WSFL and XLANG)

WS-Coordination: Describes an extensible framework for providing
    protocols that coordinate the actions of distributed applications.

WS-Transaction: Describes coordination types that are used with the
    extensible coordination framework described in WS-Coordination.


> -----Original Message-----
> From: Public discussion on JAX-RPC
> [mailto:JAXRPC-INTEREST_at_JAVA.SUN.COM]On Behalf Of Rum Pel
> Sent: Monday, September 16, 2002 12:31 AM
> Subject: transaction identifier in method call/response
> The JAX-RPC FAQ states that a method call or response
> may carry a unique transaction identifier or digital signature.
> Can somebody give me more details of this? Where does such
> information go in a SOAP message - in the header or in the
> body itself?
> thanks
> --rp
> _________________________________________________________________
> Join the world?s largest e-mail service with MSN Hotmail.