August 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1463) task condition element is not exist jpdl3.2.3 schema, but in code

by xiong cf (JIRA)

task condition element is not exist jpdl3.2.3 schema, but in code ----------------------------------------------------------------- Key: JBPM-1463 URL: https://jira.jboss.org/jira/browse/JBPM-1463 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: jPDL 3 Affects Versions: jPDL 3.2.3 Reporter: xiong cf in jpdl-3.2.xsd : <xs:element name="task"> <xs:complexType> <xs:choice minOccurs="0" maxOccurs="unbounded"> <xs:element ref="description" /> <xs:element ref="assignment"/> <xs:element ref="controller"/> <xs:element ref="event"/> <xs:element ref="timer"/> <xs:element name="reminder"> <xs:complexType> <xs:attribute name="duedate" type="xs:string" use="required" /> <xs:attribute name="repeat" type="xs:string" /> </xs:complexType> </xs:element> </xs:choice> <xs:attribute name="name" type="xs:string" /> <xs:attribute name="blocking" type="booleanType" default="false"/> <xs:attribute name="signalling" type="booleanType" default="true"/> <xs:attribute name="description" type="xs:string" /> <xs:attribute name="duedate" type="xs:string" /> <xs:attribute name="swimlane" type="xs:string" /> <xs:attribute name="priority" type="priorityType" default="normal" /> <xs:attribute name="notify" type="booleanType" default="false"/> </xs:complexType> </xs:element> is not exist element condition. but in org.jbpm.jpdl.xml.JpdlXmlReader line312 has: // get the condition String condition = taskElement.elementTextTrim("condition"); if (condition!=null) { task.setCondition(condition); } else { task.setCondition(taskElement.attributeValue("condition")); } and in org.jbpm.graph.node.TaskNode line161 has: if ( (createTasks) && (tasks!=null) ) { Iterator iter = tasks.iterator(); while (iter.hasNext()) { Task task = (Task) iter.next(); executionContext.setTask(task); if (evaluateTaskCondition(task.getCondition(), executionContext)) { tmi.createTaskInstance(task, executionContext); } } } I think in jbpm3.2.3 should be spport task condition element , but document and schema not new -- 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

14 years

5
7
0 / 0

[JBoss JIRA] Created: (JBPM-1170) Multiple Timers with same name on Node end prematurely

by David Roberts (JIRA)

Multiple Timers with same name on Node end prematurely ------------------------------------------------------ Key: JBPM-1170 URL: http://jira.jboss.com/jira/browse/JBPM-1170 Project: JBoss jBPM Issue Type: Bug Affects Versions: jBPM jPDL 3.2.2 Environment: Jbpm 3.2.2, Tomcat 5.028, MySQL 5.0 Reporter: David Roberts Assigned To: Tom Baeyens When you have multiple Tasks on a Node, and each task has a Timer called, for example, "Reminder". Lets say each timer is set to repeat every 24 hours. If you complete one of the Tasks on the node, the Timer called "Reminder" on that task instance ends, but so does every other timer for all other tasks on that node with the name "Reminder". Surely this should not happen? You could avoid this by naming each Timer differenty, example "Reminder 1", "Reminder 2". But the problem may still happen if you have multiple task instances of the SAME task. Then the name of the Reminders will still be the same, so they will all end when completing one of the task instances. -- 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

14 years

4
4
0 / 0

[JBoss JIRA] Created: (JBPM-1166) fix SEAM timer transaction integration

by Tom Baeyens (JIRA)

fix SEAM timer transaction integration -------------------------------------- Key: JBPM-1166 URL: http://jira.jboss.com/jira/browse/JBPM-1166 Project: JBoss jBPM Issue Type: Bug Components: Core Engine 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

14 years

4
19
0 / 0

[JBoss JIRA] Created: (JBPM-1140) Empty <handler> element in <decision> cause org.jbpm.graph.def.DelegationException

by Rafa? ?ukowski (JIRA)

Empty <handler> element in <decision> cause org.jbpm.graph.def.DelegationException ---------------------------------------------------------------------------------- Key: JBPM-1140 URL: http://jira.jboss.com/jira/browse/JBPM-1140 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Rafa? ?ukowski Assigned To: Tom Baeyens Priority: Trivial That is my first issue, forgive me any mistakes and possible redundancy or duplication;) Using graphical designer I've created process file with empty <handler> : <decision name="decision1"> <handler></handler> <transition to="optional" name="to optional"></transition><transition to="first" name="to optional"></transition> </decision> And this is not working (org.jbpm.graph.def.DelegationException). After deleting <handler></handler> process is running correctly. Don't know if this is error in engine or in designer. Maby this kind of decision node is incorrect, and then designer should avoid this situation. My opinion is that engine should ignore empty handlers and go on without errors... -- 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

14 years

3
4
0 / 0

[JBoss JIRA] Created: (JBPM-1118) Unexpected behavier of LoggingConfigDbTest

