What you are talking about is an experimental feature that allows the rules to control the
process execution.
http://docs.jboss.org/jbpm/v5.1/userguide/ch17.html
How to do this is still not documented that well there are some aspects we have to work on
to make it simpler - hence why it's really move of an internal experimental feature.
You'd mostly have to speak to kris, who would take you through some unit tests. Find
him on irc:
http://www.jboss.org/drools/irc
When we've tidied it up, simplified it and are happier with it, we'll document it
and promote it for general purpose use.
Mark
On 8 Nov 2012, at 19:19, dunnlow <dunnlow(a)yahoo.com> wrote:
Thank you for the information / update.
I notice that almost all of the examples that I find are user task based (or
more specifically, NOT event-based, which is my use case). I am planning to
inform a process largely (but not entirely) with events. Short of having a
signal and gateway for every node, I don't see a way of make a jBPM process
event based (ie pausing at nodes until certain events/rules are satisfied).
Is this not a good use case for jBPM?
-- salaboy, I'll be waiting anxiously for that book ;-)
Thanks again. -J
--
View this message in context:
http://drools.46999.n3.nabble.com/Is-Flow-jBPM-dying-on-the-vine-tp402073...
Sent from the Drools: User forum mailing list archive at
Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users