January 2009 - jbpm-issues - Jboss List Archives

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

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-165?page=com.atlassian.jira.plugi... ] Thomas Diesler resolved JBPM-165. --------------------------------- Fix Version/s: (was: jBPM 3.3.2 GA ) Resolution: Out of Date Out of date for all Tasks and Feature Requests created before 1-Jan-2008 > process instance versioning > --------------------------- > > Key: JBPM-165 > URL: https://jira.jboss.org/jira/browse/JBPM-165 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > > 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. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-793) refresh the bare bones tutorial

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-793?page=com.atlassian.jira.plugi... ] Thomas Diesler resolved JBPM-793. --------------------------------- Resolution: Out of Date Out of date for all Tasks and Feature Requests created before 1-Jan-2008 > refresh the bare bones tutorial > ------------------------------- > > Key: JBPM-793 > URL: https://jira.jboss.org/jira/browse/JBPM-793 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Console > Reporter: Tom Baeyens > > Here's a good example of how it should look like: http://www.springframework.org/docs/MVC-step-by-step/Spring-MVC-step-by-s... > No graphical designer, start from the bare jbpm download, jdk 1.4.2 and ant. Work out a minimal example. > The main target audience is developers that want to see what jbpm does and how it works. Tooling should be excluded to prevent unnecessary noise for this use case. > The getting started that is currently on the wiki will be kept in coexistence. That shows jbpm step by step WITH the tooling. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-791) make email port in test suite configurable

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-791?page=com.atlassian.jira.plugi... ] Thomas Diesler resolved JBPM-791. --------------------------------- Resolution: Out of Date Out of date for all Tasks and Feature Requests created before 1-Jan-2008 > make email port in test suite configurable > ------------------------------------------ > > Key: JBPM-791 > URL: https://jira.jboss.org/jira/browse/JBPM-791 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > > we're using dumpster in the test suite for testing emails. but our continuous integration server doesn't allow for ports to be opened under 1024. so we need to find a way to tell dumpster to open up the fake mailserver on a different port. also we need to figure out how to tell the JavaMail API that mails should be sent using this different port... -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-616) prevent duplicate form submissions

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-616?page=com.atlassian.jira.plugi... ] Thomas Diesler resolved JBPM-616. --------------------------------- Resolution: Out of Date Out of date for all Tasks and Feature Requests created before 1-Jan-2008 > prevent duplicate form submissions > ---------------------------------- > > Key: JBPM-616 > URL: https://jira.jboss.org/jira/browse/JBPM-616 > Project: JBoss jBPM > Issue Type: Task > Components: Console > Reporter: Tom Baeyens > Priority: Minor > > for hints and tips, you can have a look at http://raibledesigns.com/page/rd?anchor=how_does_your_mvc_framework -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-569) improve EL expression examples in the user guide

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-569?page=com.atlassian.jira.plugi... ] Thomas Diesler resolved JBPM-569. --------------------------------- Fix Version/s: (was: jBPM 3.3.2 GA ) Resolution: Out of Date Out of date for all Tasks and Feature Requests created before 1-Jan-2008 > improve EL expression examples in the user guide > ------------------------------------------------ > > Key: JBPM-569 > URL: https://jira.jboss.org/jira/browse/JBPM-569 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Reporter: Tom Baeyens > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-567) create reusable JSF UI components in webapp

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-567?page=com.atlassian.jira.plugi... ] Thomas Diesler resolved JBPM-567. --------------------------------- Fix Version/s: (was: jBPM 3.3.2 GA ) Resolution: Out of Date Out of date for all Tasks and Feature Requests created before 1-Jan-2008 > create reusable JSF UI components in webapp > ------------------------------------------- > > Key: JBPM-567 > URL: https://jira.jboss.org/jira/browse/JBPM-567 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Console > Reporter: Tom Baeyens > > We plan to package the building blocks of the webapplication as reusable JSF UI components. Candidates are : the task list, the list of process definitions you can start, the task form, ... One of the main objectives of creating these components is that this will be the reuse done between the plain webapplication and using jBPM in a portal. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-564) jbpm community contribution tips

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-564?page=com.atlassian.jira.plugi... ] Thomas Diesler resolved JBPM-564. --------------------------------- Resolution: Out of Date Out of date for all Tasks and Feature Requests created before 1-Jan-2008 > jbpm community contribution tips > -------------------------------- > > Key: JBPM-564 > URL: https://jira.jboss.org/jira/browse/JBPM-564 > Project: JBoss jBPM > Issue Type: Task > Components: Documentation > Reporter: Tom Baeyens > Priority: Minor > > if you're looking for something to contribute. this issue links to issues that are good candidates to get you started. of course, you're always free to do your own proposal on the jbpm development forum: http://www.jboss.org/index.html?module=bb&op=viewforum&f=219 > regards, tom. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-479) Option to allow Tokens with activechildren not to continue transition

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-479?page=com.atlassian.jira.plugi... ] Thomas Diesler resolved JBPM-479. --------------------------------- Resolution: Out of Date Out of date for all Tasks and Feature Requests created before 1-Jan-2008 > Option to allow Tokens with activechildren not to continue transition > --------------------------------------------------------------------- > > Key: JBPM-479 > URL: https://jira.jboss.org/jira/browse/JBPM-479 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM 3.1.0 > Environment: any > Reporter: Elmo > Priority: Optional > > When a process instance (root token) is signalled in a fork, or in a subprocess, the process continues via the default leaving node. This is quite misleading. In my opinion the desired behavior would be blocking (i.e. means all child tokens must have ended) before continuing the transition. Although this can be managed through code, signalling the token (fork) by accident would give undesired results. If possible, I would like an option to stop the token from continuing if there are still active children. The code below illustrates this: > source: Token > public void signal() { > //initial checking > //proposed code: if option is used by developer, block the signal if there are active children > if( (CHECK_ACTIVECHILDREN_OPTION) && (this.hasActiveChildren()) ) > throw new IllegalStateException( "Cannot signal " + this + " if there are active children" ); > //signal routine > } > This option is false by default. I leave it to the group how they will set the option, either through the node definition (private) or to the process definition or maybe even through system properties (global). The users who will implement this must be aware of the consequences i.e. it is their responsibility to end the child tokens themselves or else it can never continue. This is only an option. I have not fully tested or did a full test case on the side effects of this, so I would appreciate if somebody could point this out because I have it implemented in my code. Thanks. > > Regards, > Elmo -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-436) make the tasks list in the inspect instance page sortable

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-436?page=com.atlassian.jira.plugi... ] Thomas Diesler resolved JBPM-436. --------------------------------- Resolution: Out of Date Out of date for all Tasks and Feature Requests created before 1-Jan-2008 > make the tasks list in the inspect instance page sortable > --------------------------------------------------------- > > Key: JBPM-436 > URL: https://jira.jboss.org/jira/browse/JBPM-436 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Console > Affects Versions: jBPM 3.1.0 > Reporter: Ronald van Kuijk > Priority: Trivial > > default sorted on id? or start date? or end-date? Any ideas? -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-412) have process start accept a map of variables

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-412?page=com.atlassian.jira.plugi... ] Thomas Diesler resolved JBPM-412. --------------------------------- Resolution: Out of Date Out of date for all Tasks and Feature Requests created before 1-Jan-2008 > have process start accept a map of variables > -------------------------------------------- > > Key: JBPM-412 > URL: https://jira.jboss.org/jira/browse/JBPM-412 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM 3.0.1 > Reporter: Ronald van Kuijk > Priority: Minor > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > The processstart api has no option of accepting variables. This way you cannot use them in the process-start event. This fires when it is started, before you can set any variables. Be passing e.g. a map of variables to the process start this becomes possible. -- 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, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues January 2009