November 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1831) Provide a start/stop script for sybase

by Thomas Diesler (JIRA)

Provide a start/stop script for sybase -------------------------------------- Key: JBPM-1831 URL: https://jira.jboss.org/jira/browse/JBPM-1831 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Alejandro Guizar Fix For: jBPM 3.3.1 GA Please install this in /etc/init.d on the QA box Sybase should survive reboot -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

3
9
0 / 0

[JBoss JIRA] Created: (JBPM-1810) Fix clean, drop, create schema with JbpmSchema

by Thomas Diesler (JIRA)

Fix clean, drop, create schema with JbpmSchema ---------------------------------------------- Key: JBPM-1810 URL: https://jira.jboss.org/jira/browse/JBPM-1810 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler This fails with all databases mvn -o -Ddatabase=mysql -Dtest=JbpmSchemaDbTest test -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (JBPM-1861) expose subtasks through taskservice api

by Tom Baeyens (JIRA)

expose subtasks through taskservice api --------------------------------------- Key: JBPM-1861 URL: https://jira.jboss.org/jira/browse/JBPM-1861 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 4.0.0 Alpha1 allow for dynamic creation of subtasks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

2
9
0 / 0

[JBoss JIRA] Created: (JBPM-1808) Changes applied for JBPM guide included in SOA 4.3 GA release

by Darrin Mison (JIRA)

Changes applied for JBPM guide included in SOA 4.3 GA release ------------------------------------------------------------- Key: JBPM-1808 URL: https://jira.jboss.org/jira/browse/JBPM-1808 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Reporter: Darrin Mison These are the changes that were applied to the version of the JBPM Guide included with the SOA 4.3 GA Release. One comment is attached per XML file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

4
29
0 / 0

[JBoss JIRA] Created: (JBPM-1686) NPE when reading a process definition with a decision name which contains the "/" character

by Julien Kronegg (JIRA)

NPE when reading a process definition with a decision name which contains the "/" character ------------------------------------------------------------------------------------------- Key: JBPM-1686 URL: https://jira.jboss.org/jira/browse/JBPM-1686 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jPDL 3.2.2 Environment: JDK1.6.0, Eclipse 3.3 Reporter: Julien Kronegg Priority: Minor When a process definition is read and when it contains a decision named with a "/" character, a NullPointerException is raised: import org.jbpm.graph.def.ProcessDefinition; public class TestDecisionNPE { public static final void main(String[] args){ ProcessDefinition.parseXmlString( "<process-definition>" + " <start-state>" + " <transition to='d/e' />" + " </start-state>" + " <decision name='d/e'>" + " <transition name='one' to='a'>" + " <condition>#{a == 1}</condition>" + " </transition>" + " <transition name='three' to='c'>" + " <condition>#{a == 3}</condition>" + " </transition>" + " </decision>" + " <state name='a' />" + " <state name='c' />" + "</process-definition>"); } } raises: GRAVE: couldn't parse process definition java.lang.NullPointerException at org.jbpm.graph.def.ProcessDefinition.findNode(ProcessDefinition.java:345) at org.jbpm.graph.def.ProcessDefinition.findNode(ProcessDefinition.java:299) at org.jbpm.jpdl.xml.JpdlXmlReader.resolveTransitionDestination(JpdlXmlReader.java:774) at org.jbpm.jpdl.xml.JpdlXmlReader.resolveTransitionDestinations(JpdlXmlReader.java:740) at org.jbpm.jpdl.xml.JpdlXmlReader.resolveTransitionDestinations(JpdlXmlReader.java:732) at org.jbpm.jpdl.xml.JpdlXmlReader.readProcessDefinition(JpdlXmlReader.java:162) at org.jbpm.graph.def.ProcessDefinition.parseXmlString(ProcessDefinition.java:151) at test.TestDecisionNPE.main(TestDecisionNPE.java:7) Exception in thread "main" org.jbpm.jpdl.JpdlException: [[ERROR] couldn't parse process definition] at org.jbpm.jpdl.xml.JpdlXmlReader.readProcessDefinition(JpdlXmlReader.java:172) at org.jbpm.graph.def.ProcessDefinition.parseXmlString(ProcessDefinition.java:151) at test.TestDecisionNPE.main(TestDecisionNPE.java:7) This is due to a "node = nodeCollection.getNode(namePart);" in ProcessDefinition.findNode(): a Decision has no nodes, so the nodeCollection is null. It should be : 1. a more descriptive exception message, such as "could not get the node with name XXX" 2. a validation step which prevent the node name to contain "/" characters, e.g. throw an exception "the node name cannot contain a "/" character" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-1774) end-task attribute should cancel tasks instead of ending them (and thus have a different name)

