[JBoss JIRA] Created: (BPEL-242) <scope> not allowed to enclose a start activity
by Alejandro Guizar (JIRA)
<scope> not allowed to enclose a start activity
-----------------------------------------------
Key: BPEL-242
URL: http://jira.jboss.com/jira/browse/BPEL-242
Project: JBoss jBPM BPEL
Issue Type: Bug
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
According to BPEL 2, "a start activity is a <receive> or <pick> activity that is annotated with a createInstance="yes" attribute [...]. Non-start activities except <scope>, <flow>, <sequence> or <extensionActivity> MUST have a control dependency on a start activity".
In jBPM BPEL only <scope> and <flow> are allowed to contain a start activity. <scope> must be allowed as well.
--
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
16 years, 7 months
[JBoss JIRA] Created: (BPEL-241) provide a compensation example
by Alejandro Guizar (JIRA)
provide a compensation example
------------------------------
Key: BPEL-241
URL: http://jira.jboss.com/jira/browse/BPEL-241
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
The BPEL product needs a new example that demonstrates the compensation capabilities. Off the back of my head, I can think of a travel agency where customers book their flight, hotel and/or car. The agency gives them one combined bill. If they cancel their reservation, the agency has a cancellation fee on each requested service.
--
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
16 years, 7 months
[JBoss JIRA] Created: (BPEL-240) upgrade bpel 1.1 compensate to bpel 2 compensate/compensateScope
by Alejandro Guizar (JIRA)
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
16 years, 7 months
[JBoss JIRA] Created: (BPEL-235) Clean up composite activities
by Alejandro Guizar (JIRA)
Clean up composite activities
-----------------------------
Key: BPEL-235
URL: http://jira.jboss.com/jira/browse/BPEL-235
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
Implementation of NodeCollection methods in CompositeActivity subclasses is:
a) incorrect, some methods are broken and some allow things they shouldn't
b) inefficient, the underlying data structures are not exploited
c) incoherent, the view presented by the NodeCollection interface does not match the picture presented by concrete methods in CompositeActivity subclasses
Furthermore, method overriding is abused, resulting in a hard-to-understand hierarchy. Review overrides to determine if a better approach exist.
--
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
16 years, 7 months