This content has been marked as final.
Show 5 replies
-
-
2. Re: Understanding JBPM
kukeltje Sep 17, 2007 1:13 PM (in response to dingo001)bumping posts, especially ones of just a few days old, is really not appreciated by some people in this forum.
Sometimes you do not get an answer because the answer is so obvious that people expect you to find out with a little investigation -
3. Re: Understanding JBPM
dingo001 Sep 17, 2007 1:30 PM (in response to dingo001)"kukeltje" wrote:
bumping posts, especially ones of just a few days old, is really not appreciated by some people in this forum.
Sometimes you do not get an answer because the answer is so obvious that people expect you to find out with a little investigation
did u ever get smacked as a kid? -
4. Re: Understanding JBPM
estaub Sep 17, 2007 2:12 PM (in response to dingo001)1. I cannot understand is how can I tie a workflow to a document. Would that be done in each process instance as a context variable that I pass to the process instance.
Yes2. If I want my webapp to be generic enough to accommodate any workflow definition then all that I perceive that I do in the webapp is to get the process instance and just call p.signal(). this would create token (or tokens in the case of forks) and processing can continue.
"generic enough to accommodate any workflow definition" is pretty vague - there are infinite degrees of freedom you could be talking about. You probably need to answer this for yourself.
-Ed Staub -
5. Re: Understanding JBPM
kukeltje Sep 17, 2007 3:07 PM (in response to dingo001)No ding, I was the one doing the smacking... but now we are on the subject... See the answers Ed gave? Soooooo obvious...