The current jBPM issues are related but it is just part of a bigger issue with jBPM. The current codebase appears to be based on the premise that each jBPM instance is standalone and co-located with the code running within the system but this is not valid in an environment like the AS which can rely on a shared codebase. The notion of a jBPM deployer is an interesting one and is something that I have mentioned in the past. It is likely to be the keystone in any real solution to these issues. What is really missing is for jBPM to define a proper lifecycle for the processes in a shared environment, including support for artifacts which can be undeployed/redeployed. This will necessitate proper support for classloader hierarchies, scoped deployments etc. I should also add that I do not think that ESB is the correct location for this work, although we would have to modify some code to fit in with whatever is decided. Kev View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179330#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...