"kukeltje" wrote : I do not see strange things in here. There may be nothing 'strange', but I wasn't expecting multiple tokens to pass through any node.
I'm looking to use 'client base assignment' (see http://www.jboss.com/products/jbpm/docs/jpdl) and use jBPM as the execution engine. Since I then want to hang actions off the node-enter/leave events, I need to know which token is the 'active' execution path. In the example supplied, the root token that 'follows' the 't10' token is - in effect - creating a second execution path through the same node, unless there is some way to distinguish when the root token is the active token on the execution path and when it is not. (I am assuming that following the 'fork' that the root token - being the parent of the other 2 - is no longer the 'active' token'?) "kukeltje" wrote : The only thing that surprises me is that token.getName() is null for the root token.... Yeah, that threw me too. "kukeltje" wrote : What version of jBPM are you using? I'll try to reproduce tonight... btw I downloaded jbpm-jpdl-suite-3.2.2.zip View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131084#4131084 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131084 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
