December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPM-790) binary and source version are not in synch

by hakan eryargi (JIRA)

binary and source version are not in synch ------------------------------------------ Key: JBPM-790 URL: http://jira.jboss.com/jira/browse/JBPM-790 Project: JBoss jBPM Issue Type: Task Components: Graphical Process Designer Reporter: hakan eryargi Assigned To: Tom Baeyens binary and source version are not in synch current binary version is 3.0.11 and source version at cvs is 3.0.9.2. can you please sync them -- 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, 6 months

2
1
0 / 0

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

by Tom Baeyens (JIRA)

remember the previous form generation data fields ------------------------------------------------- Key: JBPM-779 URL: http://jira.jboss.com/jira/browse/JBPM-779 Project: JBoss jBPM Issue Type: Feature Request Components: Graphical Process Designer Reporter: Tom Baeyens Assigned To: Koen Aers Fix For: jBPM 3.2 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

19 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-727) add support for adding Action to Nodes without adding Event

by mehmet bozok (JIRA)

add support for adding Action to Nodes without adding Event ----------------------------------------------------------- Key: JBPM-727 URL: http://jira.jboss.com/jira/browse/JBPM-727 Project: JBoss jBPM Issue Type: Feature Request Components: Graphical Process Designer Reporter: mehmet bozok Assigned To: Tom Baeyens We are extending some parts of GDP in our project, and we need to add Action to Node without adding an Event then show this Aciton on outline tree view. Althought there is a mechanism to add a single Action to Nodes(not in GDP menu but implemented in org.jbpm.ui.model.Node), it is not shown at outline tree view. In order to make Action appear on tree view as a Node child we needed to add a menu option, and handle ActionTreeEditPart and NodeTreeEditpart relation in a different way. (not by changing GPD code, but instantiating editparts then reflecting org.eclipse.gef.AbstractEditPart and calling its protected methods which is not a very safe way.) Therefore it seems neccesary to change iplementation so that single Action (also providing which Action to add) can be added to Node and shown in outline tree 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, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-326) Run testsuite by default with udp.xml, tcp.xml and tcp-nio.xml

by Bela Ban (JIRA)

Run testsuite by default with udp.xml, tcp.xml and tcp-nio.xml -------------------------------------------------------------- Key: JGRP-326 URL: http://jira.jboss.com/jira/browse/JGRP-326 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 -- 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, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-398) Replace all _OK events with method calls to passUp() or passDown()

by Bela Ban (JIRA)

Replace all _OK events with method calls to passUp() or passDown() ------------------------------------------------------------------- Key: JGRP-398 URL: http://jira.jboss.com/jira/browse/JGRP-398 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-303) Verify that all synchronized statements have short scopes

by Bela Ban (JIRA)

Verify that all synchronized statements have short scopes --------------------------------------------------------- Key: JGRP-303 URL: http://jira.jboss.com/jira/browse/JGRP-303 Project: JGroups Issue Type: Task Affects Versions: 2.3 SP1 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.4 In all cases when we have a passUp() or passDown() call from within a synchronized statement, we need to verify whether (a) we can call passDown()/passUp() outside the synchronized statement or (b) whether there is a potential deadlock if we don't -- 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, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-378) TLS: check all major protocols for thread safety (reentrant up() methods)

by Bela Ban (JIRA)

TLS: check all major protocols for thread safety (reentrant up() methods) ------------------------------------------------------------------------- Key: JGRP-378 URL: http://jira.jboss.com/jira/browse/JGRP-378 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 So far, the down() methods could get executed in parallel, by different threads calling Channel.send(), However, this was not the case for up(), where we could assume only 1 thread was calling up() at a time. This changed with the threadless stack (TLS) and we need to make sure all of our protocols' up() methods are thread safe -- 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, 6 months

1
4
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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-794) Same JBPM project shared with each person having different JBPM installation program causes crash.

by Mark Ricard (JIRA)

Same JBPM project shared with each person having different JBPM installation program causes crash. -------------------------------------------------------------------------------------------------- Key: JBPM-794 URL: http://jira.jboss.com/jira/browse/JBPM-794 Project: JBoss jBPM Issue Type: Bug Components: Graphical Process Designer Affects Versions: jBPM 3.1.2 Environment: Eclipse, MyEclipseIDE, JBPM 3.1.2 Reporter: Mark Ricard Assigned To: Tom Baeyens To duplicate have two development machines with exactly the same versions of the software except have the Window->Preferences->JBoss jBPM installation locations in different places. Have one of the people create a jBPM project, zip up that project and send it to the user of machine 2. Then have machine 2 import that project into Eclipse. Everything blows up. Many of the other non-related projects in the project tree also begin displaying erratic behavior. If both users now synchronize to have their IDEs point to the same jBPM path on each of their machines, the project opens up fine. -- 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, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (GPD-8) Add JBoss EULA

by Rajesh Rajasekaran (JIRA)

Add JBoss EULA -------------- Key: GPD-8 URL: http://jira.jboss.com/jira/browse/GPD-8 Project: JBoss jBPM GPD Issue Type: Task Reporter: Rajesh Rajasekaran Assigned To: Koen Aers Fix For: 3.0.12 Attachments: JBossORG-EULA.txt Attached is the JBossORG-EULA.txt 1. The eula should be checked into the project's source tree. 2. The project's build should include the EULA in project distributables, ie, whatever is the unit of publish: zip, tgz, etc. -- 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, 6 months

2
3
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 December 2006