[jbpm-issues] [JBoss JIRA] Updated: (JBPM-1394) Token ID

Token ID -------- Key: JBPM-1394 URL: https://jira.jboss.org/jira/browse/JBPM-1394 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public(Everyone can see) Components: API Reporter: Thomas Diesler Fix For: API Unscheduled A Token will have a unique identity, called a TokenId set, that can be used to distinguish multiple Tokens that may exist because of concurrent Process instances or the dividing of the Token for parallel processing within a single Process instance. The parallel dividing of a Token creates a lower level of the TokenId set. The set of all levels of TokenId will identify a Token. A Start Event generates a Token that must eventually be consumed at an End Event (which may be implicit if not graphically displayed). The path of Tokens should be traceable through the network of Sequence Flow, Gateways, and activities within a Process. There MUST NOT be any implicit flow during the course of normal Sequence Flow (i.e., there should always be either Sequence Flow or a graphical indicator, such as an Intermediate Event to show all the potential paths of Tokens). An example of implicit flow is when a Token arrives at a Gateway, but none of the Gates are valid, the Token would then (implicitly) pass to the end of the Process, which occurs with some modeling notations.Tokens can also be directed through exception handling Intermediate Events, which act like a forced end to an activity. Note: A Token does not traverse the Message Flow since it is a Message that is passed down those Flow (as the name implies).