The message implementation for SOAP messages with
attachments. Messages for specific profiles will likely extend this
MessageImpl class and add more value for that particular profile.
author: Anil Vijendran (akv@eng.sun.com) author: Rajiv Mordani (rajiv.mordani@sun.com) author: Manveen Kaur (manveen.kaur@sun.com)
Construct a message from an input stream. When messages are
received, there's two parts -- the transport headers and the
message content in a transport specific stream.
Construct a message from an input stream. When messages are
received, there's two parts -- the transport headers and the
message content in a transport specific stream.
Parameters: contentType - The parsed content type header from the headers variable.This is redundant parameter, but it avoids reparsing this header again. Parameters: stat - The result of MessageImpl.identifyContentType(ContentType) overthe contentType parameter. This redundant parameter, but it avoidsrecomputing this information again.
Sniffs the Content-Type header so that we can determine how to process.
In the absence of type attribute we assume it to be text/xml.
That would mean we're easy on accepting the message and
generate the correct thing (as the SWA spec also specifies
that the type parameter should always be text/xml)
combination of flags, such as PLAIN_XML_CODE and MIME_MULTIPART_CODE.