I want to be able to deploy and access Jbpm processes outside of my application context in order to try and separate business processes (the BA's domain) from the application (the developer's domain).
I had presumed that this would be possible given the existence of the JBPM web console but cannot work out how to access the JbpmConfiguration of the process host.
I noticed that the JbpmService MBean provided is essentially a stub, so I tried to bind the current JbpmConfiguration instance to JNDI by modifying the mbean implementation. However, despite JbpmConfiguration being marked as serializable I get a NotSerializableException on java.lang.ThreadLocal when I try to bind the configuration.
a) Is it possible to separate the process and application domains like I am trying to do?
b) If so, how should I go about it?
c) If not, what is the point of deploying anything using the JBPM Web Console?
try to use hibernate.cfg.xml configured against the db server that is used as jBPM storage, you will be able to access remote jBPM processes.
If you read some of Tom Baeyens blog entries, you'll see that the separation of process and application or even the separation of the process on the business level and the one on the implementation level is not so strict. We, the company I work for, also come to this conclusion when using jBPM. aamof, it feels good that this separation is to that distinct, more close cooperation resulted in better functionality.