[jboss-dev-forums] [Design of JBoss jBPM] - Re: task assignee vs owner

[camunda]

Hi Kris,

I know about DroolsFlow and such but to be honest: I am still a bit scared about some of the stuff integrated in Drools today ;-) But maybe this is just because of the lack of time to have a deeper look into the source code.

In my opinion: Drools = BRM + CEP -> Yes, cool! But BPM? I think there is a lot of stuff around in BPM which makes it a sperate topic which should be targeted by a BPM software (like BPMN -> technical Model mapping, Simulation, BAM & Reporting, Persistence with the different kind of flavours, ...). 

With the Human Task Component I agree with you that effort should not be duplicated! But I don't see the value of drools developing the second BPM solution as well. And I really would like to see "one JBoss answer" to this, meaning a clear distinction when to use Drools and when to use jbpm. And how to combine. 

Kris wrote : 
  | Do we want to work an a shared human task component or not, and if so, what are the requirements / restrictions? Then we can decide what would be the best way to move forward?
  | 

+1 for the shared task component supporting WS-HT (but not being tied to it, means having a pluggable life cycle). Kris, is there an easy example using your task component and how to change life cycle?

Kris wrote : 
  | I'm talking about collaboration
  | 

Would make sense to me, but I still think exactly one project (or lets say one project manager) must be responsible to enable this.

Hopefully this doesn't get to political? But it is indeed a topic which is in my mind for some time already, as being someone who likes both projects very much in their respective fields! So I would like to see some progress in this area....

Cheers
Bernd

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210427#4210427

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210427