isn't a fork a splitted spoon?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911800#3911800
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911800
---
This SF.net em
by split I meant fork :-p
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911772#3911772
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911772
---
This SF.net email i
right, one subprocess per token
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911761#3911761
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911761
---
This SF.net e
Bug is in JIRA: JBPM-462
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911749#3911749
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911749
---
This SF.net email is
tom, processes with no wait states are rare. Our process do have wait states
wrapped in decision nodes. Because all the decisions are negative, the
subprocess doesn't have anything to do so it ends.
One more thing, how could you have multiple subprocess per token?
If you want to start multiple
Yes, agreed, that might be the best solution. But, here's another problem. The
subprocess-end event is useless if the context's token does not have the
subProcessInstance field set.
See, token.subprocessinstance is not a persistent field, which means that if
the subprocess is started, then load
the real solution will be to keep a list of all the subprocesses in the
ProcessInstance (in a member that is not persisted with hibernate)
then the save operation can take this list and store the subprocesses properly.
this technique is similar as with e.g. logs, timers, ...
regards, tom.
Vie
you might have a very specific situation where subprocessing fails.
in case you have multiple subprocesses that don't have wait states. because
the token has only 1 pointer to the current subprocess.
we might fix this later but this has no priority atm. although we also want to
support proce
Well, came up with another workaround, used the subprocess-created and
subprocess-end events in the process-state node to save the process instance
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911559#3911559
Reply to the post :
http://www.jboss.com/ind
