July 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2419) change Job.dueDate in Job.duedate

by Tom Baeyens (JIRA)

change Job.dueDate in Job.duedate --------------------------------- Key: JBPM-2419 URL: https://jira.jboss.org/jira/browse/JBPM-2419 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 4.1 to be in sync with capitalization in Task.duedate property REMARK: it's not possible to handle this with deprecated. as we cannot introduce the new getDuedate method as long as the getDueDate method is around. so we'll have to just document this in the 4.1 upgrade release notes. -- 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, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-2455) add template attribute to notification and reminder in xsd

by Ronald van Kuijk (JIRA)

add template attribute to notification and reminder in xsd ---------------------------------------------------------- Key: JBPM-2455 URL: https://jira.jboss.org/jira/browse/JBPM-2455 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.0 Reporter: Ronald van Kuijk Fix For: jBPM 4.2 The source of the mail producer etc already takes into account that there can be a template attribute on the notification and reminder elements under task elements. The XSD does not seem to support it though. Asked customer to test without the xsd to see if this works. If it does, I'd like to move this to 4.1 even though there is a jira freeze. -- 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, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-2466) task-reminder should not use task-notification template when sending mail

by Ronald van Kuijk (JIRA)

task-reminder should not use task-notification template when sending mail ------------------------------------------------------------------------- Key: JBPM-2466 URL: https://jira.jboss.org/jira/browse/JBPM-2466 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Ronald van Kuijk Currently it does because of a hard coded name that is *not* the event-name (task-notification is the template, task-assign the event) I'll keep the template names the same by adding a mapping in the code. -- 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, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-2194) cant share jars

by David Schlotfeldt (JIRA)

cant share jars --------------- Key: JBPM-2194 URL: https://jira.jboss.org/jira/browse/JBPM-2194 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 3.2.6.SP1 Reporter: David Schlotfeldt Priority: Critical You can't share the jbpm jars. Each application must have its own copy since classes like http://anonsvn.jboss.org/repos/jbpm/jbpm3/tags/jbpm-3.2.6.SP1/modules/cor... use static variables. This is a LARGE issue. JBoss Seam for example set settings on UserCodeInterceptorConfig and JbpmExpressionEvaluator. These settings will mess will affect ALL applications that share the same class definitions since the settings are a on static variable. -- 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, 11 months

2
7
0 / 0

[JBoss JIRA] Created: (JBPM-2092) Byte Array Should Be In Default Cache Configuration

by Brad Davis (JIRA)

Byte Array Should Be In Default Cache Configuration --------------------------------------------------- Key: JBPM-2092 URL: https://jira.jboss.org/jira/browse/JBPM-2092 Project: JBoss jBPM Issue Type: Quality Risk Security Level: Public (Everyone can see) Components: Core Engine, Documentation Affects Versions: jBPM 3.3.1 GA Reporter: Brad Davis The hibernate configuration should cache byte array by default. It is missing from the caching configuration. This leads to major performance issues when deploying handler logic classes [java action handlers and decision handlers for example] to the database. -- 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, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2460) sub-process name is not resolved upon deployment with the jbpm-console

by Martin Putz (JIRA)

sub-process name is not resolved upon deployment with the jbpm-console ---------------------------------------------------------------------- Key: JBPM-2460 URL: https://jira.jboss.org/jira/browse/JBPM-2460 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Console Affects Versions: jBPM 3.2.5.SP5, jBPM 3.2.6.SP1 Reporter: Martin Putz Assignee: Martin Putz Using the upload process function of the jbpm-console web app, deploy two processes with a parent-child relationship through a process-state node: 1. childprocess.par <process-definition name="child"> [...] </process-definition> 2. parentprocess.par <process-definition name="parent"> [...] <process-state name="process-state1"> <sub-process name="child" /> <transition to="end"></transition> </process-state> [...] </process-definition> After the two processes are deployed, the relation from the parent-process to the child-process is not properly set in the database: mysql> select ID_, NAME_, SUBPROCNAME_, SUBPROCESSDEFINITION_ from JBPM_NODE where CLASS_ = 'C'; +-----+----------------+--------------+-----------------------+ | ID_ | NAME_ | SUBPROCNAME_ | SUBPROCESSDEFINITION_ | +-----+----------------+--------------+-----------------------+ | 78 | process-state1 | NULL | NULL | +-----+----------------+--------------+-----------------------+ 1 row in set (0.00 sec) This is due to the fact that the jbpm4jsf part initializes the JbpmContext *after* the processdefinition.xml file is parsed, therefore the call to DbSubProcessResolver.findSubProcess returns null. -- 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, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-2432) Review process image display in console

