There are plenty of ways to combine jBPM and JbossESB capabilities. A few have been explored, and a preliminary version some classes has been added to the trunk in order to facilitate interoperation between both products. Unit tests and a quickstart to show a two way end to end simple interaction are under construction and will soon be commited as well. AbstractCommandVehicle: yet another 'standard' way of packaging a command, it's arguments and return values. It has a toCommandMessage() method that renders an ESB Message containing the command information, paired with a constructor that takes a Message. It could also used without packaging/extracting it from an esb message, just with setters and getters. JbpmCommandVehicle: specializes it for interaction with Jbpm. It is intended to work in conjunction with the JbpmCommandInterpreter class, that can be used as an action in the ESB. A few jBPM commands have been implemented, and we would hope more will be included as the community feeds ideas to complete what is now a very small subset of all possible interactions with jBPM. If we do things properly it should be possible to standardize on this format for all interactions originated in ESB aware classes and jBPM, including responses to these requests. I am a beginner with only superficial knowledge of the jBPM internals and intricacies, consequently it is very important that contributors with deeper jBPM exposure provide their feedback to point out mistakes, suggest better ways of tackling this matter, and contribute some code . We will appreciate ideas on some base (may be abstract) classes that implement org.jbpm.graph.def.ActionHandler, and that can make it easier to interact with the ESB from the jBPM world. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4018776#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...