[JBoss JIRA] Created: (RF-10842) dataScroller: renderIfSinglePage=false breaks component
by Ilya Shaikovsky (JIRA)
dataScroller: renderIfSinglePage=false breaks component
-------------------------------------------------------
Key: RF-10842
URL: https://issues.jboss.org/browse/RF-10842
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-tables
Affects Versions: 4.0.0.Final
Reporter: Ilya Shaikovsky
just added
<f:facet name="footer">
<rich:dataScroller renderIfSinglePage="false"></rich:dataScroller>
</f:facet>
to /richfaces-showcase/src/main/webapp/richfaces/dataTable/samples/tableFiltering-sample.xhtml
And scroller is never shown.
Should be:
1) shown initially as there are at least three pages
2) not shown after filtering if there are single page
3) rendered back if reseting filter.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (RF-10740) collapsibleSubTableToggler with expandMode="ajax" executes collapsibleSubTable on server
by Martin Kočí (JIRA)
collapsibleSubTableToggler with expandMode="ajax" executes collapsibleSubTable on server
----------------------------------------------------------------------------------------
Key: RF-10740
URL: https://issues.jboss.org/browse/RF-10740
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-tables
Affects Versions: 4.0.0.CR1
Environment: richfaces 4.0, mojarra 2.0.4
Reporter: Martin Kočí
With example below request contains javax.faces.partial.execute=form:dataTable:0:collapsibleSubTable
and that triggers validation on inputText.
<r:dataTable id="dataTable" value="#{bean.rowValues}" >
<r:column>
<r:collapsibleSubTableToggler for="collapsibleSubTable" />
</r:column>
<r:collapsibleSubTable id="collapsibleSubTable" expandMode="ajax">
<f:facet name="header">
<h:inputText id="inputText" required="true" />
</f:facet>
</r:collapsibleSubTable>
</r:dataTable>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (RF-4192) Add "noDataLabel" to rich:dataTable for purposes of display a message if the dataTable is empty
by Chris Simons (JIRA)
Add "noDataLabel" to rich:dataTable for purposes of display a message if the dataTable is empty
-----------------------------------------------------------------------------------------------
Key: RF-4192
URL: https://jira.jboss.org/jira/browse/RF-4192
Project: RichFaces
Issue Type: Feature Request
Affects Versions: 3.2.1, 3.2.0.SR1, 3.2.0, 3.1.6, 3.1.5, 3.1.4
Reporter: Chris Simons
Priority: Optional
An excellent, small addition to rich:dataTable would allow for a textual message to be displayed in the event that a dataTable is empty.
For example:
<rich:dataTable id="myTable" noDataLabel="#{messages['dataTable.noData']}" ....> </rich:dataTable>
When the condition is true that the underlying data model or list is empty, the message would display in one row that spans the entire dataTable. The headers and dataTable title would still remain.
Please vote for this issue if you would like to see this feature added.
--
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, 5 months
[JBoss JIRA] Created: (RF-10439) Introduce SelectionChange API
by Martin Kočí (JIRA)
Introduce SelectionChange API
-----------------------------
Key: RF-10439
URL: https://issues.jboss.org/browse/RF-10439
Project: RichFaces
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: component-tables
Affects Versions: 4.0.0.Milestone5
Environment: RichFaces 4.0 trunk svn rev 21496
Reporter: Martin Kočí
Priority: Optional
Fix For: 4.Future
I don't know if it is intended or not but current RF 4.0 don't have listener/event for API for "SelectionChange" behaviour. Suggestions:
1. introduce SelectionChangeEvent, SelectionChangeListener, SelectionChangeSource API - there is TreeSelectionChangeEvent already - I think the new SelectionChangeEvent can be base class for TreeSelectionChangeEvent
2. add methods addSelectionChangeListener, removeSelectionChangeListener, setSelectionListener(MethodExpression) etc. at UIExtendedDataTable
3. rename client event name from "selectionchange" to "selectionChange" - ValueChange has that convention
4. RC showcase contains selection handling based on AjaxBehaviourEvent -> modify it for r:extendedDataTable selectionChangeListener="#{}" usage
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months