[jboss-dev-forums] [Design of JBoss jBPM] - create start task inconsistency

tom.baeyens@jboss.com do-not-reply at jboss.com
Mon Aug 14 04:43:39 EDT 2006


"Jeff" wrote : 
  | | Start-state taskInstances are not created when the 
  | | start-state is entered. 
  | | 
  | | Instead,
  | | 
  | | TaskInstance taskInstance = 
  | | taskMgmtInstance.createStartTaskInstance();
  | | 
  | | must be performed by the client (the jBPM web app does this).
  | | 
  | | This seems to be inconsistent, in that task-nodes create 
  | | taskInstances if a task is specified in the task-node 
  | | definition (and create-task is not set to false). Also 
  | | problematic for a Seam application, in that there is not easy 
  | | way to tell Seam that this process definition has start tasks 
  | | and must be handled differently.
  | | 
  | | However it is not clear how to fix this. Start-nodes are not 
  | | "entered" or "executed" like other nodes, so there is no good 
  | | place to hang the invocation to 
  | | taskMgmtInstance.createStartTaskInstance.
  | | 
  | | Thoughts?
  | 

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

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



More information about the jboss-dev-forums mailing list