Package com.sun.xml.ws.security.opt.impl.message

Class MessageWrapper

  • public class MessageWrapper
extends Message
    Author:
    K.Venugopal@sun.com

    • Method Detail

      • hasHeaders

        public boolean hasHeaders()
        Returns true if headers are present in the message.
        Specified by:
        hasHeaders in class Message
        Returns:
        true if headers are present.

      • getHeaders

        public HeaderList getHeaders()
        Gets all the headers of this message.

        Implementation Note

        Message implementation is allowed to defer the construction of MessageHeaders object. So if you only want to check for the existence of any header element, use hasHeaders().

        Specified by:
        getHeaders in class Message
        Returns:
        always return the same non-null object.

      • getAttachments

        public AttachmentSet getAttachments()
        Gets the attachments of this message (attachments live outside a message.)
        Overrides:
        getAttachments in class Message

      • hasAttachments

        protected boolean hasAttachments()
        Optimization hint for the derived class to check if we may have some attachments.
        Overrides:
        hasAttachments in class Message

      • isOneWay

        public boolean isOneWay​(@NotNull
                        WSDLPort port)
        Returns true if this message is a request message for a one way operation according to the given WSDL. False otherwise.

        This method is functionally equivalent as doing getOperation(port).getOperation().isOneWay() (with proper null check and all.) But this method can sometimes work faster than that (for example, on the client side when used with SEI.)

        Overrides:
        isOneWay in class Message
        Parameters:
        port - Messages are always created under the context of one WSDLPort and they never go outside that context. Pass in that "governing" WSDLPort object here. We chose to receive this as a parameter instead of keeping WSDLPort in a message, just to save the storage.

        The implementation of this method involves caching the return value, so the behavior is undefined if multiple callers provide different WSDLPort objects, which is a bug of the caller.

      • getPayloadLocalPart

        public String getPayloadLocalPart()
        Gets the local name of the payload element.
        Specified by:
        getPayloadLocalPart in class Message
        Returns:
        null if a Message doesn't have any payload.

      • getPayloadNamespaceURI

        public String getPayloadNamespaceURI()
        Gets the namespace URI of the payload element.
        Specified by:
        getPayloadNamespaceURI in class Message
        Returns:
        null if a Message doesn't have any payload.

      • hasPayload

        public boolean hasPayload()
        Returns true if a Message has a payload.

        A message without a payload is a SOAP message that looks like: 

         <xmp>
 <S:Envelope>
   <S:Header>
     ...
   </S:Header>
   <S:Body />
 </S:Envelope>
 </xmp>
        Specified by:
        hasPayload in class Message

      • readPayloadAsSource

        public Source readPayloadAsSource()
        Returns the payload as a Source object. This consumes the message.
        Specified by:
        readPayloadAsSource in class Message
        Returns:
        if there's no payload, this method returns null.

      • readAsSOAPMessage

        public javax.xml.soap.SOAPMessage readAsSOAPMessage()
                                             throws javax.xml.soap.SOAPException
        Creates the equivalent SOAPMessage from this message. This consumes the message.
        Specified by:
        readAsSOAPMessage in class Message
        Throws:
        javax.xml.soap.SOAPException - if there's any error while creating a SOAPMessage.

      • readPayloadAsJAXB

        public <T> T readPayloadAsJAXB​(javax.xml.bind.Unmarshaller unmarshaller)
                        throws javax.xml.bind.JAXBException
        Reads the payload as a JAXB object by using the given unmarshaller. This consumes the message.
        Specified by:
        readPayloadAsJAXB in class Message
        Throws:
        javax.xml.bind.JAXBException - If JAXB reports an error during the processing.

      • readPayloadAsJAXB

        public <T> T readPayloadAsJAXB​(Bridge<T> bridge)
                        throws javax.xml.bind.JAXBException
        Reads the payload as a JAXB object according to the given Bridge. This consumes the message.
        Specified by:
        readPayloadAsJAXB in class Message
        Returns:
        null if there's no payload.
        Throws:
        javax.xml.bind.JAXBException - If JAXB reports an error during the processing.

      • writeTo

        public void writeTo​(ContentHandler contentHandler,
                    ErrorHandler errorHandler)
             throws SAXException
        Writes the whole SOAP envelope as SAX events.

        This consumes the message.

        Specified by:
        writeTo in class Message
        Parameters:
        contentHandler - must not be nulll.
        errorHandler - must not be null. any error encountered during the SAX event production must be first reported to this error handler. Fatal errors can be then thrown as SAXParseException. SAXExceptions thrown from ErrorHandler should propagate directly through this method.
        Throws:
        SAXException

      • copy

        public MessageWrapper copy()
        Creates a copy of a Message.

        This method creates a new Message whose header/payload/attachments/properties are identical to this Message. Once created, the created Message and the original Message behaves independently --- adding header/ attachment to one Message doesn't affect another Message at all.

        This method does NOT consume a message.

        To enable efficient copy operations, there's a few restrictions on how copied message can be used.

        1. The original and the copy may not be used concurrently by two threads (this allows two Messages to share some internal resources, such as JAXB marshallers.) Note that it's OK for the original and the copy to be processed by two threads, as long as they are not concurrent.
        2. The copy has the same 'life scope' as the original (this allows shallower copy, such as JAXB beans wrapped in JAXBMessage.)

        A 'life scope' of a message created during a message processing in a pipeline is until a pipeline processes the next message. A message cannot be kept beyond its life scope. (This experimental design is to allow message objects to be reused --- feedback appreciated.)

        Design Rationale

        Since a Message body is read-once, sometimes (such as when you do fail-over, or WS-RM) you need to create an idential copy of a Message.

        The actual copy operation depends on the layout of the data in memory, hence it's best to be done by the Message implementation itself.

        The restrictions placed on the use of copied Message can be relaxed if necessary, but it will make the copy method more expensive.

        Specified by:
        copy in class Message

      • readPayloadAsJAXB

        public <T> T readPayloadAsJAXB​(XMLBridge<T> arg0)
                        throws javax.xml.bind.JAXBException
        Description copied from class: Message
        Reads the payload as a Data-Bond object This consumes the message.
        Specified by:
        readPayloadAsJAXB in class Message
        Returns:
        null if there's no payload.
        Throws:
        javax.xml.bind.JAXBException - If JAXB reports an error during the processing.