September 2010 - richfaces-issues

[JBoss JIRA] Created: (RF-8102) Development: dataTable columns menus support

by Anton Belevich (JIRA)

Development: dataTable columns menus support -------------------------------------------- Key: RF-8102 URL: https://jira.jboss.org/jira/browse/RF-8102 Project: RichFaces Issue Type: Sub-task Reporter: Anton Belevich Assignee: Anton Belevich Fix For: 4.0.0.BETA2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
6
0 / 0

[JBoss JIRA] Created: (RF-7611) fix default column width assigned to extendedDataTable

by Prabhat Jha (JIRA)

fix default column width assigned to extendedDataTable ------------------------------------------------------ Key: RF-7611 URL: https://jira.jboss.org/jira/browse/RF-7611 Project: RichFaces Issue Type: Bug Components: component-tables Affects Versions: 3.3.1 Reporter: Prabhat Jha Fix For: 3.3.2.CR1 See the referenced forum entry. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
11
0 / 0

[JBoss JIRA] Created: (RF-7718) statuses grouping in 4.0

by Ilya Shaikovsky (JIRA)

statuses grouping in 4.0 ------------------------ Key: RF-7718 URL: https://jira.jboss.org/jira/browse/RF-7718 Project: RichFaces Issue Type: Feature Request Components: component-a4j-core Affects Versions: 4.0.0.ALPHA1 Reporter: Ilya Shaikovsky Assignee: Nick Belaevski Fix For: 4.0.0.BETA1 check Nick's sample on grouping statuses. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
4
0 / 0

[JBoss JIRA] Created: (RF-7538) enable submit button when all the required fields within the form/region are set propertly

by Gary Hu (JIRA)

enable submit button when all the required fields within the form/region are set propertly ------------------------------------------------------------------------------------------ Key: RF-7538 URL: https://jira.jboss.org/jira/browse/RF-7538 Project: RichFaces Issue Type: Feature Request Reporter: Gary Hu The submit button is not enabled until all the required fields within the form/region are set properly. I can think of two ways to implement it. 1) add a new attribute to a4j:form/a4j:rigion to indicate that if this feature is turned on/off. In addition, new attributes could be added to indicate the ids of the submit button, and/or ids of the required fields. For example: <a4j:form id="myForm" enableSubmitButtonForRequriedFields="true" submitButtonId="btnId" requiredFieldIds="id1,id2..." /> 2) add a new attribute to a a4j:commandButton to indicate if this feature is turned on/off. In addtion, new attributes could be added to indicate the ids of the form/region and/or the ids of the required fields. For example: <a4j:commandButton id="btnId" enableSubmitButtonForRequriedFields="true" parentidforrequiredfields="myForm" /> The example showed above means after all the required fields are set properly with the form "myForm" the button is enable. <a4j:commandButton id="btnId" enableSubmitButtonForRequriedFields="true" requiredFieldIds="id1, id2..." /> The example showed above means after all the required fields specified by the attribute "requiredFieldIds" are set properly the button is enabled. Of course, the attribute "enableSubmitButtonForRequriedFields" could be optional. So only the "parentidforrequiredfields" or "requiredFieldIds" is checked to determine if the button needs to be enabled/disable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

5
11
0 / 0

[JBoss JIRA] Created: (RF-7492) a4j:queue support for standard form submits as well as AJAX request

by Jay Balunas (JIRA)

a4j:queue support for standard form submits as well as AJAX request ------------------------------------------------------------------- Key: RF-7492 URL: https://jira.jboss.org/jira/browse/RF-7492 Project: RichFaces Issue Type: Feature Request Components: component-misc Affects Versions: 3.3.1 Reporter: Jay Balunas Fix For: 4.0.0.BETA1 a4j:queue does not currently support forwarding standard form requests through an a4j:queue. This means that input items that are ajax enabled may be processed through a queue, but if the user clicks submit on the form that request that fire before items in the queue. A user reported a work around. Use a4j:commandButton and then rerender the most of the page - not optimal. We need to create an FAQ for the work around and investigate the standard form support. Brainstorming: This behavior may not be possible on a global or page coped queue. A form scoped a4j:queue could behave like a4j:support and inject the needed behavior into the form tag. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
3
0 / 0

