January 2010 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-5759) Rich:tabPanel impossible to switch to tab with ajaxSingle="true"

by Alexandr Levkovsky (JIRA)

Rich:tabPanel impossible to switch to tab with ajaxSingle="true" ---------------------------------------------------------------- Key: RF-5759 URL: https://jira.jboss.org/jira/browse/RF-5759 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.0 Reporter: Alexandr Levkovsky Impossible to switch to tab with ajaxSingle="true" in tabPanel with switchType="ajax". -- 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

13 years, 11 months

5
13
0 / 0

[JBoss JIRA] Created: (RF-8330) Download links created with a4j:mediaOutput are unusable for inexperienced end users

by alex winizki (JIRA)

Download links created with a4j:mediaOutput are unusable for inexperienced end users ------------------------------------------------------------------------------------ Key: RF-8330 URL: https://jira.jboss.org/jira/browse/RF-8330 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-output Affects Versions: 3.3.2.SR1 Environment: OS-independent Reporter: alex winizki Priority: Minor Creating a download link with a4j:mediaOutput yields an <a where the URL in the href is several hundred characters long and ends with .jsf regardless of the content type. If the end user tries to download the file then, depending on the browser settings, the following happens: -- if the browser is configured to store all downloads in a given folder and the user left-clicks on the link, then nothing happens. The only chance is to right- click on the link and select "save as". -- if the "save as" dialogue opens because the user selected it by right- clicking or because the browser is configured to ask each time for the folder to save the file, then the suggested file name is several hundred characters long and always ends with .jsf. Accepting the suggested file name usually results in an OS error "illegal filename". The user has to rename the file and give it the right extension (which he/she has to know) in order to be able to download the document and open it. -- 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

13 years, 11 months

3
8
0 / 0

[JBoss JIRA] Created: (RF-4464) inputNumberSlider: component incorrect behavior inside rich:tabPanel during swith between tabs.

by Mikhail Vitenkov (JIRA)

inputNumberSlider: component incorrect behavior inside rich:tabPanel during swith between tabs. ----------------------------------------------------------------------------------------------- Key: RF-4464 URL: https://jira.jboss.org/jira/browse/RF-4464 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.0 Environment: IE6, IE7, FF 3.1, Safari 3.1, Opera 9.52(3.3.0) Reporter: Mikhail Vitenkov Assignee: Nick Belaevski #1. Add following code on the page(rich:tabPanel with two tabs, which contained inputNumberSlider component): <h:form> <rich:tabPanel switchType="client"> <rich:tab label="First"> Here is tab #1 <rich:inputNumberSlider value="10" /> </rich:tab> <rich:tab label="Second"> Here is tab #2 <rich:inputNumberSlider value="20" /> </rich:tab> </rich:tabPanel> <h:commandButton action="submit" value="Submit" /> </h:form> #2. Navigate to the page. #3. Go to "Second" tab. #4. Set pointer to max(100) value. #5. Return to the "First" tab & click "Submit" button(see #1) #6. Navigate to "Second" tab again & verify position of slider's pointer. #8. Enter '80' in component's input & press 'Enter'. #9. Turn back to "First" tab & press "Submit". Actual behavior: #6: Pointer is at the right border of component's input. See attachment. #9: Pointer moves to left. Screenshot described #6 issue is attached. -- 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

13 years, 11 months

6
15
0 / 0

[JBoss JIRA] Created: (RF-5379) Calendar: 'getData' JS API method is not implemented ot does not work

by Andrei Markavtsov (JIRA)

Calendar: 'getData' JS API method is not implemented ot does not work --------------------------------------------------------------------- Key: RF-5379 URL: https://jira.jboss.org/jira/browse/RF-5379 Project: RichFaces Issue Type: Bug Affects Versions: 3.0.0 Environment: RF 3.0.0.SNAPSHOT Reporter: Andrei Markavtsov Assignee: Nick Belaevski The method was described in developer guide : p. 6.27.6. JavaScript API. Currently, $('calendarId').component.getData(date) method causes JS 'is not a function' error. -- 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

13 years, 11 months

5
9
0 / 0

[JBoss JIRA] Created: (RF-2968) Deprecate MethodBinding in favor to MethodExpression

by Nick Belaevski (JIRA)

Deprecate MethodBinding in favor to MethodExpression ---------------------------------------------------- Key: RF-2968 URL: http://jira.jboss.com/jira/browse/RF-2968 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.0 Reporter: Nick Belaevski Assigned To: Maksim Kaszynski Fix For: 3.2.1 Deprecate MethodBinding/ValueBinding properties in favor to MethodExpression/ValueExpression -- 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

13 years, 11 months

2
9
0 / 0

[JBoss JIRA] Created: (RF-7339) Cell grouping on RF Grid component

by Svetlana mukhina (JIRA)

Cell grouping on RF Grid component ------------------------------------ Key: RF-7339 URL: https://jira.jboss.org/jira/browse/RF-7339 Project: RichFaces Issue Type: Task Components: doc Affects Versions: 3.3.1 Reporter: Svetlana mukhina Assignee: Alexander Tsebro Fix For: 3.3.2.CR1 Describe a new feature in the dev guide -- 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

