In the earlier section on the View Node you will notice a message fragment on the left. This was captured during the incoming request leg of the journey. You should notice that the contacts element, containing the posted information for a GetContacts operation request has been wrapped within the /mvc:eForm/mvc:Data section. This is the default message wrapper used by WebMaker. It can be changed if required, but should not be necessary. The /mvc:eForm/mvc:Control section of the message contains non-payload control information such as the name of the requested controller, the next page name, etc. One important point to note is that WebMaker will also place unbound form elements within this section. This may be because some bindings are invalid or designed intentionally to appear in the Control section.
Within each controller and also the View Node and the Access Service nodes you have full access to the wrapped information. The main information of interest typically is the payload contained within the /mvc:eForm/mvc:Data element. Once the message has flowed through the view node and the controller to the access service, it will be re-wrapped using a SOAP Wrapper by default. This is performed by transforming the contents of the /mvc:eForm/mvc:Data into /soap:Envelope/soap:Body. This transformation is achieved using file SOAP_Wrapper.xsl. You can modify this to suit your exact soap wrapping requirements.
The reverse wrapping and unwrapping is performed during the outgoing response leg of the message flow. Essentially the /mvc:eForm wrapper is used to wrap and provide a containing element for the unstructured data captured from the client pages and also to contain WebMaker domain-specific information during execution within XPlatform. The /soap:Envelope is used for SOAP and HTTP requests to remote services. These wrappers and the mappings between them can be altered, but should not be necessary is most cases.
