July 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1360) Add QA for hsqldb

by Thomas Diesler (JIRA)

Add QA for hsqldb ----------------- Key: JBPM-1360 URL: http://jira.jboss.com/jira/browse/JBPM-1360 Project: JBoss jBPM Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- 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

15 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBPM-1284) create overview of community instruments

by Tom Baeyens (JIRA)

create overview of community instruments ---------------------------------------- Key: JBPM-1284 URL: http://jira.jboss.com/jira/browse/JBPM-1284 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens First we need to discuss which mailing lists, forums and wiki entry points will be used. Then we need to create a wiki page (or website as this should be static) that documents all these instruments and when to use them. -- 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

15 years, 10 months

5
6
0 / 0

[JBoss JIRA] Created: (JBPM-1318) update the new project infrastructure on the website

by Tom Baeyens (JIRA)

update the new project infrastructure on the website ---------------------------------------------------- Key: JBPM-1318 URL: http://jira.jboss.com/jira/browse/JBPM-1318 Project: JBoss jBPM Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Documentation Reporter: Tom Baeyens Assigned To: Koen Aers -- 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

15 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBPM-1246) create descriptions for all targets in build files

by Tom Baeyens (JIRA)

create descriptions for all targets in build files -------------------------------------------------- Key: JBPM-1246 URL: http://jira.jboss.com/jira/browse/JBPM-1246 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: PVM Reporter: Tom Baeyens Assigned To: Tom Baeyens -- 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

15 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-1163) Bad property format of hibernate.cfg.xml snippet in the user guide "Persistence" chapter

by Julien Kronegg (JIRA)

Bad property format of hibernate.cfg.xml snippet in the user guide "Persistence" chapter ---------------------------------------------------------------------------------------- Key: JBPM-1163 URL: http://jira.jboss.com/jira/browse/JBPM-1163 Project: JBoss jBPM Issue Type: Bug Components: Documentation Affects Versions: jBPM jPDL 3.2.2 Environment: CVS code JBPM 3.2.2 downloaded on 2008.04.18. Reporter: Julien Kronegg Assigned To: Tom Baeyens Priority: Optional Fix For: jBPM 3.3 In "/jbpm.3/jpdl/userguide/en/modules/persistence.xml" (CVS version 1.11), the "Managed transactions" section describe the most important configuration property from the "hibernate.cfg.xml" file as follow: "hibernate.connection.datasource= --datasource JNDI name-- like e.g. java:/DefaultDS" This property should be described using a XML format because the "hibernate.cfg.xml" in in XML format, for example: <property name="hibernate.connection.datasource"> --datasource JNDI name-- like e.g. java:/DefaultDS </property> Note: not tested on the german 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

15 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-1161) Bad references to property "jbpm.hibernate.cfg.xml" from the "jbpm.properties" file removed in JBPM 3.1

by Julien Kronegg (JIRA)

Bad references to property "jbpm.hibernate.cfg.xml" from the "jbpm.properties" file removed in JBPM 3.1 ------------------------------------------------------------------------------------------------------- Key: JBPM-1161 URL: http://jira.jboss.com/jira/browse/JBPM-1161 Project: JBoss jBPM Issue Type: Bug Components: Documentation Affects Versions: jBPM jPDL 3.2.2 Environment: CVS code of JBPM 3.2.2 obtained on 2008.04.18 Reporter: Julien Kronegg Assigned To: Tom Baeyens Priority: Minor The JBPM 3.2.2 user guide refers to the file "jbpm.properties", which was replaced by "jbpm.cfg.xml" in version JBPM 3.1 (see http://sourceforge.net/project/shownotes.php?release_id=383725&group_id=7... ). While references to "jbpm.properties" may be valid in a change log or a migration guide, they are not valid in the following files. /jbpm.3/jpdl/userguide/en/modules/persistence.xml (CVS version 1.11): In the sentence "Note that the hibernate configuration file resource is mapped in the property 'jbpm.hibernate.cfg.xml' and can be customized in the jbpm.cfg.xml", the "jbpm.hibernate.cfg.xml" property name should be replaced by "resource.hibernate.cfg.xml" (i.e. the property of the file snippet shown just below that sentence). /jbpm.3/jpdl/userguide/en/modules/configuration.xml (CVS version 1.7): The sentence "Location: <literal>hibernate.cfg.xml</literal> unless specified otherwise in the jbpm.hibernate.cfg.xml property in the jbpm.properties file." should be replaced by: "Location: <literal>hibernate.cfg.xml</literal> unless specified otherwise in the resource.hibernate.cfg.xml property in the jbpm.cfg.xml file." -- 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

