June 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1115) Broken datamodel when a detached ProcInst is saved

by Britt Miner (JIRA)

Broken datamodel when a detached ProcInst is saved -------------------------------------------------- Key: JBPM-1115 URL: http://jira.jboss.com/jira/browse/JBPM-1115 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2 Reporter: Britt Miner Assigned To: Tom Baeyens I've noticed (accidentally of course, -ahem-) that if you attempt to call jbpmContext.save(processInstance) on a pi that was loaded outside of the current session, Hibernate will save a new pi with a new Id--however it will reference the same rootToken, etc. as the original pi, and all kinds of unexpected behavior quietly ensues. Of course, loading a fresh copy of the pi immediately before you do anything with it avoids the problem; however, a lot of serious data integrity hangs on remembering to do that every time. (for instance, when a pi being viewed in a UI is injected into an action component, the programmer must remember to load up a fresh copy before working on it.) Since failing to re-load a detached pi can result in what seems to be a broken jBPM data model, jBPM should probably be doing something itself to avoid the problem. I think there are possibly two ways to prevent this from happening: 1) Simply changing the HibernateSaveOperation.save(processInstance) method to saveOrUpdate() seems to perform cleanly. 2) Do a check on the pi, and throw an error if it doesn't belong to the current hibernate session. -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1173) Fork Node doesn't support conditions on Transitions

by Britt Miner (JIRA)

Fork Node doesn't support conditions on Transitions --------------------------------------------------- Key: JBPM-1173 URL: http://jira.jboss.com/jira/browse/JBPM-1173 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2 Reporter: Britt Miner Assigned To: Tom Baeyens Documentation does not clearly provide any limits to where conditions on Transitions can be used, but the Fork Node doesn't support Transition conditions. For instance <fork name='FORK_1' > <transition name='t1' to='NODE_A'> <condition>#{false}</condition> </transition> <transition name='t2' to='NODE_B'/> </fork> will fail with a "transition condition #{false} evaluated to 'false'" error when the fork attempts to take transition 't1'. Why provide for this? Someone might want to: <fork name='FORK_1' > <transition name='startMyProject' to='...'/> <transition name='orderEngine to='...'> <condition>#{needsEngine}</condition> </transition> <transition name='orderWheels to='...'> <condition>#{needsWheels}</condition> </transition> ...etc... </fork> Correcting the issue is as simple as making the following change to org.jbpm.graph.node.Fork.java: // BRITT --replace the following line with the code below // to check conditions before adding valid transitions... //transitionNames = getLeavingTransitionsMap().keySet(); //original line Iterator iter = leavingTransitions.iterator(); while (iter.hasNext()) { Transition candidate = (Transition) iter.next(); String conditionExpression = candidate.getCondition(); if (conditionExpression != null) { Object result = JbpmExpressionEvaluator.evaluate(conditionExpression, executionContext); if (Boolean.TRUE.equals(result)) { transitionNames.add(candidate.getName()); } }else{ transitionNames.add(candidate.getName()); } } if (transitionNames.size() == 0) { transitionNames.add(this.getDefaultLeavingTransition().getName()); this.getDefaultLeavingTransition().removeConditionEnforcement(); log.warn("All transition conditions have evaluated to 'false'. Taking the default transition."); } // --BRITT -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1114) If a node is set to async the console does not seem to report which node has the focus in the process.

by Kurt Stam (JIRA)

If a node is set to async the console does not seem to report which node has the focus in the process. ------------------------------------------------------------------------------------------------------ Key: JBPM-1114 URL: http://jira.jboss.com/jira/browse/JBPM-1114 Project: JBoss jBPM Issue Type: Bug Reporter: Kurt Stam Assigned To: Tom Baeyens Priority: Minor Attachments: async=true on all nodes..jpg I'm deploying 1 jPDL with all nodes having the attribute async="true" and one where I left the node synchronous. When I now start the a process instance the async one does not show a focus on the "Review Order" while the other one does. See the attached screenshots. -- 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, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-1126) ProcessDeifnition substates load into top level node list

