replace implicit tokens with implicit termination disablement in the scope lifecycle ------------------------------------------------------------------------------------ Key: BPEL-203 URL: http://jira.jboss.com/jira/browse/BPEL-203 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Components: Engine Affects Versions: jBPM BPEL 1.1 beta 1 Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 beta 2 Early jBPM 3 versions did not provide a mechanism to prevent implicit token termination. Such a mechanism was required to implement the event handling semantics of BPEL scopes. Early jBPM BPEL versions introduced so-called "implicit" tokens that prevented the scope token from being terminated when a) the nested activity completed, but event handling was still in progress or b) event handling completed, but the activity was still in progress. The behavior described in the previous paragraph remained in latter jBPM BPEL versions. It must be updated to take advantage of the mechanism to prevent implicit termination introduced in latter jBPM versions. This will save the creation of 1-2 tokens per executed scope. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira