July 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13111) Data Iteration components evaluate value on postback even if not rendered when partial state saving is turned off

by Andrey Zhemoytuk (JIRA)

[ https://issues.jboss.org/browse/RF-13111?page=com.atlassian.jira.plugin.s... ] Andrey Zhemoytuk updated RF-13111: ---------------------------------- Fix Version/s: (was: 4.3.0.M3) > Data Iteration components evaluate value on postback even if not rendered when partial state saving is turned off > ----------------------------------------------------------------------------------------------------------------- > > Key: RF-13111 > URL: https://issues.jboss.org/browse/RF-13111 > 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: Andrey Zhemoytuk > Assignee: Brian Leathem > Labels: lazy-loaded > 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13111) Data Iteration components evaluate value on postback even if not rendered when partial state saving is turned off

by Andrey Zhemoytuk (JIRA)

[ https://issues.jboss.org/browse/RF-13111?page=com.atlassian.jira.plugin.s... ] Andrey Zhemoytuk updated RF-13111: ---------------------------------- Affects Version/s: 4.3.3 (was: 4.0.0.Final) (was: 4.1.0.Milestone2) > Data Iteration components evaluate value on postback even if not rendered when partial state saving is turned off > ----------------------------------------------------------------------------------------------------------------- > > Key: RF-13111 > URL: https://issues.jboss.org/browse/RF-13111 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.3 > Environment: Fedora 15, Glassfish 3.1.1, CDI (Weld) > Reporter: Andrey Zhemoytuk > Assignee: Brian Leathem > Labels: lazy-loaded > 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13111) Data Iteration components evaluate value on postback even if not rendered when partial state saving is turned off

by Andrey Zhemoytuk (JIRA)

[ https://issues.jboss.org/browse/RF-13111?page=com.atlassian.jira.plugin.s... ] Andrey Zhemoytuk updated RF-13111: ---------------------------------- Labels: partial_state_saving (was: lazy-loaded) > Data Iteration components evaluate value on postback even if not rendered when partial state saving is turned off > ----------------------------------------------------------------------------------------------------------------- > > Key: RF-13111 > URL: https://issues.jboss.org/browse/RF-13111 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.3 > Environment: Fedora 15, Glassfish 3.1.1, CDI (Weld) > Reporter: Andrey Zhemoytuk > Assignee: Brian Leathem > Labels: partial_state_saving > 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13111) Data Iteration components evaluate value on postback even if not rendered when partial state saving is turned off

by Andrey Zhemoytuk (JIRA)

[ https://issues.jboss.org/browse/RF-13111?page=com.atlassian.jira.plugin.s... ] Andrey Zhemoytuk updated RF-13111: ---------------------------------- Environment: (was: Fedora 15, Glassfish 3.1.1, CDI (Weld)) > Data Iteration components evaluate value on postback even if not rendered when partial state saving is turned off > ----------------------------------------------------------------------------------------------------------------- > > Key: RF-13111 > URL: https://issues.jboss.org/browse/RF-13111 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.3 > Reporter: Andrey Zhemoytuk > Assignee: Brian Leathem > Labels: partial_state_saving > 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13111) Data Iteration components evaluate value on postback even if not rendered when partial state saving is turned off

by Andrey Zhemoytuk (JIRA)

Andrey Zhemoytuk created RF-13111: ------------------------------------- Summary: Data Iteration components evaluate value on postback even if not rendered when partial state saving is turned off Key: RF-13111 URL: https://issues.jboss.org/browse/RF-13111 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: Andrey Zhemoytuk Assignee: Brian Leathem Fix For: 4.3.0.M3 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-11382: ------------------------------------ [~a.zhemoytuk] can you file a new issue for the partial state saving = false use case? > 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13018) a4j:commandButton wrong actions performed

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13018?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13018: ------------------------------------ The issue has a fairly simple workaround, so we won't set it to _Blocker_. We will consider backporting the fix to RichFaces 4.x if it is reasonable to do so. > a4j:commandButton wrong actions performed > ----------------------------------------- > > Key: RF-13018 > URL: https://issues.jboss.org/browse/RF-13018 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.3.Final, 4.3.2 > Environment: Server: Fedora 17, Jboss AS 7.1.1.Final, Jboss EAP 6.1.0.Beta, Java 1.7.0_15 > Browsers: Chrome 26 and Chrome 27 on (Linux & Windows 7), Firefox 20.0 (Linux & Windows 7), IE 9 > Reporter: Rob Hare > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Attachments: RF-13018.zip > > > When an a4j commponent (a4j:commandButton, a4j:jsFunction) is activated, actions of other a4j:commandButtons on the page with type=button will be fired. > For example, pressing either button in the following code will cause both richBean.function1() and richBean.function2() actions. > {noformat} > <h:form id="testForm"> > <a4j:commandButton id="button1" type="button" value="Button 1" > action="#{richBean.function1}" /> > <a4j:commandButton id="button2" type="button" value="Button 2" > action="#{richBean.function2}" /> > </h:form> > {noformat} > Note, if one of the a4j:commandButton is marked immediate, then only one action (possibly the wrong action) will be performed and block others. For instance if an a4j:jsFunction action was being triggered, the a4j:commandButton action may occur making appear that the a4j:jsFunction failed. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13099) Disabled input text is not visible

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13099?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13099: ------------------------------------ Workaround suggested via forum reference. > Disabled input text is not visible > ---------------------------------- > > Key: RF-13099 > URL: https://issues.jboss.org/browse/RF-13099 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Kush Kumar > Priority: Minor > Labels: waiting_on_user > > Disabled input text is not visible -can you please help me out how can we make it visible or can we change the color of disabled text? -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13081) Facets "disabled" not working for dataScroller

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13081?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13081: ------------------------------- Fix Version/s: 5-Tracking > Facets "disabled" not working for dataScroller > ---------------------------------------------- > > Key: RF-13081 > URL: https://issues.jboss.org/browse/RF-13081 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.1 > Reporter: Laurent Grangier > Assignee: Pavol Pitonak > Priority: Critical > Fix For: 5-Tracking > > > All the facets which end with "disabled" (like "first_disabled", "previous_disabled", etc.) are not working for the component "rich:dataScroller". > According to the [documentation|http://docs.jboss.org/richfaces/latest_4_3_X/Component_Refe...], they should be available. > Example: > {code} > <f:facet name="first_disabled"> > <h:graphicImage value="my-image.png" /> > </f:facet> > {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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13099) Disabled input text is not visible

by SBS JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/RF-13099?page=com.atlassian.jira.plugin.s... ] SBS JIRA Integration updated RF-13099: -------------------------------------- Forum Reference: https://community.jboss.org/message/828743#828743, https://community.jboss.org/thread/230629 (was: https://community.jboss.org/thread/230629) > Disabled input text is not visible > ---------------------------------- > > Key: RF-13099 > URL: https://issues.jboss.org/browse/RF-13099 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Kush Kumar > Priority: Minor > Labels: waiting_on_user > > Disabled input text is not visible -can you please help me out how can we make it visible or can we change the color of disabled text? -- 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

10 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues July 2013