May 2008 - jbpm-issues - Jboss List Archives

[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-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, 1 month

4
7
0 / 0

[JBoss JIRA] Created: (JBPM-1145) Loops realized via a decision node will eventually cause a StackOverflow Exception

by R??diger Schmitz (JIRA)

Loops realized via a decision node will eventually cause a StackOverflow Exception ---------------------------------------------------------------------------------- Key: JBPM-1145 URL: http://jira.jboss.com/jira/browse/JBPM-1145 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.1.4, jBPM 3.1 Reporter: R??diger Schmitz Assigned To: Tom Baeyens Executing a simple, iterative loop implemented with a decision node will cause a StackOverflowException (see below for stacktrace). Apparently the iterative calls are executing using recursive calls. This approach fails if a medium sized loop should be executed (a simple reproducing testcase only reached 161 loop iterations before failing). I see this implementation style as highly problematic when processing medium-sized quantities of input data... java.lang.StackOverflowError at java.lang.ClassLoader.findBootstrapClass(Native Method) at java.lang.ClassLoader.findBootstrapClass0(ClassLoader.java:891) at java.lang.ClassLoader.loadClass(ClassLoader.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:299) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at org.hibernate.loader.Loader.loadCollection(Loader.java:1926) at org.hibernate.loader.collection.CollectionLoader.initialize(CollectionLoader.java:71) at org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:520) at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:60) at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1627) at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:344) at org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:86) at org.hibernate.collection.PersistentList.iterator(PersistentList.java:115) at org.jbpm.graph.def.GraphElement.findExceptionHandler(GraphElement.java:358) at org.jbpm.graph.def.GraphElement.raiseException(GraphElement.java:326) at org.jbpm.graph.def.GraphElement.raiseException(GraphElement.java:343) at org.jbpm.graph.def.Node.execute(Node.java:332) at org.jbpm.graph.def.Node.enter(Node.java:316) at org.jbpm.graph.def.Node$$FastClassByCGLIB$$d187eeda.invoke(<generated>) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149) at org.hibernate.proxy.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:161) <snip>...a ton of repeating stacktraceelements omitted... <snap> at org.hibernate.proxy.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:161) at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$cb94b78_3.enter(<generated>) at org.jbpm.graph.def.Transition.take(Transition.java:119) at org.jbpm.graph.def.Node.leave(Node.java:382) at org.jbpm.graph.exe.ExecutionContext.leaveNode(ExecutionContext.java:136) at org.jbpm.graph.node.Decision.execute(Decision.java:145) at org.jbpm.graph.def.Node.enter(Node.java:316) at org.jbpm.graph.def.Node$$FastClassByCGLIB$$d187eeda.invoke(<generated>) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149) at org.hibernate.proxy.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:161) at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$cb94b78_3.enter(<generated>) at org.jbpm.graph.def.Transition.take(Transition.java:119) at org.jbpm.graph.def.Node.leave(Node.java:382) at org.jbpm.graph.def.Node.leave(Node.java:346) at org.jbpm.graph.exe.ExecutionContext.leaveNode(ExecutionContext.java:120) at com.atos.worldline.kams.workflow.pf.BusinessObjectAccessHandler.doExecute(BusinessObjectAccessHandler.java:114) at com.atos.worldline.kams.workflow.pf.AbstractBusinessMethodHandler.execute(AbstractBusinessMethodHandler.java:60) at org.jbpm.graph.def.Action.execute(Action.java:123) at org.jbpm.graph.def.Action$$FastClassByCGLIB$$7876e90e.invoke(<generated>) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149) at org.hibernate.proxy.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:161) at org.jbpm.graph.def.Action$$EnhancerByCGLIB$$889386ac_3.execute(<generated>) at org.jbpm.graph.def.Node.execute(Node.java:328) at org.jbpm.graph.def.Node.enter(Node.java:316) at org.jbpm.graph.def.Node$$FastClassByCGLIB$$d187eeda.invoke(<generated>) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149) at org.hibernate.proxy.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:161) at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$cb94b78_3.enter(<generated>) at org.jbpm.graph.def.Transition.take(Transition.java:119) at org.jbpm.graph.def.Node.leave(Node.java:382) at org.jbpm.graph.exe.ExecutionContext.leaveNode(ExecutionContext.java:136) at org.jbpm.graph.node.Decision.execute(Decision.java:145) at org.jbpm.graph.def.Node.enter(Node.java:316) at org.jbpm.graph.def.Node$$FastClassByCGLIB$$d187eeda.invoke(<generated>) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149) at org.hibernate.proxy.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:161) at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$cb94b78_3.enter(<generated>) at org.jbpm.graph.def.Transition.take(Transition.java:119) at org.jbpm.graph.def.Node.leave(Node.java:382) at org.jbpm.graph.def.Node.leave(Node.java:346) -- 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, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (JBPM-1095) jBPM project bug for SOA-P Platform bug SOA-196 (jBPM does not work with MySQL/Linux combo)

by Len DiMaggio (JIRA)

jBPM project bug for SOA-P Platform bug SOA-196 (jBPM does not work with MySQL/Linux combo) ------------------------------------------------------------------------------------------- Key: JBPM-1095 URL: http://jira.jboss.com/jira/browse/JBPM-1095 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Len DiMaggio Assigned To: Tom Baeyens jBPM project bug for SOA-P Platform bug SOA-196 (jBPM does not work with MySQL/Linux combo) http://jira.jboss.com/jira/browse/SOA-196 -- 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, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-1168) JMS message service fails under WebSphere 6.1

by Alejandro Guizar (JIRA)

JMS message service fails under WebSphere 6.1 --------------------------------------------- Key: JBPM-1168 URL: http://jira.jboss.com/jira/browse/JBPM-1168 Project: JBoss jBPM Issue Type: Support Patch Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Alejandro Guizar Assigned To: Tom Baeyens Priority: Critical See the full description in JBPM-1167. -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-1127) enterprise module testable against different databases

by Aleksandar Kostadinov (JIRA)

enterprise module testable against different databases ------------------------------------------------------ Key: JBPM-1127 URL: http://jira.jboss.com/jira/browse/JBPM-1127 Project: JBoss jBPM Issue Type: Task Affects Versions: jBPM 3.2.2 SOA 1 Reporter: Aleksandar Kostadinov Assigned To: Tom Baeyens Fix For: jBPM 3.2.2 SOA 1 jpdl module is testable against databases. identity module can be tested with different databases just altering the classpath to point to the database configuration. Now enterprise module can't be tested with different DB other than hsqldb that easy. The immediate problem is calling the package target in the jboss/configuration directory where it generates hypersonic database script by default. Changing the classpath of the JBPM taskdef task in jpdl/examples/build.xml to include database driver and database configuration produces an error: /qa/services/hudson/hudson_workspace/workspace/jboss-soa-platform-JBPM.3-testsuite/jbpm.3/jpdl/examples/build.xml:167: /qa/services/hudson/hudson_workspace/workspace/jboss-soa-platform-JBPM.3-testsuite/jbpm.3/jpdl/examples/target/db not found. So obviously changes to jpdl/examples will be needed as well database driver will need to be included into the generated package and I don't know what else. We need that change to test the SOA-P distribution of JBPM against the supported databases so the change needs to be applied to the SOA-P branch. -- 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, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPM-1180) describe in detail the ejb components and the enterprise service factories

by Alejandro Guizar (JIRA)

describe in detail the ejb components and the enterprise service factories -------------------------------------------------------------------------- Key: JBPM-1180 URL: http://jira.jboss.com/jira/browse/JBPM-1180 Project: JBoss jBPM Issue Type: Task Components: Documentation Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM jPDL 3.2.3 Describe the role and the configurable fields of the enterprise persistence, message and scheduler service factories. Document the function of the enterprise beans, the environment entries and the ejb, resource manager and message destination references. -- 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, 6 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues May 2008