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

[camunda]

Heiko wrote : 
  | Either you go for WS-HT or you don't. But it doesn't make sense to rip it apart and customize bits and pieces. You'd loose the benefit of the specification in the first place.
  | 

I do not agree.

Kris wrote : 
  | I don't think that you should either go for WS-HT or not at all
  | 

My opinion too! To support WS-HT is a good thing if you need a task component which supports WS-HT or if you want to use that as central HT component in your SOA.

But a lot of use cases face different requirements and there you need to adapt task lifecycle for your needs (but break WS-HT).

Kris wrote : 
  | you are confronted with logic that could best be represented using a business process and other logic where you would like to use rules. So in that sense it makes sense to integrate them. 
  | 

I agree on that. This is why integrating jbpm and drools is a very good idea! But I would keep seperation of concers, so state chart in jbpm and rules in Drools.

Ehm, and sorry Tom for somehow hijacking this thread ;-)

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

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