com.bea.wli.sb.transports
Interface TransportMessageContext

All Known Subinterfaces:

InboundTransportMessageContext, OutboundTransportMessageContext

All Known Implementing Classes:

CoLocatedMessageContext

public interface TransportMessageContext

Most message-oriented middleware (MOM) products treat messages as lightweight entities that consist of a header and a payload. The header contains fields used for message routing and identification; the payload contains the application data being sent In general, the transport-level message context consists of the following:

    TransportMessageContext
        message id           - unique id which identifies this message
        RequestMetaData      - meta data is not carried in the payload of
                               the message, but separately and is used
                               as the "context" for processing the message.
                               Examples of such information might be
                               transmitted in the mata data are the Content
                               Type header, security information, or locale
                               information. Base for the schema is defined in
                               TransportCommon.xsd, extensions defined
                               in each transport provider-specific schema
            headers          - request headers
        request body         - the payload of the request
        ResponseMetaData     - base for the schema is defined in
                               TransportCommon.xsd, extensions defined
                               in each transport provider-specific schema
            headers          - response headers
            response code    - success/failure status code
            response message - typically a one-line response message
        response body        - the payload of the response
    

Method Summary

String	getMessageId()
URI	getURI()

Method Detail

getURI

URI getURI()

Returns:

the base uri for to which the message was sent for an outbound message or from which the message was sent on an inbound message

getMessageId

String getMessageId()

Returns:

returns transport provider-specific message identifier. Ideally it should uniquely identify the message among other messages going through the ALSB runtime, However, ALSB does not depend on the message Id being unique. The message Id will be added to the message context and thus visible in the pipeline.