[JBoss JIRA] Created: (BPEL-212) Modularize package org.jbpm.bpel.def
by Alejandro Guizar (JIRA)
Modularize package org.jbpm.bpel.def
------------------------------------
Key: BPEL-212
URL: http://jira.jboss.com/jira/browse/BPEL-212
Project: JBoss jBPM BPEL
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: jBPM BPEL 1.1 beta 2
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1
The package org.jbpm.bpel.def concentrates all activity definitions and has become monolithic. The proposal is breaking it as follows:
org.jbpm.bpel.graph.def: Core concepts, including BpelDefinition, Activity, CompositeActivity and LinkDefinition.
org.jbpm.bpel.graph.basic: Basic activities
org.jbpm.bpel.graph.struct: Structured activities
org.jbpm.bpel.graph.scope: Scope activity plus fault, compensation, event and termination handlers
For consistency, org.jbpm.bpel.exe becomes org.jbpm.bpel.graph.exe. Because the number of execution objects is small, there is no need to break this package.
--
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
17 years, 5 months
[JBoss JIRA] Created: (BPEL-214) provide a fault handling example
by Alejandro Guizar (JIRA)
provide a fault handling example
--------------------------------
Key: BPEL-214
URL: http://jira.jboss.com/jira/browse/BPEL-214
Project: JBoss jBPM BPEL
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1
The BPEL product needs a new example that demonstrates the fault handling capabilities. The sample purchase order process from the BPEL4WS 1.1 specification is a good candidate. Not only it demonstrates fault handling, but also asynchronous interaction with partner services and the use of the <flow> activity to model multiple concurrent paths of execution.
--
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
17 years, 5 months
[JBoss JIRA] Created: (BPEL-205) employ inheritance instead of enumeration to distinguish sublanguage uses
by Alejandro Guizar (JIRA)
employ inheritance instead of enumeration to distinguish sublanguage uses
-------------------------------------------------------------------------
Key: BPEL-205
URL: http://jira.jboss.com/jira/browse/BPEL-205
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
ScriptDefinition has a property of enum type Use to distinguish the intent of the sublanguage snippet in the context where it appears. Collecting this information is important because each use has different semantics.
Inheritance models the relationship between the diverse uses better from an object-oriented perspective. Therefore, the Use enumeration has to be dropped in favor of a Snippet hierarchy.
--
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
17 years, 5 months
[JBoss JIRA] Created: (BPEL-203) replace implicit tokens with implicit termination disablement in the scope lifecycle
by Alejandro Guizar (JIRA)
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
17 years, 5 months
[JBoss JIRA] Created: (BPEL-198) prevent stale object state exceptions
by Alejandro Guizar (JIRA)
prevent stale object state exceptions
-------------------------------------
Key: BPEL-198
URL: http://jira.jboss.com/jira/browse/BPEL-198
Project: JBoss jBPM BPEL
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: jBPM BPEL 1.1 beta 1
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Priority: Critical
Fix For: jBPM BPEL 1.1 beta 2
After incorporating optimistic concurrency control, Hibernate frequently throwed StaleObjectStateExceptions due to the integration service's enabling of RequestListeners as soon as the process instance reached an inbound message activity. When the expected message comes before the transaction that reached the activity ends, nothing prevents JMS from delivering it. The unavoidable outcome of this situation is a StaleObjectStateException.
We must find a way to enable RequestListeners after the originating transaction ends.
--
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
17 years, 5 months