by Jan-Philipp Bolle (JIRA)

Unexpected behavier of LoggingConfigDbTest ------------------------------------------ Key: JBPM-1118 URL: http://jira.jboss.com/jira/browse/JBPM-1118 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Jan-Philipp Bolle Assigned To: Tom Baeyens Priority: Trivial It looks like that the LoggingConfigDbTest is not working. I added in nologging.jbpm.cfg.xml the org.jbpm.logging.db.DbLoggingServiceFactory. Now I assume that the test must fail because jBPM is configured to use the loggingservice. But the test still work (is green). -- 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

14 years

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-1159) Update missing suggested alternatives in deprecated JbpmSessionFactory

by Julien Kronegg (JIRA)

Update missing suggested alternatives in deprecated JbpmSessionFactory ---------------------------------------------------------------------- Key: JBPM-1159 URL: http://jira.jboss.com/jira/browse/JBPM-1159 Project: JBoss jBPM Issue Type: Bug Components: Documentation Affects Versions: jBPM jPDL 3.2.2 Environment: source code downloaded from CVS :pserver:anonymous@anoncvs.forge.jboss.com:/cvsroot/jbpm (jbpm.3) Reporter: Julien Kronegg Assigned To: Tom Baeyens Priority: Minor The class org.jbpm.db.JbpmSessionFactory is deprecated and the deprecation comment states: @deprecated use {@link org.jbpm.tc.ContextBuilder} and {@link org.jbpm.tc.db.JbpmSessionContext} instead. However, the org.jbpm.tc package is no more in the code. Thus, another suggested replacement should be provided. Contrarily of as specified in http://jira.jboss.com/jira/browse/JBPM-624 this issue is not fixed in CVS (as the code was downloaded from CVS). -- 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

14 years

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-1395) verify jbpm/soa integration

by Tom Baeyens (JIRA)

verify jbpm/soa integration --------------------------- Key: JBPM-1395 URL: https://jira.jboss.org/jira/browse/JBPM-1395 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: jPDL 3 Reporter: Tom Baeyens Fix For: jPDL 3.2.4 ESB people have already done some good work on trying to get jBPM integrated into ESB and the rest of the SOA platform. But this work should be verified from a jBPM perspective. Mainly it should be verified if there is enough coverage of the different transaction scenarios. E.g. a rollback in case of multiple transactional resources. More can be found in the related SOA issue description -- 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

14 years

4
14
0 / 0

[JBoss JIRA] Created: (JBPM-1171) make jbpm configurable to use a mail session from jndi instead of an additional config file

by Ronald van Kuijk (JIRA)

make jbpm configurable to use a mail session from jndi instead of an additional config file ------------------------------------------------------------------------------------------- Key: JBPM-1171 URL: http://jira.jboss.com/jira/browse/JBPM-1171 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Ronald van Kuijk Assigned To: Tom Baeyens Fix For: jBPM 3.3 jBPM now uses a config file for mail properties. Often (especially in JEE envs) a mail session is already configured and could be used by looking it up via jndi. jBPM should support this as well. -- 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

14 years, 1 month

4
14
0 / 0

[JBoss JIRA] Created: (JBPM-1453) merge job notification booleans

by Tom Baeyens (JIRA)

merge job notification booleans ------------------------------- Key: JBPM-1453 URL: https://jira.jboss.org/jira/browse/JBPM-1453 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: PVM Reporter: Tom Baeyens Priority: Critical merge the 2 independent booleans that keep track whether a notification to the job executor was already sent JobExecutorMessageSession.isNotificationAdded and JobExecutorTimerSession.jobExecutorNotificationScheduled -- 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

14 years, 5 months

3
16
0 / 0

[JBoss JIRA] Created: (JBPM-1164) Null Pointer Exception is thrown when subprocess is leave event is fired.

by Gurpreet Sahota (JIRA)

Null Pointer Exception is thrown when subprocess is leave event is fired. ------------------------------------------------------------------------- Key: JBPM-1164 URL: http://jira.jboss.com/jira/browse/JBPM-1164 Project: JBoss jBPM Issue Type: Bug Affects Versions: jBPM jPDL 3.2.2 Environment: Windows XP Pro, Sun JDK 1.5.0_13 Reporter: Gurpreet Sahota Assigned To: Tom Baeyens I have a process flow where process (A) calls a process state that in turn calls subprocess (B). When Subprocess "end" state is signalled then I receive a Null Pointer Exception. Following is stack trace java.lang.NullPointerException at org.jbpm.graph.node.ProcessState.leave(ProcessState.java:204) at org.jbpm.graph.exe.Token.signal(Token.java:195) at org.jbpm.graph.exe.Token.signal(Token.java:140) When debugging, it turns out that "leave" method in ProcessState tries to retrieve subProcessInstance from execution context. This is set to null causing exception. If executionContext.getToken() is used to retrieve the subProcessInstance, then it is not null. -- 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

14 years, 5 months

4
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues August 2008