[jboss-dev-forums] [Design of JBoss jBPM] - Re: releasing 3.2.Beta1

[david.lloyd@jboss.com]

"jeffdelong" wrote : anonymous wrote : Also one question I have is this: when a process starts that does not have a task on the start state (and therefore, I presume, no reason to wait), should the token automatically proceed out of the start state? Right now the user must signal the token manually in this case.
  | 
  | In this situation the client should signal the token via the api, i.e, the web app should signal the token.

In this case I have to establish the criteria for signalling the token.  The start node might have multiple transitions, so I presume that I'd only signal if there is a default leaving transition (node.getDefaultLeavingTransition() != null).  The main thing that concerns me though is, how do we know that the start token isn't intended to be a wait state, for whatever reason.  In a normal Node, we rely on the execute() method to determine whether a transition is immediately taken or the Node is a wait state.  However, since StartState's execute() is an illegal operation (in other words, the Token is just pointed at the Node without calling execute()), you never "arrive" in the start state; therefore the start state node never has an opportunity to establish its intention.

My personal opinion is that the start state should be executed like any other node, but of course I'm probably missing critical background on the issue. :-)

I think the best I can do with what we've got now, is something like this: if (no start task instance && initial node has a default leaving transition) { signal the token along the default transition }

Make sense?

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

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