From Traditional Integration to Composition – Enterprise Business Services - Applied SOA Patterns on the Oracle Platform - page 243

This modification can be done on the MessageHeader Java object if the receiver is one,
or after combining the message header and message body together in an individual trans-
formation step within an execution plan if we have multiple TP receivers.
We can say the same about the Acknowledge object. Initially, the sender was only one,
Oracle e-Business Suite, and the Acknowledge was predefined for this application.
However, as it was described in the business case, quite soon, other internal applications
discovered the benefits of this Message Broker and the transformation of the Acknow-
ledge message becomes necessary. Luckily, standardization of the Acknowledge mes-
sage is easier than Message Header, as all applications are internal.
You can understand the structure of the Acknowledge object from the overridden
toString() function, which we recommend that you should have for every entity
class. The following code is for object structure only, as you can be better off with Apache
commons for the implementation of the toString() function, by using
ToStringBuilder.reflectionToString(this) for instance:
/*
* @webmethod
*/
public String toString(){
return getClass().getName()