I am currently evaluating/learning jbpm(4.1). Since our application businness layer is running on a ejb-container, my thoughts are to use jbpm embedded as a library. Have a couple of questions regarding this infrastructure. Might be a bit long...but thanks in advance
a)First is this a valid solution. I did see some spring modules but it was for 3.x so I skipped it. My plan is to write a Facade Service(most likely accessible locally only) which exposes the service Process Engine etc
b)For simple processes in which each state is invoked by an external event looks like the above will work.
c) if I wanted to use the more complex stuff like timers, etc would the embedded library still be able to support. In Quartz, the schedule usually allows some thread management -- how does jbpm support similar functionality. Quartz schedulers do also support clustering and I think guarantees only one process locks the job and invokes it. Can i assume the same for jbpm?
thanks for now, might have more questions as we go.
a: Facade Service (Process Access Object) is a good idea
c: The jBPM documentation also states there is 'some' threadmanagement, regarding 'clustering': yes this works