January 2007 - jboss-jira - Jboss List Archives

[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, 10 months

2
4
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, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (BPEL-207) module definitions file is reparsed every time a bpelDefinition is instantiated

by Alejandro Guizar (JIRA)

module definitions file is reparsed every time a bpelDefinition is instantiated ------------------------------------------------------------------------------- Key: BPEL-207 URL: http://jira.jboss.com/jira/browse/BPEL-207 Project: JBoss jBPM BPEL Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Similarly to the scenario sketched in BPEL-206, each bpelDefinition parses, upon creation, the module definitions file listing the default ModuleDefinitions that should accompany it. We have to parse the resource in advance and keep a reference to the loaded classes so that the bpelDefinition 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, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (BPEL-201) Release 1.1 beta 3

by Alejandro Guizar (JIRA)

Release 1.1 beta 3 ------------------ Key: BPEL-201 URL: http://jira.jboss.com/jira/browse/BPEL-201 Project: JBoss jBPM BPEL Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Engine Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 beta 3 -- 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, 10 months

2
8
0 / 0

[JBoss JIRA] Created: (BPEL-202) rename correlation initiate mode 'rendezvous' to 'join'

by Alejandro Guizar (JIRA)

rename correlation initiate mode 'rendezvous' to 'join' ------------------------------------------------------- Key: BPEL-202 URL: http://jira.jboss.com/jira/browse/BPEL-202 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Components: Documents Affects Versions: jBPM BPEL 1.1 beta 1 Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 beta 2 The WS-BPEL issue 202 [http://www.choreology.com/external/WS_BPEL_issues_list.html#Issue202] describes the change. The change is already in the BPEL 2.0 schema distributed with JBoss BPEL. -- 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, 10 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, 10 months

2
3
0 / 0

[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

18 years, 10 months

2
2
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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (BPEL-197) integers are represented with a decimal point when used as source content

by Alejandro Guizar (JIRA)

integers are represented with a decimal point when used as source content ------------------------------------------------------------------------- Key: BPEL-197 URL: http://jira.jboss.com/jira/browse/BPEL-197 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 When the evaluation of an expression results in a Number value, and this value is latter used to compute a source content TII, the resulting TII contains a decimal point and a trailing zero. The BPEL 2 spec, section 8.4.2, states: > Once the information item is returned from the source, a TII will be computed based upon it. [...] This is analogous to the XPath 1.0 string() function. However, jBPM BPEL converts an object of a type other than node-set to a string by calling the toString() method. This method does not match the behavior of the string() function for a number. In particular, the XPath 1 spec, section 4.2 states: > if the number is an integer, the number is represented in decimal form as a Number with no decimal point and no leading zeros, preceded by a minus sign (-) if the number is negative -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-503) Compiler Throwing an exception on generics

by jasonc411 (JIRA)

Compiler Throwing an exception on generics ------------------------------------------ Key: JBRULES-503 URL: http://jira.jboss.com/jira/browse/JBRULES-503 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 3.0.4 Environment: JBoss Rules 3.0.4, antlr-2.7.6.jar, antlr-3.0ea8.jar, commons-jci-core-1.0-406301.jar, commons-jci-eclipse-3.2.0.666.jar, core-3.2.0.666.jar, drools-compiler-3.0.4.jar, drools-jsr94-3.0.4.jar, jsr94-1.1.jar, stringtemplate2.3b6.jar Reporter: jasonc411 Assigned To: Mark Proctor #created on: Sep 15, 2006 package com.ca.data.dsrules #list any import classes here. import com.ca.data.model.base.DataSourceEnum; import com.ca.data.model.issuer.Issuer; import java.util.ArrayList; import java.util.List; import com.ca.data.model.Data; import com.ca.data.datasubs.utils.JMSServiceLocator; import com.ca.data.jms.JMSTextMessageSender; function void save(Issuer issuer){ JMSTextMessageSender cleanQueue = JMSServiceLocator.getTextSender("SomeServer", "SomeTopic"); Data data = new Data(); List<Issuer> myIssuers = new ArrayList<Issuer>(); myIssuers.add(issuer); Data.setIssuerList(myIssuers); cleanQueue.simpleSend(issuer); } rule "Persist Validated Data" agenda-group "Data In" no loop salience 1 when issuer : Issuer(dataSource == DataSourceEnum.SomeSource, id != -1) then System.out.println("Validated"); save(issuer); end -- 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, 10 months

3
7
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2007