by Joram Barrez (JIRA)

Review process image display in console --------------------------------------- Key: JBPM-2432 URL: https://jira.jboss.org/jira/browse/JBPM-2432 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Joram Barrez Assignee: Joram Barrez Priority: Minor Fix For: jBPM 4.1 -- 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, 11 months

4
7
0 / 0

[JBoss JIRA] Created: (JBPM-2462) CLONE -sub-process name is not resolved upon deployment with the jbpm-console

by Trevor Kirby (JIRA)

CLONE -sub-process name is not resolved upon deployment with the jbpm-console ----------------------------------------------------------------------------- Key: JBPM-2462 URL: https://jira.jboss.org/jira/browse/JBPM-2462 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Console Affects Versions: jBPM 3.2.6.SP1, jBPM 3.2.5.SP5 Reporter: Martin Putz Assignee: Martin Putz Using the upload process function of the jbpm-console web app, deploy two processes with a parent-child relationship through a process-state node: 1. childprocess.par <process-definition name="child"> [...] </process-definition> 2. parentprocess.par <process-definition name="parent"> [...] <process-state name="process-state1"> <sub-process name="child" /> <transition to="end"></transition> </process-state> [...] </process-definition> After the two processes are deployed, the relation from the parent-process to the child-process is not properly set in the database: mysql> select ID_, NAME_, SUBPROCNAME_, SUBPROCESSDEFINITION_ from JBPM_NODE where CLASS_ = 'C'; +-----+----------------+--------------+-----------------------+ | ID_ | NAME_ | SUBPROCNAME_ | SUBPROCESSDEFINITION_ | +-----+----------------+--------------+-----------------------+ | 78 | process-state1 | NULL | NULL | +-----+----------------+--------------+-----------------------+ 1 row in set (0.00 sec) This is due to the fact that the jbpm4jsf part initializes the JbpmContext *after* the processdefinition.xml file is parsed, therefore the call to DbSubProcessResolver.findSubProcess returns null. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-2457) Make tasks the default editor

by Heiko Braun (JIRA)

Make tasks the default editor ----------------------------- Key: JBPM-2457 URL: https://jira.jboss.org/jira/browse/JBPM-2457 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Heiko Braun -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-2093) Stabilize EjbSchedulerTest.testScheduleFork under MySQL

by Alejandro Guizar (JIRA)

Stabilize EjbSchedulerTest.testScheduleFork under MySQL ------------------------------------------------------- Key: JBPM-2093 URL: https://jira.jboss.org/jira/browse/JBPM-2093 Project: JBoss jBPM Issue Type: Quality Risk Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.2.6 GA , jBPM-3.2.5.SP3 Environment: JBoss 5.0.0.GA MySQL 5.0.67 Sun JDK 1.5.0.16 Reporter: Alejandro Guizar testScheduleFork fails with: org.jbpm.JbpmException: event 'process-end' did not occur within 300000 ms at org.jbpm.graph.def.EventCallback.waitForEvent(EventCallback.java:125) at org.jbpm.graph.def.EventCallback.waitForEvent(EventCallback.java:106) at org.jbpm.enterprise.ejbtimer.EjbSchedulerTest.testScheduleFork(EjbSchedulerTest.java:265) -- 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, 11 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues July 2009