&quot;Kevin.Conner(a)jboss.com&quot; wrote : "jim.ma" wrote : The mainly intention for it is we can make the Request/Response class as a subclass of esb Message. | But why is this a requirement? What is wrong with using POJOs and populating a created message? | When we want to put the below class in request message body , which message body should I use ? RawBody, MapBody or ObjectBody? org.jboss.esb.Request { | public String foo; | public byte[] bar; | } what will be added to message body ? body.add(requestObj) or body.add("foo", "foovalue"); body.add("bar", "barvalue"); If later is right, use the subclass can simplify adding the filed value in message body.(move the add(key, value) code to parent class and subclass can put all field value sby calling this.setMessageBodys()). &quot;Kevin.Conner(a)jboss.com&quot; wrote : | To fit in with the current code it would be better if it was handled as follows. | payloadProxy = new MessagePayloadProxy(config) | and then something like the following | | | Message message = MessageFactory.getInstance().getMessage(); | | payloadProxy.setPayload(message, <incoming request>); | | ... evaluate pipeline ... | | Object response = payloadProxy.getPayload(responseMessage); | | | Does payloadProxy get payLoad from the default location ? If there are multiple objects in message body , does it also work? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148594#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...