anonymous wrote : And I get the feeling that Human task Management is more in the
direction of BPM than BRM, so I see jBPM responsible for it. And Drools shouldn't even
need persistence in the most common use cases for a Rule Engine, different to jbpm.
|
Bernd, you might not be aware, but Drools as a platform is moving towards a Business Logic
integration Platform (BLiP), combining rules with processes and complex event processing.
So we're talking about BRM + BPM + CEP. In that context, a human task component makes
sense (in the restricted BRM case it is useful but I agree, a less common requirement).
Drools Flow is the process engine integrated into the platform for process execution:
https://hudson.jboss.org/hudson/job/drools/lastSuccessfulBuild/artifact/t...
I've proposed the idea of an independent JBoss Human Task component about half a year
ago, that's why I'm a little disappointed jBPM is now seems to be moving towards
adding their custom implementation without discussing the alternatives.
Kris
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210418#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...