SOAP Envelopes and schemas should be handled more natively by the current ESB Tooling. To illustrate the difficulty for the developers when it is not handled natively: When a Web Service transformation is made with Smooks, the entire SOAP Envelope needs to be imported, additional items like security may change based on the service contract, this will cause issues for more than the most basic example. In addition, A Content Base Router could use the Soap Envelope without the need for casts of Message body to Classes, which can cause many exceptions during runtime. The XSLT Actions could also use the entire SOAP Envelope as well. Tooling should be available to import the SOAP Envelope and the defined body and Security Headers etc.

the 3 attached screenshots hope to show the need for SOAP Native support.