by Ronald van Kuijk (JIRA)

end-task attribute should cancel tasks instead of ending them (and thus have a different name) ---------------------------------------------------------------------------------------------- Key: JBPM-1774 URL: https://jira.jboss.org/jira/browse/JBPM-1774 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.3.0 CR1, jBPM 3.2.3, SOA 4.2 CP02 Environment: N/A Reporter: Ronald van Kuijk Priority: Minor The end-tasks attribute on a task-node is used to end tasks that are not ended when the task node is left and no blocking tasks exist. These non-blocking tasks should (imo) be cancelled and not ended. So the attribute should also chance from end-tasks to cancel-tasks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/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-1280) QA job executor

by Tom Baeyens (JIRA)

QA job executor --------------- Key: JBPM-1280 URL: http://jira.jboss.com/jira/browse/JBPM-1280 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: PVM Reporter: Tom Baeyens First, we need to establish what we're going to QA and how. I see 3 distinct types of tests for the job executor 1) Using JobSession to create jobs and then use the JobExecutor API's to control the execution of those jobs. This way, all these tests can and should be done in a single thread. * a commit for processing an asynchronous message * a commit for processing a timer * a commit for the combination of a an asynchronous message and a timer * a commit with a custom resource in the standard transaction * test a rollback caused by a user code exception in an asynchronous continuation * test a rollback caused by a user code exception in an timer * test a rollback caused by a user code exception with a custom resource in the standard transaction * test a rollback caused by an optimistic locking exception in an asynchronous continuation * test a rollback caused by an optimistic locking exception in an timer * test a rollback caused by an optimistic locking with a custom resource in the standard transaction 2) If we only use the public, stable API's, we'll be a lot more limited in what we're able to test. We can e.g. run this test suite against the jBPM 3 codebase. * create and execute a process with a couple of asynchronous continuation in it. * create and execute a process with asynchronous continuations in a concurrent section. * create and execute a process with a couple of timers in it. * create and execute a process with a couple of timers in a concurrent section * a combination of a timer and an asynchronous continuation 3) Load and stress tests. Also these should only make use of public API's and ways to deploy processes. So that this test suite is configurable/runnable on different environments (and also against the jBPM 3 codebase) -- 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
19
0 / 0

[JBoss JIRA] Created: (JBPM-1798) potential nullpointer in asynchronous jobs when process ends

by Tom Baeyens (JIRA)

potential nullpointer in asynchronous jobs when process ends ------------------------------------------------------------ Key: JBPM-1798 URL: https://jira.jboss.org/jira/browse/JBPM-1798 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Reporter: Tom Baeyens Fix For: jBPM 3.3.1 GA when a process instance ends, a cleaning Job is issued. if that happens when an async job is outstanding, then it turns out that this may lead to a NPE when the outstanding job is executed. use this process to reproduce in an AbstractDbTestCase ProcessDefinition processDefinition = ProcessDefinition.parseXmlString( "<process-definition name='customjobexecution' initial='start'>" + " <node name='start'>" + " <transition to='end'>" + " <action async='true' class='"+AsyncAction.class.getName()+"' />" + " </transition>" + " </node>" + " <end-state name='end' />" + "</process-definition>" deploy and start it new Transaction() then start the job executor with startJobExecutor() -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

3
10
0 / 0

[JBoss JIRA] Created: (JBPM-1160) Bad link to documentation in org.jbpm.context.exe.ContextInstance javadoc

by Julien Kronegg (JIRA)

Bad link to documentation in org.jbpm.context.exe.ContextInstance javadoc ------------------------------------------------------------------------- Key: JBPM-1160 URL: http://jira.jboss.com/jira/browse/JBPM-1160 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Environment: ContextInstance.java (CVS version 1.2) Reporter: Julien Kronegg Assigned To: Tom Baeyens Priority: Minor The class javadoc states: "More information on context and process variableInstances can be found in <a href="../../../../../userguide/en/html/reference.html#context">the userguide, section context</a>" This link does not exist in version 3.2.2 and should be corrected. The good link is ".../userguide/html/context.html" (chapter title is "10. Context"). -- 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-1132) bad variable "instanceId" in CancelProcessInstanceCommand with query GraphSession.findSubProcessInstances

by jerome tellier (JIRA)

bad variable "instanceId" in CancelProcessInstanceCommand with query GraphSession.findSubProcessInstances ---------------------------------------------------------------------------------------------------------- Key: JBPM-1132 URL: http://jira.jboss.com/jira/browse/JBPM-1132 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 method CancelProcessInstanceCommand.cancelSubProcesses use "instanceId" in the query findSubProcessInstances, but it was renamed "processInstance" in the hql query in 3.2.2. -- 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues November 2008