Cleaning up the callback EPR.... The current callback into an awaiting BPM process is via this chunk of XML injected into the reply-to: <wsa:From xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">... xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb"&g... esb="BODY_CONTENT" bpm="theBody"/>&lt;/esbToBpmVars></jbossesb:esbToBpmVars><jbossesb:jbpmTokenId xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb"&g... xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb"&g... xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb"&g... xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb"&g... xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb"&g... It is injected via a custom action like so: message.getHeader().getCall().setTo(epr); where epr equals the content listed above. This is essentially our "cookie" for managing the conversation between ESB & the process instance. This chunk of XML is a bit unwieldy, especially if must go out to a business partner or actual client application. It also requires a custom action to be created. An easier to use correlation solution should be created so that it works more like the older model of signal (out of the box action) & token id (a simpler "cookie"). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197744#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...