I understand that it is part of the SOAP XML structure, but the parsing done by Axis is inefficient due to generation of intermediate DOM objects that are a major cause of performance degredation and are absolutely redundant since there are other mechanisms of gettting data out of a payload and should be left to the business implementation to check for well-formedness.
No doubt, but even so. it's *still* not an Axis issue. To avoid parsing the body as an optimization, Axis would need to do a (weird) preprocessing with the XML to strip out the body before handing the remaining envelope off to the XML parser.
I really do think SwA is where you should start, even though it seems to be deprecated in favour of embedded payloads - but that strikes me as fashion more than sense.
CDATA is not even to considered an option since the payload will not support charset outside of ISO8859 during the parse routines of a UTF-8 charset.
Yep, good catch.
