October 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2237) Reporting for jBPM4

by Heiko Braun (JIRA)

Reporting for jBPM4 ------------------- Key: JBPM-2237 URL: https://jira.jboss.org/jira/browse/JBPM-2237 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: GWT Console 1.0.0 CR1 -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2157) Identity management editor

by Heiko Braun (JIRA)

Identity management editor -------------------------- Key: JBPM-2157 URL: https://jira.jboss.org/jira/browse/JBPM-2157 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Heiko Braun Assignee: Heiko Braun Fix For: GWT Console 1.0.x -- 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, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (JBPM-1797) Add authorization to the console

by Heiko Braun (JIRA)

Add authorization to the console -------------------------------- Key: JBPM-1797 URL: https://jira.jboss.org/jira/browse/JBPM-1797 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: GWT Console 1.0.0 CR1 Role based access to specific parts of the console -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2600) Update to console 1.2.0

by Heiko Braun (JIRA)

Update to console 1.2.0 ----------------------- Key: JBPM-2600 URL: https://jira.jboss.org/jira/browse/JBPM-2600 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Heiko Braun Assignee: Heiko Braun Fix For: jBPM 4.2 -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-2559) Transitions with timers from a user activity lead to incompleteable and indeleteable tasks

by Sebastian Schneider (JIRA)

Transitions with timers from a user activity lead to incompleteable and indeleteable tasks ------------------------------------------------------------------------------------------ Key: JBPM-2559 URL: https://jira.jboss.org/jira/browse/JBPM-2559 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.1 Environment: Windows XP, Apache Tomcat 6, JDK 1.6 (should not be relevant) Reporter: Sebastian Schneider Priority: Critical Fix For: jBPM 4.2 Situation: ======= Imagine you want to model an escalation of a user activity. After a specific timeout a transition should be taken to deal with the escalation. The transition might lead to a user activity assigned to someobody else or to a different role or more important to the next steps performed automatically without a reaction of the user. Problem: ======= When the timeout event fires the transition is taken and the execution moves on to the next activity. However the task remains in the user's task list who had the task assigned. The task was not completed. Deleting the task will not succeed since you cannot delete a task which belongs to an execution. Completing the task will also fail since the associated execution does not exist anymore but was already removed from 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, 7 months

3
7
0 / 0

[JBoss JIRA] Created: (JBPM-2603) Restore automatic save of timer actions

by Alejandro Guizar (JIRA)

Restore automatic save of timer actions --------------------------------------- Key: JBPM-2603 URL: https://jira.jboss.org/jira/browse/JBPM-2603 Project: jBPM Issue Type: Bug Components: Runtime Engine Reporter: Alejandro Guizar Assignee: Alejandro Guizar Fix For: jBPM 3.2.9 In jBPM 3.2.2, the JobSession.saveJob(Job) method looked like this: session.saveOrUpdate(job); if (job instanceof Timer) { Timer timer = (Timer) job; Action action = timer.getAction(); if (action != null && !session.contains(action)) session.save(action); } However this resulted in a duplicate action being saved to the database every time a 'static' timer was created. Hence the above method was reduced to: session.save(job); This change would affect dynamic timers whose actions are dynamic as well, that is, not present in the process definition. Dynamic actions are a somewhat extraneous use case. Normally a dynamic timer would be assigned a named action from the process definition: <process-definition> <action name="normal" class="org.example.NormalAction"/> <action name="exceptional" class="org.example.ExceptionalAction"/> </process-definition> Action action; if (isNormalSituation) action = processDefinition.getAction("normal")); else action = processDefinition.getAction("exceptional")); timer.setAction(action); If the action *must* be dynamic, it has to be saved manually under the new saveJob() behavior. Unlike the previous code snippet, where many dynamic timers share one static action, each timer is assigned a new action instance here: Action action = new Action(); executionContext.getJbpmContext().getSession().save(action); timer.setAction(action); jBPM deletes timers after they execute, but the associated actions are NOT deleted because they are normally static. The leftover actions will remain in the database, unreachable from any other object. Junk data is thus the price of restoring automatic action saves. -- 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, 8 months

