This content has been marked as final. Show 1 reply
So, just to make it clear to me, the general idea of the jbpm-reliance project is to prepare the conf,classes,dependencies,annotations etc that will make the jbpm-jpdl runtime run in the jboss microcontainer without using the jboss
application server, is that right?
The main idea that I have is to be able to introduce flow into bean's lifecycle.
Currently you have pre-defined states - ..., described, instantiated, configured, ..., installed.
You can of course add new states - see DeployersImpl - but I want to make it more flexible / extensible and transparent at the same time.
a) perhaps squeezing in a fork of states, and later on a join
b) having human interaction to confirm your bean can move fwd
c) add additional behavior when leaving/arriving to state
And jBPM already addresses all these issues.
a) flexible flow definition
b) tasks, actors + transparent persistency
c) actions, execution, ...
Perhaps most of the things can be implemented just as a simple facade on top of jBPM's PVM. I need to investigate this further.