When you mention something generic as a WorkItem, we don't know how the implementation will be. Remember that, WorkItems are extension points. So, depending on your extension is the implementation of the mechanism that you will use. Simple than that. We implement the WorkItem for Human tasks, (a concrete work item), where we include the mechanism to continue those workitems. Because we know the behavior of that. If we don't know we don't know the behavior looking concrete projects and uses cases we cannot give you more suggestions.. please provide them. (with code of course)
On Fri, Apr 2, 2010 at 11:17 AM, tolitius <webaka...@gmail.com> wrote: > > I see. So "When the process is in a wait state I must have a mechanism to > continue", why not have framework help me? > > What is the rationale behind that? > > Thank you, > /Anatoly > -- > View this message in context: > http://n3.nabble.com/Resuming-the-Flow-SESSION-ID-PROCESS-INSTANCE-ID-WORKITEM-ID-tp607507p693070.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 > -- - http://salaboy.wordpress.com - http://www.jbug.com.ar - Salatino "Salaboy" Mauricio -
_______________________________________________ rules-users mailing list rules-users@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users
