In reference to the message posted, I am specifically interested in knowing if there has been any development done in addressing the issue around parsing of the XML payload sent in the SOAP body by the AXIS runtime. I see a design issue here with respect to performance since parsing of the xml payload in a doc-lit style service does not add any value/functionality in performing AXIS related tasks. I see that the Message object has the ability to store different formats of the SOAP body element, inputstream, string, bytes etc. Why isn't the content of the SOAP body element left alone instead of parsing it.
Because the body element and its contents are inside the envelope's root element. That is, this is a SOAP/XML issue, not an Axis issue. And if you're sending XML, you should parse it to ensure well-formedness or you'll break your receiver.
Is there an alternative other than using attachments ? where the payload will not be parsed ? Please advise.
The MIME people got this right a long time ago. If you don't want to parse a SOAP payload, don't put it in a SOAP envelope. I would use SwA, or multipart mime. CDATA is a hack.
