September 2009 - jbpm-issues - Jboss List Archives

[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

15 years, 1 month

3
7
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

15 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPM-1772) Fix JoinDbTest on postgresql

by Thomas Diesler (JIRA)

Fix JoinDbTest on postgresql ---------------------------- Key: JBPM-1772 URL: https://jira.jboss.org/jira/browse/JBPM-1772 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jBPM 3.3.1 GA expected:<[10X, 10Y, 10Z, 10a, 10b, 10c, 10d, 10e, 11X, 11Y, 11Z, 11a, 11b, 11c, 11d, 11e, 12X, 12Y, 12Z, 12a, 12b, 12c, 12d, 12e, 13X, 13Y, 13Z, 13a, 13b, 13c, 13d, 13e, 14X, 14Y, 14Z, 14a, 14b, 14c, 14d, 14e, 15X, 15Y, 15Z, 15a, 15b, 15c, 15d, 15e, 16X, 16Y, 16Z, 16a, 16b, 16c, 16d, 16e, 17X, 17Y, 17Z, 17a, 17b, 17c, 17d, 17e, 18X, 18Y, 18Z, 18a, 18b, 18c, 18d, 18e, 19X, 19Y, 19Z, 19a, 19b, 19c, 19d, 19e, 1X, 1Y, 1Z, 1a, 1b, 1c, 1d, 1e, 20X, 20Y, 20Z, 20a, 20b, 20c, 20d, 20e, 2X, 2Y, 2Z, 2a, 2b, 2c, 2d, 2e, 3X, 3Y, 3Z, 3a, 3b, 3c, 3d, 3e, 4X, 4Y, 4Z, 4a, 4b, 4c, 4d, 4e, 5X, 5Y, 5Z, 5a, 5b, 5c, 5d, 5e, 6X, 6Y, 6Z, 6a, 6b, 6c, 6d, 6e, 7X, 7Y, 7Z, 7a, 7b, 7c, 7d, 7e, 8X, 8Y, 8Z, 8a, 8b, 8c, 8d, 8e, 9X, 9Y, 9Z, 9a, 9b, 9c, 9d, 9e]> but was:<[100X, 100Y, 100Z, 100a, 100b, 100c, 100d, 100e, 108X, 108Y, 108Z, 108a, 108b, 108c, 108d, 108e, 116X, 116Y, 116Z, 116a, 116b, 116c, 116d, 116e, 124X, 124Y, 124Z, 124a, 124b, 124c, 124d, 124e, 132X, 132Y, 132Z, 132a, 132b, 132c, 132d, 132e, 140X, 140Y, 140Z, 140a, 140b, 140c, 140d, 140e, 148X, 148Y, 148Z, 148a, 148b, 148c, 148d, 148e, 156X, 156Y, 156Z, 156a, 156b, 156c, 156d, 156e, 164X, 164Y, 164Z, 164a, 164b, 164c, 164d, 164e, 172X, 172Y, 172Z, 172a, 172b, 172c, 172d, 172e, 180X, 180Y, 180Z, 180a, 180b, 180c, 180d, 180e, 188X, 188Y, 188Z, 188a, 188b, 188c, 188d, 188e, 36X, 36Y, 36Z, 36a, 36b, 36c, 36d, 36e, 44X, 44Y, 44Z, 44a, 44b, 44c, 44d, 44e, 52X, 52Y, 52Z, 52a, 52b, 52c, 52d, 52e, 60X, 60Y, 60Z, 60a, 60b, 60c, 60d, 60e, 68X, 68Y, 68Z, 68a, 68b, 68c, 68d, 68e, 76X, 76Y, 76Z, 76a, 76b, 76c, 76d, 76e, 84X, 84Y, 84Z, 84a, 84b, 84c, 84d, 84e, 92X, 92Y, 92Z, 92a, 92b, 92c, 92d, 92e]> -- 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, 2 months

4
13
0 / 0

[JBoss JIRA] Created: (JBPM-2547) Verify JDK5 compatibility of Signavio

by Joram Barrez (JIRA)

Verify JDK5 compatibility of Signavio ------------------------------------- Key: JBPM-2547 URL: https://jira.jboss.org/jira/browse/JBPM-2547 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: jBPM 4.1 Reporter: Joram Barrez Fix For: jBPM 4.2 (Stefan Krumnow) I just checked-in some changes so that the project can now be build with an JDK version 1.5 (it wasn't that difficult). (Maybe you will have to delete the folder oryx/build/buildApps/ manually before you run the build with ant under JDK 5) One additional comment: When updating your working copy there will often occur SVN-conflicts in the oryx/ folder. These conflicts are cauesed by the build-process that copies some source-files and can be resolved by using the new incoming version of the files. -- 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, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (JBPM-2554) jPDL schema does not contain an attribute "description" for the element task

