[jboss-jira] [JBoss JIRA] Commented: (BPEL-240) upgrade bpel 1.1 compensate to bpel 2 compensate/compensateScope

[Alejandro Guizar (JIRA)]

    [ http://jira.jboss.com/jira/browse/BPEL-240?page=comments#action_12356015 ] 
            
Alejandro Guizar commented on BPEL-240:
---------------------------------------

Actually the above description is incorrect! <compensate /> invokes compensation for all completed nested scopes, NOT the enclosing scope. The enclosing scope has not completed and thus CANNOT be compensated!

The current implementation of Compensate is wrong. It tries to compensate the enclosing scope and rightfully gets the following exception:

java.lang.IllegalStateException: ScopeState[faultingWithHandler=4]: transition=compensate
	at org.jbpm.bpel.graph.exe.ScopeState.newStateException(ScopeState.java:94)
	at org.jbpm.bpel.graph.exe.ScopeState.compensate(ScopeState.java:52)
	at org.jbpm.bpel.graph.exe.ScopeInstance.compensate(ScopeInstance.java:154)
	at org.jbpm.bpel.graph.basic.Compensate.execute(Compensate.java:45)

because a ScopeInstance in a state other than "completed" is not permitted.

> upgrade bpel 1.1 compensate to bpel 2 compensate/compensateScope
> ----------------------------------------------------------------
>
>                 Key: BPEL-240
>                 URL: http://jira.jboss.com/jira/browse/BPEL-240
>             Project: JBoss jBPM BPEL
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Engine
>    Affects Versions: jBPM BPEL 1.1 beta 3
>            Reporter: Alejandro Guizar
>         Assigned To: Alejandro Guizar
>             Fix For: jBPM BPEL 1.1.GA
>
>
> In BPEL 1.1, compensation for a specific *nested* scope can be explicitly invoked using the compensate activity. Omitting the scope attribute invokes the default compensation behavior for the *enclosing* scope.
> <compensate scope="ncname"? />
> In BPEL 2, it was recognized that the presence or absence of the scope attribute led to very different behavior. As a result, a new activity was introduced to cope with the nested scope compensation case:
> <compensateScope target="ncname" />
> Default compensation is invoked just like BPEL 1.1:
> <compensate />
> We must extend the XSL template and the activity parsers to accommodate the changes in BPEL 2.

-- 
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