SOAP message parsing redundancy with doc-lit services.

[Sharmin Choksey [comcast]]

This is a followup to the thread posted at http://www.mail-archive.com/[EMAIL PROTECTED]/msg09663.html,. Subject : "Accessing the XML in the SOAP message body" posted Feb-03.   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.   Doc-lit services fail to scale beyond 5 concurrent users with payloads of 150K with poor response times in contrast to sending the xml payload within CDATA where the parser will ignore such contents, scaling exponentially with response times in sub seconds.   Is there an alternative other than using attachments ? where the payload will not be parsed ? Please advise.   -Sharmin.