by Sebastian Schneider (JIRA)

jPDL schema does not contain an attribute "description" for the element task ---------------------------------------------------------------------------- Key: JBPM-2554 URL: https://jira.jboss.org/jira/browse/JBPM-2554 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.1 Environment: not relevant Reporter: Sebastian Schneider Fix For: jBPM 4.2 The jPDL schema defintion does not contain an attribute named description for the element task. It was just left out. You find a changed schema file attached. Should description be an attribute anyway but rather an element in task? Might be more comfortable with bigger descriptions when hand-editing process definitions. I have no clue how exactly the parsing of the file is done in the engine so I do not know if this would be a major change. For now it would be great to account for the attribute "description" and get this change into the 4.2 release. -- 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, 2 months

3
8
0 / 0

[JBoss JIRA] Created: (JBPM-2540) Fix replacement of Signavio repository path on Windows

by Joram Barrez (JIRA)

Fix replacement of Signavio repository path on Windows ------------------------------------------------------ Key: JBPM-2540 URL: https://jira.jboss.org/jira/browse/JBPM-2540 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.1 Reporter: Joram Barrez Assignee: Joram Barrez Priority: Minor Fix For: jBPM 4.2 Currently, you need to set the repo path hard coded when installing signavio. A regexp was used to change the repo path in the web.xml of Signavio war, but this doesn't seem to work on Windows. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-2521) User docs are showing many v4.0 entries instead of current version (4.1)

by Eric D. Schabell (JIRA)

User docs are showing many v4.0 entries instead of current version (4.1) ------------------------------------------------------------------------ Key: JBPM-2521 URL: https://jira.jboss.org/jira/browse/JBPM-2521 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jBPM 4.1 Environment: n/a Reporter: Eric D. Schabell Priority: Trivial Fix For: jBPM 4.2 The user docs when following the installation section have numerous references to v4.0 instead of the v4.1 as released this week. I might be able to help update them for the next release if you need this sort of help. Just let me know. -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2509) database migration installation script

by Tom Baeyens (JIRA)

database migration installation script -------------------------------------- Key: JBPM-2509 URL: https://jira.jboss.org/jira/browse/JBPM-2509 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Alejandro Guizar Fix For: jBPM 4.2 Database migration should be offered as a target in the install build file. And it should work in the distro without requiring the source build. -- 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, 2 months

2
8
0 / 0

[JBoss JIRA] Created: (JBPM-2542) jBPM 4.1 task Form example ( BPM Console authentication )

by Makarand Kulkarni (JIRA)

jBPM 4.1 task Form example ( BPM Console authentication ) --------------------------------------------------------- Key: JBPM-2542 URL: https://jira.jboss.org/jira/browse/JBPM-2542 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Console Affects Versions: jBPM 4.1 Environment: jBPM 4.1, JBOSS 5.0.0 GA,eclipse 3.5 Reporter: Makarand Kulkarni Hi, I have just downloaded jBPM 4.1. I was trying to run "taskform" example available in jBPM 4.1 examples through GWT console (http://localhost:8080/jbpm-console). After creating new process instance, "request vacation" form has opened with BPM-console Server Username and password... I tried lot of combinations like alex/password, administrator/administrator, admin/admin, manager/manager etc. but unfortunately nothing worked Can anybody guide me in this regard ? Also If I dont want authentication for form like this, is there any way ? By going through GWT 1.1.2 list, i can see some "Switch to form based authentication and session management" -Regards Makarand -- 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, 2 months

3
9
0 / 0

[JBoss JIRA] Created: (JBPM-2453) Add suport for custom reports

by Joram Barrez (JIRA)

Add suport for custom reports ----------------------------- Key: JBPM-2453 URL: https://jira.jboss.org/jira/browse/JBPM-2453 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jBPM 4.0 Reporter: Joram Barrez Assignee: Heiko Braun Fix For: jBPM 4.1 Currently, the default reports can be customized completely if the file name is kept the same. The reporting mechanism should be extended that it is possible to add custom reports (ie with other names) for display in the gwt 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

15 years, 2 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues September 2009