[JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on RF-11382:
----------------------------------------------
Rodney Russ <rruss(a)redhat.com> changed the Status of [bug 916314|https://bugzilla.redhat.com/show_bug.cgi?id=916314] from NEW to ON_QA
> Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
> -------------------------------------------------------------------------------
>
> Key: RF-11382
> URL: https://issues.jboss.org/browse/RF-11382
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.0.0.Final, 4.1.0.Milestone2
> Environment: Fedora 15, Glassfish 3.1.1, CDI (Weld)
> Reporter: Frederick Kämpfer
> Assignee: Brian Leathem
> Labels: lazy-loaded
> Fix For: 4.3.0.M3
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> In Richfaces 4 both datatable and extendedDatatable evaluate the value attribute even when rendered is set to false, even though it is not necessary. This makes it hard to achieve performance by trimming parts of the view tree. The built-in h:dataTable behaves correctly in that case.
> To reproduce simply try this snipplet:
> {code:xml}
> <h:form>
> <rich:dataTable value="#{myBean.property}" rendered="false">
> </rich:dataTable>
> </h:form>
> {code}
> Side note: The reason I'm posting this is, that i want to embed a rich:dataTable in a ajax loaded rich:togglePanelItem which is loaded on demand. Probably fixing the "render" problem will also make the dataTable lazy-loadable when switching to the corresponding togglePanelItem.
> I hope this is no duplicate, I only found RichFaces 3 issues mentioning this problem.
--
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
11 years, 10 months
[JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration updated RF-11382:
-----------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=916314
> Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
> -------------------------------------------------------------------------------
>
> Key: RF-11382
> URL: https://issues.jboss.org/browse/RF-11382
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.0.0.Final, 4.1.0.Milestone2
> Environment: Fedora 15, Glassfish 3.1.1, CDI (Weld)
> Reporter: Frederick Kämpfer
> Assignee: Brian Leathem
> Labels: lazy-loaded
> Fix For: 4.3.0.M3
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> In Richfaces 4 both datatable and extendedDatatable evaluate the value attribute even when rendered is set to false, even though it is not necessary. This makes it hard to achieve performance by trimming parts of the view tree. The built-in h:dataTable behaves correctly in that case.
> To reproduce simply try this snipplet:
> {code:xml}
> <h:form>
> <rich:dataTable value="#{myBean.property}" rendered="false">
> </rich:dataTable>
> </h:form>
> {code}
> Side note: The reason I'm posting this is, that i want to embed a rich:dataTable in a ajax loaded rich:togglePanelItem which is loaded on demand. Probably fixing the "render" problem will also make the dataTable lazy-loadable when switching to the corresponding togglePanelItem.
> I hope this is no duplicate, I only found RichFaces 3 issues mentioning this problem.
--
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
11 years, 10 months
[JBoss JIRA] (RF-12765) Rich:tabPanel not possible to switch tabs when only dynamic tabs are present
by Tali Han (JIRA)
[ https://issues.jboss.org/browse/RF-12765?page=com.atlassian.jira.plugin.s... ]
Tali Han commented on RF-12765:
-------------------------------
I can, but I need your e-mail.Please let me know your e-mail and what exactly you want to see in this tar.
I guess I am little bit confused what you trying to achieve?
I can deploy this war on our test server, so you'll be able to click and reproduce this bug? Will it work?
Or you want to learn something about our setup?
It is just apache-tomcat6, and your war in a webapp's directory.Nothing special.
> Rich:tabPanel not possible to switch tabs when only dynamic tabs are present
> ----------------------------------------------------------------------------
>
> Key: RF-12765
> URL: https://issues.jboss.org/browse/RF-12765
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.0.M3, 4.3.0.CR2
> Environment: Linux, windows any browser Chrom, Mozilla
> Reporter: Tali Han
> Assignee: Lukáš Fryč
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Rih:Tab panel functionality is broken.
> If you have dynamically generated tabs, you'll be able to switch from first to last, and then to first, but you'll not be able to switch to any other tab again.
> Remove from example that comes with richfaces distribution first static tab for dynamic tabs and you'll be able to reproduce this behaviour.
> richfaces/tabPanel/samples/dynamic-sample.xhtml
> {code}
> <rich:tabPanel activeItem="#{dynamicPanelBean.activeTab}">
> <ui:remove>
> <rich:tab header="Static">
> <p>This tab is static one.</p>
>
> <p>All of the following tabs are dynamically generated using <b>a4j:repeat</b>.</p>
> </rich:tab>
> </ui:remove>
> <a4j:repeat value="#{skinBean.skins}" var="skinName">
>
> <rich:tab header="#{skinName}" name="#{skinName}">
> <f:facet name="header">#{skinName}</f:facet>
> <i> All the controls below are just standard JSF components skinned with RichFaces: </i>
> <hr />
> <h:form>
> {code}
--
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
11 years, 10 months
[JBoss JIRA] (RF-6446) dataScroller: facet "controlSeparator" doesn't work
by David Kocher (JIRA)
[ https://issues.jboss.org/browse/RF-6446?page=com.atlassian.jira.plugin.sy... ]
David Kocher commented on RF-6446:
----------------------------------
The controlsSeparator facet does not work in Richfaces 4.3.0.Final.
> dataScroller: facet "controlSeparator" doesn't work
> ---------------------------------------------------
>
> Key: RF-6446
> URL: https://issues.jboss.org/browse/RF-6446
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: doc
> Affects Versions: 3.3.0
> Environment: FF-3, IE6, IE7, Opera, Safari
> Tomcat 6.0
> sun RI 1.2.10
> jsp
> Reporter: Inna Shchibrya
> Assignee: Nick Belaevski
> Fix For: 3.3.1
>
>
> For example:
> <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%>
> <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f"%>
> <%@ taglib uri="http://richfaces.org/a4j" prefix="a4j"%>
> <%@ taglib uri="http://richfaces.org/rich" prefix="rich"%>
> <f:subview id="DataScrollerSubviewID">
> <rich:dataTable id="dataTableId" value="#{dataScroller.dataTable}"
> var="dT" cellpadding="5px" rows="5" border="1" reRender="dsID,dataTableId" sortMode="#{dataScroller.sortMode}">
> <f:facet name="header">
> <rich:datascroller for="dataTableId" ajaxSingle="#{dataScroller.ajaxSingle}" reRender="dataTableId"
> boundaryControls="#{dataScroller.boundaryControls}"
> binding="#{dataScroller.htmlDatascroller}" data="datascrData" fastStep="#{dataScroller.fastStep}" id="dsID"
> page="#{dataScroller.page}" pagesVar="pages" pageIndexVar="index"
> value="#{dataScroller.value}" status="a4jStatusID" stepControls="#{dataScroller.stepControls}"
> eventsQueue="eventsQueue" inactiveStyle="#{style.inactiveStyle}" inactiveStyleClass="#{style.inactiveStyleClass}" selectedStyle="#{style.selectedStyle}" selectedStyleClass="#{style.selectedStyleClass}" style="#{style.style}" styleClass="#{style.styleClass}" tableStyle="#{style.tableStyle}" tableStyleClass="#{style.tableStyleClass}"
> fastControls="#{dataScroller.fastControls}" action="#{dataScroller.act}" actionListener="#{dataScroller.actListener}"
> align="center" rendered="#{dataScroller.render}"
> limitToList="#{dataScroller.limitToList}"
> renderIfSinglePage="#{dataScroller.renderIfSinglePage}"
> maxPages="#{dataScroller.maxPages}"
> scrollerListener="#{dataScroller.ScrollerListener}"
> onclick="#{event.onclick}" oncomplete="#{event.oncomplete}"
> ondblclick="#{event.ondblclick}" onkeydown="#{event.onkeydown}"
> onkeypress="#{event.onkeypress}" onkeyup="#{event.onkeyup}"
> onmousedown="#{event.onmousedown}"
> onmousemove="#{event.onmousemove}" onmouseout="#{event.onmouseout}"
> onmouseover="#{event.onmouseover}" onmouseup="#{event.onmouseup}">
> <f:facet name="controlSeparator">
> <h:graphicImage value="/image/sep.png"/>
> </f:facet>
> </rich:datascroller>
> </f:facet>
> <f:facet name="footer">
> </f:facet>
> <rich:column sortBy="#{dT.str0}" filterBy="#{dT.str0}" filterEvent="onkeyup"
> selfSorted="#{dataScroller.selfSorted}" filterValue="#{dataScroller.filterValue}">
> <h:outputText value="#{dT.str0}" />
> </rich:column>
> <rich:column sortBy="#{dT.int0}" filterBy="#{dT.int0}" filterEvent="onkeyup" selfSorted="#{dataScroller.selfSorted}">
> <h:outputText value="#{dT.int0} " />
> </rich:column>
> </rich:dataTable>
> <h:panelGrid id="dataScrollerActionID" columns="1">
> <a4j:commandButton value="Show action" reRender="dataScrollerActionID" style=" width : 95px;"></a4j:commandButton>
> <h:outputText value="#{dataScroller.action}" />
> <h:outputText value="#{dataScroller.actionListener}" />
> </h:panelGrid>
> </f:subview>
> Open the page in the browser --> Separators between controls didn't appear.
> Expected result: Separators between controls should appear.
--
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
11 years, 10 months
[JBoss JIRA] (RF-12765) Rich:tabPanel not possible to switch tabs when only dynamic tabs are present
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12765?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-12765:
---------------------------------
[~talik], could you please upload it to Dropbox or any other file hosting?
I will share my setup with you once I will get it commited (~tomorrow).
> Rich:tabPanel not possible to switch tabs when only dynamic tabs are present
> ----------------------------------------------------------------------------
>
> Key: RF-12765
> URL: https://issues.jboss.org/browse/RF-12765
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.0.M3, 4.3.0.CR2
> Environment: Linux, windows any browser Chrom, Mozilla
> Reporter: Tali Han
> Assignee: Lukáš Fryč
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Rih:Tab panel functionality is broken.
> If you have dynamically generated tabs, you'll be able to switch from first to last, and then to first, but you'll not be able to switch to any other tab again.
> Remove from example that comes with richfaces distribution first static tab for dynamic tabs and you'll be able to reproduce this behaviour.
> richfaces/tabPanel/samples/dynamic-sample.xhtml
> {code}
> <rich:tabPanel activeItem="#{dynamicPanelBean.activeTab}">
> <ui:remove>
> <rich:tab header="Static">
> <p>This tab is static one.</p>
>
> <p>All of the following tabs are dynamically generated using <b>a4j:repeat</b>.</p>
> </rich:tab>
> </ui:remove>
> <a4j:repeat value="#{skinBean.skins}" var="skinName">
>
> <rich:tab header="#{skinName}" name="#{skinName}">
> <f:facet name="header">#{skinName}</f:facet>
> <i> All the controls below are just standard JSF components skinned with RichFaces: </i>
> <hr />
> <h:form>
> {code}
--
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
11 years, 10 months