July 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (BPEL-220) Introduce distribution module

by Alejandro Guizar (JIRA)

Introduce distribution module ----------------------------- Key: BPEL-220 URL: http://jira.jboss.com/jira/browse/BPEL-220 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Components: Engine Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 The introduction of an external repository in jBPM 3.2 brought changes in the way the distribution is built. We need to introduce a BPEL distribution module, similar to the jPDL distribution module located in jpdl/dist. -- 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

18 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (BPEL-210) compatibility broken with the axis-based stack in jboss 4.0.3 and below

by Alejandro Guizar (JIRA)

compatibility broken with the axis-based stack in jboss 4.0.3 and below ----------------------------------------------------------------------- Key: BPEL-210 URL: http://jira.jboss.com/jira/browse/BPEL-210 Project: JBoss jBPM BPEL Issue Type: Bug 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 -- 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

18 years, 5 months

2
3
0 / 0

[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

18 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (BPEL-211) update user guide to include new features

by Alejandro Guizar (JIRA)

update user guide to include new features ----------------------------------------- Key: BPEL-211 URL: http://jira.jboss.com/jira/browse/BPEL-211 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Components: Documents Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 beta 2 -Describe the simplified deployment process -Document time-driven activities -- 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

18 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (BPEL-209) Introduce a default destination/connection factory to ease deployment of new processes

by Alejandro Guizar (JIRA)

Introduce a default destination/connection factory to ease deployment of new processes -------------------------------------------------------------------------------------- Key: BPEL-209 URL: http://jira.jboss.com/jira/browse/BPEL-209 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Components: Engine Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 beta 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

18 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (BPEL-213) termination handling

by Alejandro Guizar (JIRA)

termination handling -------------------- Key: BPEL-213 URL: http://jira.jboss.com/jira/browse/BPEL-213 Project: JBoss jBPM BPEL Issue Type: Sub-task Reporter: Alejandro Guizar Assigned To: Alejandro Guizar -- 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

18 years, 5 months

2
4
0 / 0

[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

18 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (BPEL-206) activity readers file is reparsed every time a bpelReader is instantiated

by Alejandro Guizar (JIRA)

activity readers file is reparsed every time a bpelReader is instantiated ------------------------------------------------------------------------- Key: BPEL-206 URL: http://jira.jboss.com/jira/browse/BPEL-206 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 The activity readers file, located by default in org/jbpm/bpel/xml/activity.readers.xml, contains the activity tag names available to the process along with the ActivityReader capable of unmarshalling the XML element to a definition object. Each bpelReader contains its own set of activityReaders. To instantiate them, it parses the activity readers file, retrieves the ActivityReader class names, loads the classes and instantiates them. This is wasteful. We need to parse the resource and keep a reference to the loaded classes in advance so that the bpelReader instance only instantiates the classes. -- 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

18 years, 5 months

2
4
0 / 0

[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

18 years, 5 months

2
2
0 / 0

[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

18 years, 5 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2007