yes, but:
1. It is too low level to be a true clean / simple client API. Instead of
something as simple as:
"process.findWorkInProgress()"
developers need to know to:
a. cast the processInstance,
b. get a hold of NodeInstances
c. iterate over them
d. filter out what nodes are in progress
e. query DB for the data associated with those nodes
2. There is no "one view" to all the wait nodes, because of the
sub-processes, so this solution gets even hairier when there are multiple
subflows, subflows within subflows, etc..
That is why it is rather odd that you think these low level APIs are enough.
/Anatoly
--
View this message in context:
http://n3.nabble.com/Resuming-the-Flow-SESSION-ID-PROCESS-INSTANCE-ID-WORKITEM-ID-tp607507p693482.html
Sent from the Drools - User mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
