January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBPM-127) create packaging strategy

by Koen Aers (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-127?page=all ] Koen Aers closed JBPM-127. -------------------------- Resolution: Done This is also done through the use of the deployment page in the editor. GPD-9 is related. > create packaging strategy > ------------------------- > > Key: JBPM-127 > URL: http://jira.jboss.com/jira/browse/JBPM-127 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Graphical Process Designer > Reporter: Tom Baeyens > Assigned To: Koen Aers > > add links from the graphical information to the process definition, forms and classes so that a .par file can be generated. > The data should be editable in the graphical process designer and should correspond to the data for the ant zip task. ideally this information should be stored as an ant-zip-task in the *.gpd.xml > Packaging can then be based on this and zip task. A ant build file is generated from the ant zip task in some temporary location. then executed. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-194) deploy a process archive

by Koen Aers (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-194?page=all ] Koen Aers closed JBPM-194. -------------------------- Resolution: Done This is now done through the use of the deployment page in the editor. > deploy a process archive > ------------------------ > > Key: JBPM-194 > URL: http://jira.jboss.com/jira/browse/JBPM-194 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Graphical Process Designer > Reporter: Tom Baeyens > Assigned To: Koen Aers > > in a first phase, the configuration of the database could be done by means of a hibernate.cfg.xml file in the jbpm class path (in the plugin?) > then a special deploy button (or menu-item) could be displayed. that uses this configuration to deploy a process to a jbpm database. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-206) Add support for the process-state

by Koen Aers (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-206?page=all ] Koen Aers closed JBPM-206. -------------------------- Resolution: Done Replaced by GPD-21 > Add support for the process-state > --------------------------------- > > Key: JBPM-206 > URL: http://jira.jboss.com/jira/browse/JBPM-206 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Graphical Process Designer > Reporter: Koen Aers > Assigned To: Koen Aers > > Basic support is already provided. What still needs to be added is a way to configure. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-202) refactor naming strategy

by Koen Aers (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-202?page=all ] Koen Aers closed JBPM-202. -------------------------- Resolution: Done Replaced by GPD-20 > refactor naming strategy > ------------------------ > > Key: JBPM-202 > URL: http://jira.jboss.com/jira/browse/JBPM-202 > Project: JBoss jBPM > Issue Type: Task > Components: Graphical Process Designer > Reporter: Koen Aers > Assigned To: Koen Aers > > 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-205) Endpoint Editing

by Koen Aers (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-205?page=all ] Koen Aers closed JBPM-205. -------------------------- Resolution: Done Replaced by GPD-19 > Endpoint Editing > ---------------- > > Key: JBPM-205 > URL: http://jira.jboss.com/jira/browse/JBPM-205 > Project: JBoss jBPM > Issue Type: Task > Components: Graphical Process Designer > Reporter: Koen Aers > Assigned To: Koen Aers > > Move endpoints of connections to wherever location on the edge of a node. Involves implementing a particular form of anchor point. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-201) Reordering graph elements in outline view

by Koen Aers (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-201?page=all ] Koen Aers closed JBPM-201. -------------------------- Resolution: Done Replaced by GPD-18 > Reordering graph elements in outline view > ----------------------------------------- > > Key: JBPM-201 > URL: http://jira.jboss.com/jira/browse/JBPM-201 > Project: JBoss jBPM > Issue Type: Task > Components: Graphical Process Designer > 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-755) streamline designer build

by Tom Baeyens (JIRA)

streamline designer build ------------------------- Key: JBPM-755 URL: http://jira.jboss.com/jira/browse/JBPM-755 Project: JBoss jBPM Issue Type: Task Components: Graphical Process Designer Reporter: Tom Baeyens Assigned To: Koen Aers Priority: Critical 1) Remove usage of jbpm.version. * The docs should not be included directly in the designer plugin. Instead, in the help docs, a reference should be published to the docs of the configured runtimes. * The jbpm version constant should be removed cause it's not used any more. When fixing this, make sure to do a search for jbpm.version. 2) Rename jbpm.gpd.version to module.version so that it is in sync with all other jbpm subprojects. Make sure that the used definition is located in the version.properties file and that the property definition in the build.xml is removed. 3) Remove all CVS checkout stuff. Have the build fail in case one of the submodules is not present. No cvs checkout should be done in case a module is missing. Later we'll define a cvs checkout script in the overall build. -- 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

19 years, 3 months

2
2
0 / 0

[JBoss JIRA] Closed: (JBPM-553) gpd user guide documentation

by Koen Aers (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-553?page=all ] Koen Aers closed JBPM-553. -------------------------- Resolution: Done Replaced by GPD-17 > gpd user guide documentation > ---------------------------- > > Key: JBPM-553 > URL: http://jira.jboss.com/jira/browse/JBPM-553 > Project: JBoss jBPM > Issue Type: Task > Components: Graphical Process Designer > Reporter: Tom Baeyens > Assigned To: Koen Aers > Priority: Critical > -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-532) moving nodes around currupts process

by Koen Aers (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-532?page=all ] Koen Aers closed JBPM-532. -------------------------- Resolution: Done replaced by GPD-16 > moving nodes around currupts process > ------------------------------------ > > Key: JBPM-532 > URL: http://jira.jboss.com/jira/browse/JBPM-532 > Project: JBoss jBPM > Issue Type: Bug > Components: Graphical Process Designer > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Priority: Critical > > in the XML i moves some nodes around. that lead to a corrupted graphical view. i tried to delete the whole gpd.xml content (and then the whole) file in the hope that the graphical content would be restored, but instead i lost the content of the processdefinition.xml and had to start all over 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-529) add a readme in the create-project wizard

by Koen Aers (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-529?page=all ] Koen Aers closed JBPM-529. -------------------------- Resolution: Done replaced by GPD-15 > add a readme in the create-project wizard > ----------------------------------------- > > Key: JBPM-529 > URL: http://jira.jboss.com/jira/browse/JBPM-529 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Graphical Process Designer > Reporter: Tom Baeyens > Assigned To: Koen Aers > Priority: Critical > > all features that help beginner get started are vital imho. therefor, i think the forum user points out a good opportunity for us: we could create a readme.txt in the root of the generated project. that readme is opened when the wizard creates the project and it explains the contents of the project and what do to next. -- 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

19 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2007