13 years, 11 months

4
6
0 / 0

[JBoss JIRA] Created: (RF-4275) Java docs language

by Svetlana mukhina (JIRA)

Java docs language ------------------- Key: RF-4275 URL: https://jira.jboss.org/jira/browse/RF-4275 Project: RichFaces Issue Type: Task Components: doc Affects Versions: 3.2.1 Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 3.2.2 Check English in Java Docs -- 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

13 years, 11 months

5
13
0 / 0

[JBoss JIRA] Created: (RF-8272) when in multi sort mode, provide an option to render numbers in each sorted column that indicates the current sort precedence of the columns

by Ian Springer (JIRA)

when in multi sort mode, provide an option to render numbers in each sorted column that indicates the current sort precedence of the columns -------------------------------------------------------------------------------------------------------------------------------------------- Key: RF-8272 URL: https://jira.jboss.org/jira/browse/RF-8272 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 3.3.2.SR1 Reporter: Ian Springer For example, if a table is currently multi-sorted by three columns - Name, Description, and Price, there is no quick way to know for each of these three columns, whether it is the primary, secondary, or tertiary sort column. A tiny "1", "2", and "3" next to the up or down arrow icon would clear this up nicely. For the RHQ project, we currently have a custom sorting facet which supports this feature. The facet is applied to a column as follows: <rich:column> <f:facet name="header"> <onc:sortableColumnHeader sort="res.resourceType.name"> <h:outputText styleClass="headerText" value="Type"/> </onc:sortableColumnHeader> </f:facet> <h:outputText value="#{resourceComposite.resource.resourceType.name}"/> </rich:column> I've attached a screenshot that shows how the column headers are rendered with the little numbers. I am creating this issue, because we would prefer using a built-in RichFaces feature, rather than a custom facet. -- 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

13 years, 11 months

4
7
0 / 0

[JBoss JIRA] Created: (RF-8270) provide a way to render a commandButton based on a minimum and/or maximum number of rows currently selected in a rich:*dataTable

by Ian Springer (JIRA)

provide a way to render a commandButton based on a minimum and/or maximum number of rows currently selected in a rich:*dataTable -------------------------------------------------------------------------------------------------------------------------------- Key: RF-8270 URL: https://jira.jboss.org/jira/browse/RF-8270 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 3.3.2.SR1 Reporter: Ian Springer This is useful when a particular action only makes sense when a certain number of rows are selected - here are a few examples: 1) most CRUD actions only make sense when at least one row is selected 2) a diff/compare action would only make sense when at least two rows were selected For RHQ, we currently have a custom component for this but would prefer use something that was built-in to RichFaces. Here's what the usage of our component (onc:selectCommandButton) looks like (not the low and high attributes, which reflect the minimum and maximum rows that must be selected: <f:facet name="footer"> <rich:columnGroup> <rich:column colspan="4" width="100%"> <onc:selectCommandButton action="#{ResourceGroupOperationScheduleUIBean.unschedule}" value="UNSCHEDULE" target="selectedItems" styleClass="on-pager-button buttonsmall" low="1" rendered="#{ResourceGroupUIBean.permissions.control}"/> <onc:selectCommandButton action="#{ResourceGroupOperationScheduleUIBean.executeNow}" value="EXECUTE NOW" target="selectedItems" styleClass="on-pager-button buttonsmall" low="1" high="1" rendered="#{ResourceGroupUIBean.permissions.control}"/> </rich:column> </rich:columnGroup> </f:facet> However, I think a nicer way to implement this would be to add a new optional attribute to the rich:*dataTable components, e.g.: <rich:extendedDataTable selectedRowCount="#{MyManagedBean.selectedRowCount}" ... /> The extendedDataTable component would update this attribute any time the selection is changed by the GUI user. Then a standard commandButton could be used as follows: <h:commandButton value="MyAction" rendered="#{MyManagedBean.selectedRowCount eq 1}" .../> An alternative to a new 'selectedRowCount' attribute would be using the existing 'selection' attribute and adding a new getSelectedRowCount() method to the org.richfaces.model.selection.Selection interface that the 'selection' attribute updates. An example of what this option would look like: <rich:extendedDataTable selection="#{MyManagedBean.selection}" ... /> <h:commandButton value="MyAction" rendered="#{MyManagedBean.selection.selectedRowCount eq 1}" .../> -- 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

13 years, 11 months

4
6
0 / 0

[JBoss JIRA] Created: (RF-8181) provide footer facets in all components which have header facets

by nimo stephan (JIRA)

provide footer facets in all components which have header facets ---------------------------------------------------------------- Key: RF-8181 URL: https://jira.jboss.org/jira/browse/RF-8181 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: nimo stephan Would be nice to provide facet:footers for ALL components which has a facet:header. For consistency, all components which have header-facets should also have footer-facets. For example, rich:modalPanel, rich:panel, 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

13 years, 11 months

4
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues January 2010