1
3
0 / 0

[JBoss JIRA] Updated: (JBPM-165) process instance versioning

by Koen Aers (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-165?page=com.atlassian.jira.plugi... ] Koen Aers updated JBPM-165: --------------------------- Fix Version/s: jBPM 4.2 (was: jBPM 4.3) > process instance versioning > --------------------------- > > Key: JBPM-165 > URL: https://jira.jboss.org/jira/browse/JBPM-165 > Project: jBPM > Issue Type: Feature Request > Components: Runtime Engine > Reporter: Tom Baeyens > Assignee: Koen Aers > Fix For: jBPM 4.2 > > > i think jbpm could offer some degree of assistence in process instance versioning. > when a new version of a process is deployed, jbpm could do the following conversion for a process instance : > * input required: mapping of the nodes from the old to the new definition. > * cancel the old process instance > * create a new process instance and copy the runtime (exe) information such as tokens and process variables from the old process instance. > * then establish a special link between the 2 process instances to indicate that the new process instance is the continuation of the old process instance. > this way we can avoid the problematic conversion of logs, while still keeping them in the system. > NOTE: i believe that Bernd has got some code for this in jBPM 3. That could be used as a basis. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-165) process instance versioning

by Koen Aers (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-165?page=com.atlassian.jira.plugi... ] Koen Aers closed JBPM-165. -------------------------- Resolution: Done > process instance versioning > --------------------------- > > Key: JBPM-165 > URL: https://jira.jboss.org/jira/browse/JBPM-165 > Project: jBPM > Issue Type: Feature Request > Components: Runtime Engine > Reporter: Tom Baeyens > Assignee: Koen Aers > Fix For: jBPM 4.2 > > > i think jbpm could offer some degree of assistence in process instance versioning. > when a new version of a process is deployed, jbpm could do the following conversion for a process instance : > * input required: mapping of the nodes from the old to the new definition. > * cancel the old process instance > * create a new process instance and copy the runtime (exe) information such as tokens and process variables from the old process instance. > * then establish a special link between the 2 process instances to indicate that the new process instance is the continuation of the old process instance. > this way we can avoid the problematic conversion of logs, while still keeping them in the system. > NOTE: i believe that Bernd has got some code for this in jBPM 3. That could be used as a basis. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-2200) add process classloading

by Tom Baeyens (JIRA)

add process classloading ------------------------ Key: JBPM-2200 URL: https://jira.jboss.org/jira/browse/JBPM-2200 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.0.0.CR1 Some of the tests in the integration test suite depends on this capability. They are currently excluded from the integration test run. Don't forget to exclude those tests when done. The used user code test classes will have to be added to the deployment in the examples as well. -- 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, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPM-2590) mail activities do not work with the Tomcat demo setup: javax.mail.NoSuchProviderException: smtp

by Sebastian Schneider (JIRA)

mail activities do not work with the Tomcat demo setup: javax.mail.NoSuchProviderException: smtp ------------------------------------------------------------------------------------------------ Key: JBPM-2590 URL: https://jira.jboss.org/jira/browse/JBPM-2590 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.1 Environment: Apache Tomcat 6.0.20, JDK 1.6.0_16 Reporter: Sebastian Schneider Fix For: jBPM 4.2 Using the mail activity in a process definition does not work as soon as the process is deployed to the jBPM installation on Tomcat. The mail activity works fine in a unit test. The following exception is thrown when the execution reaches the mail activity: Caused by: javax.mail.NoSuchProviderException: smtp at javax.mail.Session.getService(Session.java:794) at javax.mail.Session.getTransport(Session.java:718) at javax.mail.Session.getTransport(Session.java:661) at javax.mail.Session.getTransport(Session.java:641) at javax.mail.Session.getTransport(Session.java:696) at org.jbpm.pvm.internal.email.impl.MailSessionImpl.send(MailSessionImpl .java:48) -- 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, 8 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues October 2009