[JBoss JIRA] Created: (RF-6524) maxRequestSize for richfile upload should be made configurable per component and not globally.

by sathay sayee (JIRA)

maxRequestSize for richfile upload should be made configurable per component and not globally. ---------------------------------------------------------------------------------------------- Key: RF-6524 URL: https://jira.jboss.org/jira/browse/RF-6524 Project: RichFaces Issue Type: Feature Request Affects Versions: 3.3.0 Environment: ALL Reporter: sathay sayee The Richfaces fileupload control currently has maxRequestSize attribute which can be passed as a init-param in the web.xml It would be better if it can be configured on a percontrol basis and not global. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

6
7
0 / 0

[JBoss JIRA] Created: (RF-5406) Calendar: add the additional attribute to set 'immediate' option for ajax request caused by component's controls buttons & links

by Andrei Markavtsov (JIRA)

Calendar: add the additional attribute to set 'immediate' option for ajax request caused by component's controls buttons & links -------------------------------------------------------------------------------------------------------------------------------- Key: RF-5406 URL: https://jira.jboss.org/jira/browse/RF-5406 Project: RichFaces Issue Type: Task Reporter: Andrei Markavtsov Assignee: Nick Belaevski Currently calendar has 'immediate' attribute. It should be applied for component input value. Additional attribute should be implemeted to set 'immediate' option for each ajax request caused by component'c controls such as change month/year, apply button and etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
5
0 / 0

[JBoss JIRA] Created: (RF-1870) Need to allow for single set of headers with datatable and embedded datatable

by David M. Karr (JIRA)

Need to allow for single set of headers with datatable and embedded datatable ----------------------------------------------------------------------------- Key: RF-1870 URL: http://jira.jboss.com/jira/browse/RF-1870 Project: RichFaces Issue Type: Feature Request Affects Versions: 3.1.3 Reporter: David M. Karr Priority: Minor I have a need to present a datatable that models the information in a spreadsheet. As such, some of the columns are "scalars", which represent a single value per entity, and some of the columns are multi-valued, such that multiple row values correspond to a single entity. For instance, consider the notion of a "Project" entity with "name" and "department" fields, along with a "servers" list property. Each server has "hostname", "cpuCount", and "platform" fields. I want to display a table with a single list of column headers, being "name", "department", "host name", "cpu count", and "platform" (and some others). One row in the "projects" table will have an embedded table for servers. In current functionality in v3.1.2, I can have a single header in the main datatable that corresponds to the embedded datatable (like "Servers"), and I can have headers in the embedded datatable (which would repeat for every project row), but there appears to be no way to just have a single set of headers representing all the existing columns unioned from the main datatable and the embedded datatable. I've looked at the "subTable" component, but this doesn't appear to do what I need. I will attach some artifacts that demonstrate what I'm trying to achieve. -- 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

14 years

5
22
0 / 0

[JBoss JIRA] Created: (RF-8546) improve pick/ordering/shuttle lists keyboard support

by Ilya Shaikovsky (JIRA)

improve pick/ordering/shuttle lists keyboard support ---------------------------------------------------- Key: RF-8546 URL: https://jira.jboss.org/jira/browse/RF-8546 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.3.3.CR1 Reporter: Ilya Shaikovsky Assignee: Nick Belaevski Good RFC from comunity for 4.x components improvements. http://community.jboss.org/message/533910#533910 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
7
0 / 0

[JBoss JIRA] Created: (RF-7844) FileUpload: add attribute to trim file path

by Nick Belaevski (JIRA)

FileUpload: add attribute to trim file path ------------------------------------------- Key: RF-7844 URL: https://jira.jboss.org/jira/browse/RF-7844 Project: RichFaces Issue Type: Feature Request Components: component-input Affects Versions: 3.3.2.CR1 Reporter: Nick Belaevski Assignee: Nick Belaevski Fix For: Future This attribute should control whether full file path is shown in rich:fileUpload control or just a file name -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues September 2010