15 years, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPM-1244) hardcoded keys for standard definitions map in class ProcessDefinition

by Hauke Rabe (JIRA)

hardcoded keys for standard definitions map in class ProcessDefinition ---------------------------------------------------------------------- Key: JBPM-1244 URL: http://jira.jboss.com/jira/browse/JBPM-1244 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Hauke Rabe in case you replace the "resource.default.modules" to define different definition classes, such as #org.jbpm.taskmgmt.def.TaskMgmtDefinition .........jbpm.taskmgmt.def.ExtendedTaskMgmtDefinition (extends TaskMgmtDefinition) ProcessDefinition#addDefinition(final ModuleDefinition moduleDefinition) uses the classname as definition map key, but for example the accessor ProcessDefinition#getTaskMgmtDefinition() uses hardcoded TaskMgmtDefinition.class as key. conclusion: the defined ExtendedTaskMgmtDefinition instance must use the TaskMgmtDefinition.class as key. -- 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

15 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPM-1206) ActionLog, SignalLog and TransitionLog hibernate mapping incorrect

by pieter martin (JIRA)

ActionLog, SignalLog and TransitionLog hibernate mapping incorrect ------------------------------------------------------------------ Key: JBPM-1206 URL: http://jira.jboss.com/jira/browse/JBPM-1206 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Environment: linux, jboss 4.2.2 Reporter: pieter martin When calling SignalLog.getChildren() it is always null. After some investigation I noticed that SignalLog extends CompositeLog in the java class and ProcessLog in the hibernate mapping files. i.e. in SignalLog.hbm.xml extends="org.jbpm.logging.log.ProcessLog" After editing the hibernate mapping file SignalLog.getChildren() returns the children. -- 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

15 years, 11 months

3
7
0 / 0

[JBoss JIRA] Created: (JBPM-1169) NPE in org.jbpm.graph.node.Decision.execute() when using transitions with null conditions migrated from JBPM 3.0

by Julien Kronegg (JIRA)

