May 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1403) First Pass WSRP Portlet Improvements

by Julien Viet (JIRA)

First Pass WSRP Portlet Improvements ------------------------------------ Key: JBPORTAL-1403 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1403 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.6.CR2 Reporter: Julien Viet Assigned To: Chris Laprun Fix For: 2.6 Final In the WSRP page, the pages portlet should be removed as it duplicates the same information as is in the Navigation tabs. Configured WSRP Consumers View Need more horizontal spacing between the "Create a consumer named:" label and the text box it is a label for. Need more vertical spacing between the consumer creation UI elements, and then defined consumer list. The Legend for the consumer list should not be (or appear to be) a row within the consumer list. This element should be below or above the consumer list. Linking the consumer name and providing an Action called "Configure" that both go to the same function is redundant. Either remove the Configure action or un-link the consumer name. The actions for the consumer should not be styled the same as the consumer name. I could cause confusion as users may percieve the actions are "active", "inactive", or "need refresh". There should be a space after the "pipe" separator in the WSRP consumer list to be consistent with the other action lists in the administrative portal. Consider using icon images (with alt attributes set to the name of the function) for actions in the list. Configuration View The form labels in this view are inconsistent with all the other field labels in the portlets in the administrative portal. I'm not saying they are bad (in fact, I personally prefer the style of these labels over the others), but they need to be made consistent with the rest of the admin portal labels, or the rest of the admin portal labels should be made to look like these labels. The vertical bars in front of the fields in this view are inconsistent with all of the other fields in the admin portal. The bars need to be removed. The buttons "Refresh", "Activate" and "Destroy" shouldn't be in the view that deals with changing the configuration of a WSRP consumer. These buttons should be removed. The "Save" and "Return to list" buttons should be on the left-bottom side of the portlet, and they should be sized, aligned, and padded consistently. The "Return to list" button label should be changed to "Cancel". -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-970) Identify version via log statement upon startup

by Dan Allen (JIRA)

Identify version via log statement upon startup ----------------------------------------------- Key: EJBTHREE-970 URL: http://jira.jboss.com/jira/browse/EJBTHREE-970 Project: EJB 3.0 Issue Type: Feature Request Components: Documentation, EJB3 Extensions Affects Versions: EJB 3.0 RC9 - Patch 1, EJB 3.0 RC9 - FD Environment: Sun Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode, sharing) Ubuntu Linux 7.04 Maven 2.0.6 Reporter: Dan Allen The problems with the remiss documentation regarding the versions of the libraries included in the EJB 3.0 distributions is already well represented in this issue tracker (EJBTHREE-621 EJBTHREE-512 EJBTHREE-596). However, aside from being more explicit with naming, there is another way to document which version is in use. Please add a DEBUG or INFO level log statement to the EJB 3.0 container startup class (such as in the EJB3StandaloneBoostrap) that identifies the version number of the distribution. Seam implements this feature by using the statement "Welcome to Seam 1.2.1.GA". I have found cases where this statement clued me into the fact that someone had named the jar file with a version number that was inconsistent with its contents. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBFORUMS-240) Indexing problem with creation of polls and attachments

by Ryszard Kozmik (JIRA)

Indexing problem with creation of polls and attachments ------------------------------------------------------- Key: JBFORUMS-240 URL: http://jira.jboss.com/jira/browse/JBFORUMS-240 Project: JBoss Forums Issue Type: Bug Components: Forum View Layer Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Fix For: 1.0.0 GA, 1.0.1 RC There are problems with indexing of polls answers and attachments when posting and using Update, Delete buttons. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-500) Special connective "or" constraint

by Michael Neale (JIRA)

Special connective "or" constraint ---------------------------------- Key: JBRULES-500 URL: http://jira.jboss.com/jira/browse/JBRULES-500 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Reteoo, Rule Assemply/SPI Reporter: Michael Neale Assigned To: Mark Proctor Would be nice to have some construct like Person(address == null or age < 30) which would kind of short circuit (ideally). Could be done as a special thing with alpha nodes, or another type of join node, or something else. This is a common problem to have for users. -- 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, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-948) ClusteredPostOffice should throw an exception when two nodes are started with the same ID

by Clebert Suconic (JIRA)

ClusteredPostOffice should throw an exception when two nodes are started with the same ID ----------------------------------------------------------------------------------------- Key: JBMESSAGING-948 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-948 Project: JBoss Messaging Issue Type: Feature Request Affects Versions: 1.2.0.SP1 Reporter: Clebert Suconic Assigned To: Clebert Suconic Fix For: 1.2.0.SP2 -- 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, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-955) Potential issue in calling JBM from web application

by Tim Fox (JIRA)

Potential issue in calling JBM from web application --------------------------------------------------- Key: JBMESSAGING-955 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-955 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.SP1 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.SP2 We need to investigate whether there is an issue in calling JBM from inside a web application co-located in same VM as JBM. The user has had difficulty in getting this to work. -- 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, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBTM-214) Transactions are not removed on completion resulting in OOMEs

by Leon van Zantvoort (JIRA)

Transactions are not removed on completion resulting in OOMEs ------------------------------------------------------------- Key: JBTM-214 URL: http://jira.jboss.com/jira/browse/JBTM-214 Project: JBoss Transaction Manager Issue Type: Patch Security Level: Public (Everyone can see) Affects Versions: 4.2.3, 4.2.2, 4.2.1, 4.2 Reporter: Leon van Zantvoort Assigned To: Mark Little Priority: Critical Attachments: TransactionReaper.java Please find attached a patched TransactionReaper class. This patch fixes a memory issue, which is seen in JavaSE (stand-alone client) applications integrating JBossTS. An OOME is raised in case the client application starts multiple (timeout bound) transactions concurrently. More information can be found at line 374 of the patched class. -- 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, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (JBREM-744) Release 2.2.0.SP4

by Ron Sigal (JIRA)

Release 2.2.0.SP4 ----------------- Key: JBREM-744 URL: http://jira.jboss.com/jira/browse/JBREM-744 Project: JBoss Remoting Issue Type: Release Security Level: Public (Everyone can see) Affects Versions: 2.2.0.SP4 Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.SP4 -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-742) Release 2.2.0.SP3

by Ron Sigal (JIRA)

Release 2.2.0.SP3 ----------------- Key: JBREM-742 URL: http://jira.jboss.com/jira/browse/JBREM-742 Project: JBoss Remoting Issue Type: Release Security Level: Public (Everyone can see) Affects Versions: 2.2.0.SP3 Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.SP3 -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-740) Release 2.2.0.SP2

by Ron Sigal (JIRA)

Release 2.2.0.SP2 ----------------- Key: JBREM-740 URL: http://jira.jboss.com/jira/browse/JBREM-740 Project: JBoss Remoting Issue Type: Release Security Level: Public (Everyone can see) Affects Versions: 2.2.0.SP2 Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.SP2 -- 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, 2 months

1
1
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 May 2007