May 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Commented: (JBPM-668) JPDL : Missing name on a transition in a decision make the conditions fail

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-668?page=comments#action_12412817 ] Ronald van Kuijk commented on JBPM-668: --------------------------------------- is this still an issue? I again vote for making the name required > JPDL : Missing name on a transition in a decision make the conditions fail > -------------------------------------------------------------------------- > > Key: JBPM-668 > URL: http://jira.jboss.com/jira/browse/JBPM-668 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.1.1 > Reporter: Ephemeris Lappis > Assigned To: Tom Baeyens > Priority: Minor > > Inside a decision node, if a transition has not a name attribute, the condition is not evaluated as expected. > For exemple, the following lines work : > <decision name="decision-x"> > <transition name="t1" to="node-a" /> > <transition name="t2" to="node-b"> > <condition expression="#{...}" /> > </transition> > </decision> > If the condition in the second transition matches, this transition is selected as expected. > But if the name of the transition is removed, the condition result is not correct : > <decision name="decision-x"> > <transition name="t1" to="node-a" /> > <transition to="node-b"> > <condition expression="#{...}" /> > </transition> > </decision> > In this case, the first transition seems to be always selected as default choice... > The name attribute of a transition seems optional, and no error is produced if it is not present : the conditional transition seems to be simply ignored... > Perhaps the following code excerpt from the class org.jbpm.graph.node.Decision is implied : > Iterator iter = decisionElement.elementIterator("transition"); > while (iter.hasNext()) { > Element transitionElement = (Element) iter.next(); > Element conditionElement = transitionElement.element("condition"); > if (conditionElement!=null) { > String conditionExpression = getConditionExpression(conditionElement); > if (conditionExpression!=null) { > String transitionName = transitionElement.attributeValue("name"); > if (decisionConditions==null) { > decisionConditions = new ArrayList(); > } > decisionConditions.add(new DecisionCondition(transitionName, conditionExpression)); > } > } > } > } > What occurs if the transition has no name attribute value ? -- 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

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-652) individual .project and .classpaths contain errors

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-652?page=all ] Ronald van Kuijk closed JBPM-652. --------------------------------- Resolution: Out of Date source structure changed > individual .project and .classpaths contain errors > -------------------------------------------------- > > Key: JBPM-652 > URL: http://jira.jboss.com/jira/browse/JBPM-652 > Project: JBoss jBPM > Issue Type: Bug > Environment: Eclipse 3.1.2 on windows > Reporter: Ronald van Kuijk > Assigned To: Tom Baeyens > > Importing the individual projects in e.g. a jbpm workspace does not work out of the box > The .classpath files of the individual projects contain references to jar files which are not in the repository or in a different place (jboss-j2ee.jar). to prevent duplicate work, I would suggest to 'export' the libraries from the 'build' project and make all other projects dependant on this one. The individual .classpath files are not needed then (afaik) > Besides that, the dependancies are wrong. If I import the individial parts, somew are called jbpm.something and some not, while the dependancies refere to something instead of jbpm.something -- 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

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-625) generate SQL scripts for databases

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-625?page=all ] Ronald van Kuijk closed JBPM-625. --------------------------------- Resolution: Out of Date already 'fixed'. The source generates ddl for many databases > generate SQL scripts for databases > ---------------------------------- > > Key: JBPM-625 > URL: http://jira.jboss.com/jira/browse/JBPM-625 > Project: JBoss jBPM > Issue Type: Task > Components: Documentation > Reporter: Koen Aers > Assigned To: Koen Aers > > This should be included in the database chapter of the documentation. -- 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

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-295) Dynamic/configurable sub-process via ProcessInvocationHandler

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-295?page=all ] Ronald van Kuijk closed JBPM-295. --------------------------------- Resolution: Done fixed some time ago by making the subprocess name accept an EL > Dynamic/configurable sub-process via ProcessInvocationHandler > ------------------------------------------------------------- > > Key: JBPM-295 > URL: http://jira.jboss.com/jira/browse/JBPM-295 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM 3.0, jBPM 3.0.1 > Reporter: rory steele > Assigned To: Tom Baeyens > Priority: Optional > > In move from version 2 to version 3, the ability to configure a process-state via a ProcessInvocationHandler has been lost. > This facility was very useful when used in a template definition and the using a process variable to control sub-process instantiation. As version 3 uses a sub-process element that only takes a process name (and optional version), template definitions are no longer possible - a new defintion would be required, differing only in the sub-process/@name element. > An option to have a choice between a sub-process element or a process-config element (similar to an ActionHandler/ProcessInvocationHandler) within a process-state node would be very useful. -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-250) policy implementation based on the identity component

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-250?page=all ] Ronald van Kuijk updated JBPM-250: ---------------------------------- Fix Version/s: jBPM 4.0 > policy implementation based on the identity component > ----------------------------------------------------- > > Key: JBPM-250 > URL: http://jira.jboss.com/jira/browse/JBPM-250 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Priority: Minor > Fix For: jBPM 4.0 > > > a policy implementation that verifies permissions against the currently authenticated user. the currently authenticated user should be looked up in the identity component database and the permissions can be collected from that database. -- 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

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-512) jBPM incorrectly accumulating variables for child token

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-512?page=all ] Ronald van Kuijk closed JBPM-512. --------------------------------- Resolution: Out of Date behaviour changed in 3.1 (or was it 3.2). If something like this is still an issue, create a new jira item > jBPM incorrectly accumulating variables for child token > ------------------------------------------------------- > > Key: JBPM-512 > URL: http://jira.jboss.com/jira/browse/JBPM-512 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.0.1, jBPM 3.0.2 > Environment: Running jBPM under JBoss 4.0.2, Sun JDK1.5.0_04, Fedora Core 4 Linux, although the problem is not specific to this environment > Reporter: Jim McMaster > Assigned To: Tom Baeyens > > I have a process which forks child tokens to handle parts of the processing. Each node in the process sets a "status" variable to indicate success or failure. Prior to the fork, a node set a STATUS_SUCCESS, then the children are forked off. > One of the children invokes a node which sets the status to STATUS_FAILURE, and invokes: > Code: > contextInstance.addVariables(variables, childToken) > At this point, the ContextInstance has two entries in TokenVariableMap, one for the parent and one for the child. Each variable map contains a status variable, but the values are different. > Later, I invoke: > Code: > contextInstance.getVariables(token) > When the variables come back, the status varable has the value STATUS_SUCCESS. In TokenVariableMap.collectAllVariables, the code gets all the variables for the child token, then adds the variables for the parent. This is great, except it does not check to see if the variable already exists in the HashMap, so the parent value overlays the child's. > It does not make sense fo the parent token's variables to override those of the child. -- 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

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-477) saveProcessInstance does not save Logs & Timers of Sub-Processes

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-477?page=all ] Ronald van Kuijk closed JBPM-477. --------------------------------- Resolution: Out of Date if still an issue in 3.2 please reopen > saveProcessInstance does not save Logs & Timers of Sub-Processes > ---------------------------------------------------------------- > > Key: JBPM-477 > URL: http://jira.jboss.com/jira/browse/JBPM-477 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.0.2 > Reporter: Bernd Ruecker > Assigned To: Tom Baeyens > > line 200 and following: > public void saveProcessInstance(ProcessInstance processInstance) { > try { > // saveProcessInstanceLogs(processInstance); > session.saveOrUpdate(processInstance); > jbpmSession.getLoggingSession().saveLogs(processInstance); > jbpmSession.getSchedulerSession().saveTimers(processInstance); > } catch (Exception e) { > log.error(e); > jbpmSession.handleException(); > throw new RuntimeException("couldn't save process instance '" + processInstance + "'", e); > } > } > this code does not save logs & timers of created sub-processes! -- 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

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-481) Invoking subprocess from ParentProcess issue

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-481?page=all ] Ronald van Kuijk closed JBPM-481. --------------------------------- Resolution: Out of Date > Invoking subprocess from ParentProcess issue > -------------------------------------------- > > Key: JBPM-481 > URL: http://jira.jboss.com/jira/browse/JBPM-481 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.0.2 > Environment: window XP professional, jbpm-starters-kit-3.1-alpha1 > Reporter: Srikanth Ramaswamy > Assigned To: Tom Baeyens > Original Estimate: 2 days > Remaining Estimate: 2 days > > Please refer the below url issue > http://www.jboss.com/index.html?module=bb&op=viewtopic&t=74227 > It's not trigger the subprocess when i put the statement below > > <process-state name="Parent Process"> > <sub-process name = "subProcess"/> > <variable name="Account Id" access="write" mapped-name="Account Id"></variable> > <variable name="Name" access="write" mapped-name="Name"></variable> > <transition name="tr1" to="Mainstate2"></transition> > </process-state> > > Let me what is wrong in my code or it's bug? > thanks > Srikanth -- 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

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-475) use aggregation for finding the latest definition

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-475?page=all ] Ronald van Kuijk closed JBPM-475. --------------------------------- Resolution: Out of Date second level caching from hibernate is used. Not an issue anymore > use aggregation for finding the latest definition > ------------------------------------------------- > > Key: JBPM-475 > URL: http://jira.jboss.com/jira/browse/JBPM-475 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > > performance optimization, the latest process definition can be fetched in 1 query instead of 2 by using select pd ... where max(...) -- 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

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-437) Fix unit tests for MySQL database...

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-437?page=all ] Ronald van Kuijk closed JBPM-437. --------------------------------- Resolution: Out of Date > Fix unit tests for MySQL database... > ------------------------------------ > > Key: JBPM-437 > URL: http://jira.jboss.com/jira/browse/JBPM-437 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Affects Versions: jBPM 3.0.1 > Environment: SuSE Linux 9,1, MySQL 4.0.18, release 32.20, JDK 1.4.2_01-b06 > Reporter: ErikEngerd2 > Assigned To: Tom Baeyens > Priority: Minor > Attachments: testresults.zip > > > 42 out of 195 testcases fail. The errors vary from 'cannot commit transaction' to actual assertions failing. > The problems might be just related to the test code but it could also be compatibility issues with MySQL, but this is not certain. > After running the test cases, running the mysql.drop.sql script on the database fails with the following message: > ERROR 1025 at line 1: Error on rename of './jbpmtest/JBPM_ACTION' to './jbpmtest/#sql2-427e-2dd' (errno: 152) > Therefore, it could also simply be an issue of a cleanup for a test case that fails (assuming that the test code does cleanup exactly as the script does). -- 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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues May 2008