NPE in org.jbpm.graph.node.Decision.execute() when using transitions with null conditions migrated from JBPM 3.0 ---------------------------------------------------------------------------------------------------------------- Key: JBPM-1169 URL: http://jira.jboss.com/jira/browse/JBPM-1169 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Environment: win2000, JBPM 3.2.2, Jboss 4.2.2, Eclipse Europa 3.3 Reporter: Julien Kronegg Assigned To: Tom Baeyens A NullPointerException is raised by org.jbpm.graph.node.Decision.execute(ExecutionContext) if the table JBPM_DECISIONCONDITIONS row has null EXPRESSION_ field. The following conditions must meet: 1) initially, the user has a JBPM database in version 3.0 and a decision with conditional transitions 2) one of the conditional condition is cleared, which leads to setting the field EXPRESSION_ to null in the database 3) the JBPM database migrated from 3.0 schema to version 3.2 Note: the JBPM 3.2 database is (almost?) the same as the version 3.1, so the bug should also occur in version 3.1 (not tested). The exception is: Exception in thread "main" org.jbpm.graph.def.DelegationException at org.jbpm.graph.def.GraphElement.raiseException(GraphElement.java:387) at org.jbpm.graph.def.GraphElement.raiseException(GraphElement.java:378) at org.jbpm.graph.node.Decision.execute(Decision.java:148) at org.jbpm.graph.def.Node.enter(Node.java:319) at org.jbpm.graph.def.Transition.take(Transition.java:151) at org.jbpm.graph.def.Node.leave(Node.java:394) at org.jbpm.graph.node.StartState.leave(StartState.java:70) at org.jbpm.graph.exe.Token.signal(Token.java:195) at org.jbpm.graph.exe.Token.signal(Token.java:140) at org.jbpm.graph.exe.ProcessInstance.signal(ProcessInstance.java:271) at com.sample.TestDecisionNPE.main(TestDecisionNPE.java:53) Caused by: java.lang.NullPointerException at org.jbpm.jpdl.el.impl.JbpmExpressionEvaluator.translateExpressionToDollars(JbpmExpressionEvaluator.java:52) at org.jbpm.jpdl.el.impl.JbpmExpressionEvaluator.evaluate(JbpmExpressionEvaluator.java:38) at org.jbpm.jpdl.el.impl.JbpmExpressionEvaluator.evaluate(JbpmExpressionEvaluator.java:30) at org.jbpm.graph.node.Decision.execute(Decision.java:110) ... 8 more This bug can be tested using the following test case: package com.sample; import java.lang.reflect.Field; import java.util.ArrayList; import java.util.List; import org.jbpm.graph.def.ProcessDefinition; import org.jbpm.graph.def.Transition; import org.jbpm.graph.exe.ProcessInstance; import org.jbpm.graph.node.Decision; import org.jbpm.graph.node.DecisionCondition; public class TestDecisionNPE { public static final void main(String[] args) throws SecurityException, NoSuchFieldException, IllegalArgumentException, IllegalAccessException{ ProcessDefinition processDefinition = ProcessDefinition.parseXmlString( "<process-definition>" + " <start-state>" + " <transition to='d' />" + " </start-state>" + " <decision name='d'>" + " <transition name='one' to='a'>" + " <condition>#{a == 1}</condition>" + " </transition>" + " <transition name='two' to='b'>" + " <condition>#{a == 2}</condition>" + " </transition>" + " <transition name='three' to='c'>" + " <condition>#{a == 3}</condition>" + " </transition>" + " </decision>" + " <state name='a' />" + " <state name='b' />" + " <state name='c' />" + "</process-definition>"); // start-state. ProcessInstance processInstance = new ProcessInstance(processDefinition); // Update a transition decision condition as if it was on the old format // by setting the condition to null (i.e. no condition). // Build a decisionConditions list (emulates an old database from // JBPM 3.0, obsolete JBPM_DECISIONCONDITION table). List decision_conditions = new ArrayList(); decision_conditions.add(new DecisionCondition("one", null)); Decision decision = (Decision) processDefinition.getNode("d"); Field field = decision.getClass().getDeclaredField("decisionConditions"); field.setAccessible(true); field.set(decision, decision_conditions); // fire the transition (as we have an old decision condition set, org.jbpm.graph.node.Decision#execute will raise a NullPointerException). processInstance.signal(); } } The bug can be corrected using the following code in the execute() method (added lines ends with "JK") : // backwards compatible mode based on separate DecisionCondition's Iterator iter = decisionConditions.iterator(); while (iter.hasNext() && (transition==null)) { DecisionCondition decisionCondition = (DecisionCondition) iter.next(); if (decisionCondition.expression!=null) {//JK Object result = JbpmExpressionEvaluator.evaluate(decisionCondition.getExpression(), executionContext); if (Boolean.TRUE.equals(result)) { if (transition!=null) { transition.removeConditionEnforcement(); } String transitionName = decisionCondition.getTransitionName(); transition = getLeavingTransition(transitionName); } } else {//JK String transitionName = decisionCondition.getTransitionName();//JK transition = getLeavingTransition(transitionName);//JK }//JK Note that the JBPM 3.0.4 version had this check against null values. -- 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

15 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-1138) deleting a processInstance without any log related cause an Exception

by Dino Lupo (JIRA)

deleting a processInstance without any log related cause an Exception --------------------------------------------------------------------- Key: JBPM-1138 URL: http://jira.jboss.com/jira/browse/JBPM-1138 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.1.4 Environment: Windows, Linux, JBoss AS 4.2.2 GA Reporter: Dino Lupo Assigned To: Tom Baeyens When deleting process instances calling graphSession.deleteProcessInstance(processInstance); if a process instance doesn't have any logs, an hibernate error occurs. -- 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

15 years, 11 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues July 2008