July 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2423) jBPM 4 Task Forms Example Not Working

by Viswanath Durbha (JIRA)

jBPM 4 Task Forms Example Not Working ------------------------------------- Key: JBPM-2423 URL: https://jira.jboss.org/jira/browse/JBPM-2423 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Console Affects Versions: jBPM 4.0, GWT Console 1.0.0 GA Environment: GNU/Linux, Java version: 1.6.0_11,Sun Microsystems Inc, jBPM 4.0, jBoss 5.1.0.GA, Eclipse Galileo, Embedded Database, Standard Installation (ant demo.setup) Reporter: Viswanath Durbha After installing jBPM using the standard ant demo.setup task, I opened up the jBPM console followed the steps below: 1. Log in as peter 2. Create instance of VacationRequest process (Example with Task Forms) 3. Open Group Tasks and Claim the task 4. Open Personal Tasks and Click "View". Expected Resut: Task opened with details as specified in request_vacation.ftl form Actual Result: Pop-up window with error message "The task doesn't provide a UI" -- 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, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-2301) process start forms

by Tom Baeyens (JIRA)

process start forms ------------------- Key: JBPM-2301 URL: https://jira.jboss.org/jira/browse/JBPM-2301 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Console Reporter: Tom Baeyens Assignee: Heiko Braun Fix For: jBPM 4.1 in jbpm 3 wee have a mechanism where starting of process could be done with a form. something similar should be introduced in the current console / forms support. -- 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, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPM-2443) Simplify adding classpath resources to deployment

by Joram Barrez (JIRA)

Simplify adding classpath resources to deployment -------------------------------------------------- Key: JBPM-2443 URL: https://jira.jboss.org/jira/browse/JBPM-2443 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Joram Barrez Priority: Minor Fix For: jBPM 4.x Currently, every resource needs to be added to the deployment: deployment.addResourceFromClasspath("be/jorambarrez/jbpm4/demo/taskform/process.jpdl.xml"); deployment.addResourceFromClasspath("be/jorambarrez/jbpm4/demo/taskform/process.png"); deployment.addResourceFromClasspath("be/jorambarrez/jbpm4/demo/taskform/verify_request.ftl"); deployment.addResourceFromClasspath("be/jorambarrez/jbpm4/demo/taskform/request_vacation.ftl"); This can be simplified by automatically importing resources such as taskforms referenced in the process xml or the process png. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-2441) DeployCmd should use NewDeployment instead of DeploymentImpl

by Jorge Morales Pou (JIRA)

DeployCmd should use NewDeployment instead of DeploymentImpl ------------------------------------------------------------ Key: JBPM-2441 URL: https://jira.jboss.org/jira/browse/JBPM-2441 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.0 Reporter: Jorge Morales Pou Fix For: jBPM 4.x In order to make code reusable, this should accept the interface rather than a concrete impl. class. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-2437) add start task form capability to console

by Tom Baeyens (JIRA)

add start task form capability to console ----------------------------------------- Key: JBPM-2437 URL: https://jira.jboss.org/jira/browse/JBPM-2437 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Console Reporter: Tom Baeyens Assignee: Heiko Braun Fix For: jBPM 4.1 Add capability to supply data through a form when a new process instance is started. First the engine needs to expose the form property. (see the dependent issue). Once that is done then the console can add this feature. -- 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, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-2210) Add support for AS 5.1.x

by Heiko Braun (JIRA)

Add support for AS 5.1.x ------------------------ Key: JBPM-2210 URL: https://jira.jboss.org/jira/browse/JBPM-2210 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Heiko Braun Assignee: Tom Baeyens Fix For: jBPM 4.0.0.CR1 As 5.1 is already CR1. We should have on the QA matrix. Hence the installer needs to support it. -- 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, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (JBPM-2429) Userguide has wrong URL for console

by Joram Barrez (JIRA)

Userguide has wrong URL for console ----------------------------------- Key: JBPM-2429 URL: https://jira.jboss.org/jira/browse/JBPM-2429 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.0 Reporter: Joram Barrez Assignee: Joram Barrez Priority: Minor Fix For: jBPM 4.1 Link to console (demo.setup) is still gwt-console, while it was renamed to jbpm-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, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-2062) remove version specification in module pom dependencies

by Tom Baeyens (JIRA)

remove version specification in module pom dependencies ------------------------------------------------------- Key: JBPM-2062 URL: https://jira.jboss.org/jira/browse/JBPM-2062 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens currently, the dependencies on jbpm modules have the version specified when they are used. this is also done in the parent pom so that is actually not necessary. the fix is that the version specification in the module poms should be removed. -- 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, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-2040) Inconsistent behaviour depending on the ordering of events (fork+end state+join)

