April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (GPD-50) review the packaging mechanism

by Koen Aers (JIRA)

review the packaging mechanism ------------------------------ Key: GPD-50 URL: http://jira.jboss.com/jira/browse/GPD-50 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl Reporter: Koen Aers Assigned To: Koen Aers Leverage the eclipse packager mechanism to include the necessary features in the distributable and make the site installation mechanism work again. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

2
2
0 / 0

[JBoss JIRA] Created: (GPD-18) Reordering graph elements in outline view

by Koen Aers (JIRA)

Reordering graph elements in outline view ----------------------------------------- Key: GPD-18 URL: http://jira.jboss.com/jira/browse/GPD-18 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0 alpha1 Reporter: Koen Aers Assigned To: Koen Aers Reordering elements is possible by directly editing the xml. It should be possible to obtain the same effect by dragging and dropping elements in the outline view. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

2
2
0 / 0

[JBoss JIRA] Created: (GPD-54) Label and name support for graph elements

by Koen Aers (JIRA)

Label and name support for graph elements ----------------------------------------- Key: GPD-54 URL: http://jira.jboss.com/jira/browse/GPD-54 Project: JBoss jBPM GPD Issue Type: Feature Request Affects Versions: jBPM JPDL Designer 3.1.0.alpha2 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.alpha3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

3
15
0 / 0

[JBoss JIRA] Created: (GPD-38) Comment in graphical editor (UML annotations)

by Koen Aers (JIRA)

Comment in graphical editor (UML annotations) --------------------------------------------- Key: GPD-38 URL: http://jira.jboss.com/jira/browse/GPD-38 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl Reporter: Koen Aers Assigned To: Koen Aers It should be possible to annotate the graphical elements in the graphical editor with comments. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

2
3
0 / 0

[JBoss JIRA] Created: (GPD-26) Offer the GPD as a standalone package

by Koen Aers (JIRA)

Offer the GPD as a standalone package ------------------------------------- Key: GPD-26 URL: http://jira.jboss.com/jira/browse/GPD-26 Project: JBoss jBPM GPD Issue Type: Task Reporter: Koen Aers Assigned To: Koen Aers This can be done in a number of ways: - Most easy way is to use the perspective mechanism to distinguish between a 'developer' and a 'analist' perspective - Another way is to deliver the designer as an Eclipse RCP application -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

3
6
0 / 0

[JBoss JIRA] Created: (GPD-9) save deployment options

by Brice Ruth (JIRA)

save deployment options ----------------------- Key: GPD-9 URL: http://jira.jboss.com/jira/browse/GPD-9 Project: JBoss jBPM GPD Issue Type: Feature Request Affects Versions: 3.0.11 Reporter: Brice Ruth Assigned To: Koen Aers The current jBPM Process Designer plugin for Eclipse does not save deployment settings for a process definition. It would be useful to set remote deploy settings as a workspace preference (host/port/path). Then, what files are to be deployed (gpd.xml, processdefinition.xml, processimage.xml, src files, etc.) should be saved per process, and stored as part of the project/process files (whichever, just not in .metadata, so it can be committed to CVS and shared by a team). JBoss Support Case: 00012512 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

3
9
0 / 0

[JBoss JIRA] Created: (GPD-40) A slash character in Task Node name causes crash. Graphical Process Designer allows the slash to be entered anyway.

by Koen Aers (JIRA)

A slash character in Task Node name causes crash. Graphical Process Designer allows the slash to be entered anyway. ------------------------------------------------------------------------------------------------------------------- Key: GPD-40 URL: http://jira.jboss.com/jira/browse/GPD-40 Project: JBoss jBPM GPD Issue Type: Bug Components: jpdl Reporter: Koen Aers Assigned To: Koen Aers The Graphical Process Designer allows the user to enter a Task Node name that includes a slash, such as "Accounting/Finance". The slash causes a crash later on when the process is run, and it isn't obvious what the source of the problem is. Suggestion: somehow prevent the user from entering a name that includes a slash. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

2
7
0 / 0

[JBoss JIRA] Created: (GPD-51) Integration of web console in GPD

by Koen Aers (JIRA)

Integration of web console in GPD --------------------------------- Key: GPD-51 URL: http://jira.jboss.com/jira/browse/GPD-51 Project: JBoss jBPM GPD Issue Type: Feature Request Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.beta1 Provide a number of links (throug hyperlinks or menu buttons) that open a browser on the configured url pointing at a jBPM server installation. These options should be disabled if no server installation is configured. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

2
5
0 / 0

[JBoss JIRA] Created: (GPD-33) remember the previous form generation data fields

by Koen Aers (JIRA)

remember the previous form generation data fields ------------------------------------------------- Key: GPD-33 URL: http://jira.jboss.com/jira/browse/GPD-33 Project: JBoss jBPM GPD Issue Type: Feature Request Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0 alpha1 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.alpha3 In the form generation, we currently start from the data entered in the task controller (if any) Whenever a form is generated, I would like the form generation data to be stored in the gpd.xml. Then, whenever the user does a second generation, the taskform generation form is prefilled with the previous data instead of starting from the controller data again. The motivation for this is that mostly people will not have controllers. Then if they have 5 data items to display and collect, it takes a lot of clicking. Users don't want to redo this effort for every little change they want to make to the form (additions and removals of fields). I think users should be able to live with the fact that controller data items are not kept automatically in sync with the task form data items. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

3
10
0 / 0

[JBoss JIRA] Created: (GPD-20) refactor naming strategy

by Koen Aers (JIRA)

refactor naming strategy ------------------------ Key: GPD-20 URL: http://jira.jboss.com/jira/browse/GPD-20 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0 alpha1 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.alpha3 1) generate default node names when nodes are created: {node1, node2, ...}. use this naming strategy for each node type. 2) do not generate a node name for the start-state. users should be able to give the start-state a name, though. 3) use the following naming strategy for end states: {end, end2, end3, end4, ...} 4) do not generate names for transitions. the problem reporting should generate warnings if a node-type requires named nodes. the correlation between the graphical information and the processdefinition.xml will be done based on the position (index), rather then on the name. 5) disallow slashes in names in a process definition (nodes, transitions, process definition, actions, ...) Because slashes will be used as a separator in hierarchical names. We should also investigate if it would be useful to specify a strict set of chars that can be used like e.g. 0-9,a-z,A-Z,space,dot -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

2
11
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2007