by James Violette (JIRA)

ProcessDeifnition substates load into top level node list --------------------------------------------------------- Key: JBPM-1126 URL: http://jira.jboss.com/jira/browse/JBPM-1126 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.1.4 Environment: ANY Reporter: James Violette Assigned To: Tom Baeyens Priority: Minor The ProcessDefinition.hbm.xml nodes list must have a where clause to avoid loading substate nodes into the top level node list. The released nodes list definition <list name="nodes" cascade="all"> <cache usage="nonstrict-read-write"/> <key column="PROCESSDEFINITION_" /> <list-index column="NODECOLLECTIONINDEX_" /> <one-to-many class="org.jbpm.graph.def.Node" /> </list> should be <list name="nodes" cascade="all" where="superstate is null" > <cache usage="nonstrict-read-write"/> <key column="PROCESSDEFINITION_" /> <list-index column="NODECOLLECTIONINDEX_" /> <one-to-many class="org.jbpm.graph.def.Node" /> </list> -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1133) the query findActiveNodesByProcessInstance doesn't find active nodes in the root token

by jerome tellier (JIRA)

the query findActiveNodesByProcessInstance doesn't find active nodes in the root token -------------------------------------------------------------------------------------- Key: JBPM-1133 URL: http://jira.jboss.com/jira/browse/JBPM-1133 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: jerome tellier Assigned To: Tom Baeyens Priority: Minor the query findActiveNodesByProcessInstance has the condition "token.parent is not null", but if the token is the root token his parent is null. the query needs certainly also a "distinct". -- 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, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-1242) publish pvm api and examples online

by Tom Baeyens (JIRA)

publish pvm api and examples online ----------------------------------- Key: JBPM-1242 URL: http://jira.jboss.com/jira/browse/JBPM-1242 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens to get more community feedback -- 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, 1 month

3
7
0 / 0

[JBoss JIRA] Created: (JBPM-1256) review VariableDefinitionImpl.getSourceValue

by Tom Baeyens (JIRA)

review VariableDefinitionImpl.getSourceValue -------------------------------------------- Key: JBPM-1256 URL: http://jira.jboss.com/jira/browse/JBPM-1256 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: PVM Reporter: Tom Baeyens Fix For: PVM 1.0 beta1 verify if Guillaume's updates make sense in the bigger picture -- 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, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-1181) document 'end-complete-process' attribute on end-state

by Ronald van Kuijk (JIRA)

document 'end-complete-process' attribute on end-state ------------------------------------------------------ Key: JBPM-1181 URL: http://jira.jboss.com/jira/browse/JBPM-1181 Project: JBoss jBPM Issue Type: Task Reporter: Ronald van Kuijk Assigned To: Tom Baeyens Using an end-state in a leg of fork does not end the process. It ends the token (and parent tokens if it was the last active child). If one really wants to end the full process, the end-complete-process attribute should be used on the end-state. This is not documented anywhere, but it should. -- 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, 2 months

4
7
0 / 0

[JBoss JIRA] Created: (JBPM-1294) Integrate console tests in automated testrun

by Thomas Diesler (JIRA)

Integrate console tests in automated testrun -------------------------------------------- Key: JBPM-1294 URL: http://jira.jboss.com/jira/browse/JBPM-1294 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jBPM jPDL 3.2.4 -- 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, 2 months

3
11
0 / 0

[JBoss JIRA] Created: (JBPM-1297) Integrate all tests in automated QA

by Thomas Diesler (JIRA)

Integrate all tests in automated QA ----------------------------------- Key: JBPM-1297 URL: http://jira.jboss.com/jira/browse/JBPM-1297 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: jPDL 3 Reporter: Thomas Diesler Fix For: jBPM jPDL 3.2.4 -- 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, 2 months

2
9
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues June 2008