by Thomas Diesler (JIRA)

Inconsistent behaviour depending on the ordering of events (fork+end state+join) -------------------------------------------------------------------------------- Key: JBPM-2040 URL: https://jira.jboss.org/jira/browse/JBPM-2040 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.2.3 Reporter: Mauro Molinari Assignee: Thomas Diesler Given the following process definition: <?xml version="1.0" encoding="UTF-8"?> <process-definition xmlns="urn:jbpm.org:jpdl-3.2" name="Complex"> <description> Complex description </description> <start-state name="start-state1"> <transition to="task-node1"></transition> </start-state> <task-node name="task-node3"> <task name="Task3_1"> <assignment actor-id="1"></assignment> </task> <transition to="end-state1"></transition> </task-node> <node name="node1"> <transition to="task-node3"></transition> </node> <join name="join1"> <transition to="node1"></transition> </join> <fork name="fork1"> <transition to="task-node2"></transition> <transition to="node2" name="to node2"></transition> <transition to="state1" name="to state1"></transition> </fork> <task-node name="task-node2"> <task name="Task2_1"> <assignment actor-id="1"></assignment> </task> <task name="Task2_2"> <assignment actor-id="1"></assignment> </task> <transition to="join1"></transition> </task-node> <task-node name="task-node1"> <task name="Task1_1"> <assignment actor-id="1"></assignment> </task> <transition to="fork1"></transition> </task-node> <node name="node2"> <transition to="end-state2"></transition> </node> <state name="state1"> <transition to="end-state2"></transition> </state> <end-state name="end-state1"></end-state> <end-state name="end-state2"></end-state> </process-definition> Try to do this: - create a process instance and start it - a Task1_1 instance is created: end it - the root token halts at the fork and three children tokens are created 1) the first causes the creation of a Task2_1 instance and of a Task2_2 instance 2) the second halts at the state1 state 3) the third dies at the end-state2 state Now, there are two cases: CASE A) - signal the second token: it then goes on and dies at end-state2 state - end Task2_1 and Task2_2 instances so that the first token goes on and reaches the join - now, the root token is restored and goes through node1 and task-node3 nodes, causing the creation of a Task3_1 instance This is what I would expect! CASE B) - end Task2_1 and Task2_2 instances so that the first token goes on and reaches the join - signal the second token: it then goes on and dies at end-state2 state - now, the root token is ended, halting the process instance! This is not the expected behaviour, as I would expect that the root token is restored because now all the sibling tokens of those that have reached the join node are ended, so the parent token (= the root token) should be restored and should continue to node1 and subsequent nodes. Moreover, I would not expect that the behaviour is different depending on the ordering of the actions "signal the state1 token" and "signal the task-node2 token". My suspect is this: in case B) the join node is not "triggered" anymore after Task2_1 and Task2_2 are ended, so it can't restore the parent node. Moreover, when the second children token is signalled, it reaches end-state2: jBPM then realizes that all of the sibling tokens are also ended, so it wrongly decides that the parent token should also be ended. -- 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, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPM-2347) Transitive dependency pointing to snapshot repository

by Johan Kumps (JIRA)

Transitive dependency pointing to snapshot repository ----------------------------------------------------- Key: JBPM-2347 URL: https://jira.jboss.org/jira/browse/JBPM-2347 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.0.CR1 Reporter: Johan Kumps Priority: Minor When adding the Jbpm dependancy to a pom.xml like this : <dependency> <groupId>org.jbpm.jbpm4</groupId> <artifactId>jbpm-pvm</artifactId> <version>4.0.CR1</version> </dependency> a transitive dependency is downloaded from the snapshot Jboss repository. It would be better to use the latest release in the default Jboss repository. Work around : <dependency> <groupId>org.jbpm.jbpm4</groupId> <artifactId>jbpm-pvm</artifactId> <version>4.0.CR1</version> <exclusions> <exclusion> <groupId>org.jboss.identity.idm</groupId> <artifactId>idm-core</artifactId> </exclusion> <exclusion> <groupId>org.jboss.identity.idm</groupId> <artifactId>idm-hibernate</artifactId> </exclusion> </exclusions> </dependency> <dependency> <groupId>org.jboss.identity.idm</groupId> <artifactId>idm-core</artifactId> <version>1.0.0.Alpha8</version> </dependency> <dependency> <groupId>org.jboss.identity.idm</groupId> <artifactId>idm-hibernate</artifactId> <version>1.0.0.Alpha8</version> </dependency> -- 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, 5 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues July 2009