December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3473) Fix DistributedStateImpl.nodeRemove

by Brian Stansberry (JIRA)

Fix DistributedStateImpl.nodeRemove ----------------------------------- Key: JBAS-3473 URL: http://jira.jboss.com/jira/browse/JBAS-3473 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta AFAICT, this is not correct. Key/value pairs are stored in the category node's data map; nodeRemoved treats things as if each key is its own node. Actually, I think the node per key approach is correct, until TreeCacheListener can provide info on what data was changed. Also, remove() itself notifies listeners of a removal, and then the listener does as well. Needs to be one or the other; probably nodeRemoved() as that gets called for both local and remote removes. -- 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

17 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-698) gpd is not working with latest version of commons-fileupload jar.

by Olivier Debels (JIRA)

gpd is not working with latest version of commons-fileupload jar. ----------------------------------------------------------------- Key: JBPM-698 URL: http://jira.jboss.com/jira/browse/JBPM-698 Project: JBoss jBPM Issue Type: Bug Components: Graphical Process Designer Reporter: Olivier Debels Assigned To: Tom Baeyens When trying to used the graphical process designer with the latest version of commons-upload (version 1.1.1) it is not longer possible to deploy process definitions. You get the exception 'The process definition was rejected because no multiplart boundary was found'. The reason is that the gpd is using a ',' to separate its content type (in the url used to trigger the upload servlet) where it must be a ';' according to RFC1341. So instead of 'multipart/form-data,boundary=AaB03x' it must be 'multipart/form-data;boundary=AaB03x'. The webapp must work with the latest version of commons-fileupload. -- 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

17 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAOP-332) Surpress transformation errors is ignored

by Kabir Khan (JIRA)

Surpress transformation errors is ignored ----------------------------------------- Key: JBAOP-332 URL: http://jira.jboss.com/jira/browse/JBAOP-332 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.5.2.GA Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 1.5.3.GA, 2.0.0.alpha3 See if this is the case for 2.0.0.alpha2 as well -- 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

17 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-382) TLS: check whether interruption policies are implemented correctly

by Bela Ban (JIRA)

TLS: check whether interruption policies are implemented correctly ------------------------------------------------------------------ Key: JGRP-382 URL: http://jira.jboss.com/jira/browse/JGRP-382 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 - Look at thread interruption policies. Are we handling these correctly ? - There are some exceptions due to uncaught interrupt exceptions - PooledExecutor.shutdownNow() interrupts all threads, therefore they need to handle interruptions correctly Suggested reading: Java Concurrency in Practice (Goetz) chapter 7 -- 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

17 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-699) build.xml needs to be modified for jbpm to build successfully

by Prabhat Jha (JIRA)

build.xml needs to be modified for jbpm to build successfully ------------------------------------------------------------- Key: JBPM-699 URL: http://jira.jboss.com/jira/browse/JBPM-699 Project: JBoss jBPM Issue Type: Task Reporter: Prabhat Jha Assigned To: Koen Aers Priority: Minor To build jBPM successfully, I had to make the following changes. A. Add the constructs to create missing directories under target "download-eclipse" in jbpm.dist\build.xml <mkdir dir="${local-repository}/${eclipse-folder}"/> <mkdir dir="${local-repository}/${webtools-folder}"/> <mkdir dir="${local-repository}/${emf-folder}"/> <mkdir dir="${local-repository}/${gef-folder}"/> <mkdir dir="${local-repository}/${jem-folder}"/> B. Modify the <import file > under jbpm.dist\build\projects\docs\gpd.userguide as <import file="../../docbook-support/support.xml" /> Can you check in these changes in CVS? I am not sure if you are the right person. Thanks, Prabhat -- 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

17 years, 9 months

3
8
0 / 0

[JBoss JIRA] Created: (JBPM-773) gpd deploy tab defaults to jbpm-console

by David Owens (JIRA)

gpd deploy tab defaults to jbpm-console --------------------------------------- Key: JBPM-773 URL: http://jira.jboss.com/jira/browse/JBPM-773 Project: JBoss jBPM Issue Type: Bug Components: Graphical Process Designer Environment: Eclipse 3.2 Reporter: David Owens Assigned To: Tom Baeyens Priority: Minor In the GPD, in the deploy tab, under Deployment Server Settings, the value for Server Deployer defaults to jbpm-console/upload, but should be jbpm/upload -- 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

17 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBPM-784) Re-generating a form adds a duplicate entry in forms.xml

by Ronald van Kuijk (JIRA)

Re-generating a form adds a duplicate entry in forms.xml -------------------------------------------------------- Key: JBPM-784 URL: http://jira.jboss.com/jira/browse/JBPM-784 Project: JBoss jBPM Issue Type: Bug Components: Graphical Process Designer Environment: Eclipse 3.2, GPD from CVS JDK 1.4/1.5 Reporter: Ronald van Kuijk Assigned To: Koen Aers Priority: Minor Re-generating a form adds a duplicate entry in forms.xml This is imo unwanted behaviour -- 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

17 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-281) Fix conosle import.sql script execution for HSQLDB

by Tom Fennelly (JIRA)

Fix conosle import.sql script execution for HSQLDB -------------------------------------------------- Key: JBESB-281 URL: http://jira.jboss.com/jira/browse/JBESB-281 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.0 RC1 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 5.0 Hibernate/HSQLDB (possibly the Hibernate HSQLDB dialect impl) throws an exception when executing the import.sql script (it's just a seeding script - load of insert statements). Syas there are characters in the script the it down't like. Same script runs fine on postgres. -- 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

17 years, 9 months

3
7
0 / 0

[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

17 years, 9 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

17 years, 9 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2006