[JBoss JIRA] (RF-12684) The last page shows rows from the page before if rich:collapsibleSubTable is included in rich:dataTable with rich:dataScroller.
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/RF-12684?page=com.atlassian.jira.plugin.s... ]
Ilia Vassilev updated RF-12684:
-------------------------------
Steps to Reproduce:
1. Hit the attached page dataScroller_RF-12684.xhtml. The table has 7 records displayed in 3 pages (rows="3") page1.png
2. Go to the last page. Records 2 and 3 are also displayed which is incorrect. page2.png
was:
1. Hit the attached page dataScroller_RF-12639.xhtml. The table has 7 records displayed in 3 pages (rows="3") page1.png
2. Go to the last page. Records 2 and 3 are also displayed which is incorrect. page2.png
> The last page shows rows from the page before if rich:collapsibleSubTable is included in rich:dataTable with rich:dataScroller.
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: RF-12684
> URL: https://issues.jboss.org/browse/RF-12684
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.2.3.Final
> Reporter: Ilia Vassilev
>
> The last page shows rows from the page before if rich:collapsibleSubTable is included in rich:dataTable with rich:dataScroller.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (RF-12684) The last page shows rows from the page before if rich:collapsibleSubTable is included in rich:dataTable with rich:dataScroller.
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/RF-12684?page=com.atlassian.jira.plugin.s... ]
Ilia Vassilev updated RF-12684:
-------------------------------
Description: The last page shows rows from the page before if rich:collapsibleSubTable is included in rich:dataTable with rich:dataScroller. (was: The last page shows rows from the page before if rich:collapsibleSubTable is included in rich:dataTable with rich:dataScroller.)
Steps to Reproduce:
1. Hit the attached page dataScroller_RF-12639.xhtml. The table has 7 records displayed in 3 pages (rows="3") page1.png
2. Go to the last page. Records 2 and 3 are also displayed which is incorrect. page2.png
Workaround Description: 1. Use rich:extendedDataTable instead of rich:dataTable
> The last page shows rows from the page before if rich:collapsibleSubTable is included in rich:dataTable with rich:dataScroller.
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: RF-12684
> URL: https://issues.jboss.org/browse/RF-12684
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.2.3.Final
> Reporter: Ilia Vassilev
>
> The last page shows rows from the page before if rich:collapsibleSubTable is included in rich:dataTable with rich:dataScroller.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (RF-12682) extendedDataTable render issue with rich:tabPanel (4.2.3)
by SBS JIRA Integration (JIRA)
[ https://issues.jboss.org/browse/RF-12682?page=com.atlassian.jira.plugin.s... ]
SBS JIRA Integration updated RF-12682:
--------------------------------------
Forum Reference: https://community.jboss.org/message/783522#783522
> extendedDataTable render issue with rich:tabPanel (4.2.3)
> ---------------------------------------------------------
>
> Key: RF-12682
> URL: https://issues.jboss.org/browse/RF-12682
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-tables
> Reporter: Kaveh A.
> Labels: richfaces
> Fix For: 4.2.3.Final
>
>
> This issue is not just specific to tabPanel. Anytime the extendedDataTable is hidden (when the page loads) and then it is made visible later the table can not display the data (table is empty at the load time).
> In this particular case if we load a page with two tabs. Furthermore if we have one extendedDataTable in each tab (the first tab shows and the second tab is not shown at first). In this case once the user clicks on the second tab and tries to populate the extendedDataTable (via any action). Then the table is not rendered properly. A sample project has been provided at the following link that further describe this issue. You can download the eclipse project attached at the end of the following message to reproduce this issue.
> https://community.jboss.org/message/783787
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (RF-12683) Provide a configuration option to disable built-in sorting/filtering
by Brian Leathem (JIRA)
Brian Leathem created RF-12683:
----------------------------------
Summary: Provide a configuration option to disable built-in sorting/filtering
Key: RF-12683
URL: https://issues.jboss.org/browse/RF-12683
Project: RichFaces
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: component-tables
Affects Versions: 4.3.0.M3
Reporter: Brian Leathem
Fix For: 4.3.0.CR1
The built-in sorting/filtering feature introduced in 4.3.0.M3 requires developer who are already using the EDT sorting/filtering functionality to introduce the _sortType=custom_ and _filterType=custom_ attributes to prevent a "doulbing up" of the sort and filter controls.
To make it easier for people to migrate from RichFaces 4.2 to 4.3, we should provide a central configuration option (ie. a web.xml context-param) to disable built-in sorting/filtering, so developers can introduce the new attributes to their facelets at their leisure.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (RF-12670) JSF 2.0 compatibility issue, NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12670?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-12670:
------------------------------------
CDI interoperability should not break when you bundle a JSF implementation. If it does, that's a app server bug IMO. In the JBoss AS issue you linked (AS7-1628) it sounds likes it's more of a problem with a change from Mojarra -> MyFaces then a version change.
I do agree with your point that JSF 2.1 is not part of the Java EE 6 umbrella specification, however Java EE 6 compatibility was the target for JSF 2.1, so one is expected to use JSF 2.1 in a Java EE 6 stack trouble-free.
This all being said, it looks like we have a workaround here, whereby we can keep the desired functionality, while maintaining compatibility with JSF 2.0. Instead of using the VisitHint.SKIP_ITERATION enum, we can look for the [javax.faces.visit.SKIP_ITERATION attribute|https://github.com/jboss/mojarra/blob/2.1.7-jbossorg-2/jsf-ri/s...] in the FacesContext.
I'll re-open this issue with that fix in mind.
> JSF 2.0 compatibility issue, NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION
> ---------------------------------------------------------------------------------------------------
>
> Key: RF-12670
> URL: https://issues.jboss.org/browse/RF-12670
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.0.M3
> Reporter: Dupont Dupont
> Assignee: Brian Leathem
>
> When using RF 4.3.0-SNAPSHOT with a JSF 2.0 implementation (i.e. Websphere 8), I get a
> {code}
> java.lang.NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION
> at org.richfaces.component.UIDataAdaptor.requiresRowIteration(UIDataAdaptor.java:1387)
> at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1304)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:793)
> at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007)
> at javax.faces.component.UIForm.visitTree(UIForm.java:269)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:793)
> at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:793)
> at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007)
> at org.apache.myfaces.lifecycle.DefaultRestoreViewSupport.processComponentBinding(DefaultRestoreViewSupport.java:90)
> at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:142)
> at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:171)
> at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
> at
> {code}
> RF 4.3.0-SNAPSHOT is using an API introduced with JSF 2.1 in UIDataAdaptor.
> See https://github.com/richfaces/components/commit/d65e614ef03adf87c0b6df2288...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (RF-12670) JSF 2.0 compatibility issue, NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12670?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reopened RF-12670:
--------------------------------
> JSF 2.0 compatibility issue, NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION
> ---------------------------------------------------------------------------------------------------
>
> Key: RF-12670
> URL: https://issues.jboss.org/browse/RF-12670
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.0.M3
> Reporter: Dupont Dupont
> Assignee: Brian Leathem
>
> When using RF 4.3.0-SNAPSHOT with a JSF 2.0 implementation (i.e. Websphere 8), I get a
> {code}
> java.lang.NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION
> at org.richfaces.component.UIDataAdaptor.requiresRowIteration(UIDataAdaptor.java:1387)
> at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1304)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:793)
> at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007)
> at javax.faces.component.UIForm.visitTree(UIForm.java:269)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:793)
> at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:793)
> at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007)
> at org.apache.myfaces.lifecycle.DefaultRestoreViewSupport.processComponentBinding(DefaultRestoreViewSupport.java:90)
> at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:142)
> at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:171)
> at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
> at
> {code}
> RF 4.3.0-SNAPSHOT is using an API introduced with JSF 2.1 in UIDataAdaptor.
> See https://github.com/richfaces/components/commit/d65e614ef03adf87c0b6df2288...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (RF-12670) JSF 2.0 compatibility issue, NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12670?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12670:
-------------------------------
Fix Version/s: 4.3.0.CR1
> JSF 2.0 compatibility issue, NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION
> ---------------------------------------------------------------------------------------------------
>
> Key: RF-12670
> URL: https://issues.jboss.org/browse/RF-12670
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.0.M3
> Reporter: Dupont Dupont
> Assignee: Brian Leathem
> Fix For: 4.3.0.CR1
>
>
> When using RF 4.3.0-SNAPSHOT with a JSF 2.0 implementation (i.e. Websphere 8), I get a
> {code}
> java.lang.NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION
> at org.richfaces.component.UIDataAdaptor.requiresRowIteration(UIDataAdaptor.java:1387)
> at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1304)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:793)
> at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007)
> at javax.faces.component.UIForm.visitTree(UIForm.java:269)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:793)
> at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:793)
> at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007)
> at org.apache.myfaces.lifecycle.DefaultRestoreViewSupport.processComponentBinding(DefaultRestoreViewSupport.java:90)
> at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:142)
> at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:171)
> at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
> at
> {code}
> RF 4.3.0-SNAPSHOT is using an API introduced with JSF 2.1 in UIDataAdaptor.
> See https://github.com/richfaces/components/commit/d65e614ef03adf87c0b6df2288...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (RF-7524) rich:columns throws Exception when value is null
by Tom Caflisch (JIRA)
[ https://issues.jboss.org/browse/RF-7524?page=com.atlassian.jira.plugin.sy... ]
Tom Caflisch commented on RF-7524:
----------------------------------
As a workaround you can just use a ternary operator to check for null like this:
<rich:columns value="#{myBacker.columns == null ? '' : myBacker.columns}"
> rich:columns throws Exception when value is null
> ------------------------------------------------
>
> Key: RF-7524
> URL: https://issues.jboss.org/browse/RF-7524
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 3.3.1, 3.3.2.SR1
> Environment: Windows Vista, Java 6, JBoss 4.2.2.GA, JBoss Seam 2.1.1.GA
> Reporter: Markus Merder
> Priority: Minor
> Fix For: 3.Future
>
>
> Since Richfaces Version 3.3.1.GA an exception is thrown, when value of rich:columns is null.
> For example:
> <rich:columns value="#{someList[0].years}" var="year" index="index" rendered="#{not empty someList[0].years}">...</rich:columns>
> throws:
> javax.servlet.jsp.JspTagException: FOREACH_BAD_ITEMS
> at org.richfaces.iterator.SimpleForEachIterator.toForEachIterator(SimpleForEachIterator.java:135)
> at org.richfaces.iterator.SimpleForEachIterator.supportedTypeForEachIterator(SimpleForEachIterator.java:98)
> at org.richfaces.taglib.ColumnsHandler.prepare(ColumnsHandler.java:304)
> at org.richfaces.taglib.ColumnsHandler.apply(ColumnsHandler.java:489)
> at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
> ....
> because supportedTypeForEachIterator(Object o) in SimpleForEachIterator is called with null.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months