[JBoss JIRA] Created: (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
5:26 a.m.
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
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:21 p.m.
New subject: [JBoss JIRA] Updated: (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
[
https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-11382:
-------------------------------
Fix Version/s: 4.1.0.Tracking
(was: 4.2.0.Tracking)
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
Fix For: 4.1.0.Tracking
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:21 p.m.
New subject: [JBoss JIRA] Updated: (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
[
https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-11382:
-------------------------------
Fix Version/s: 4.2.0.Tracking
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
Fix For: 4.1.0.Tracking
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:42 p.m.
New subject: [JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
[
https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-11382:
-------------------------------
Fix Version/s: 4.2.0.Tracking
(was: 4.1.0.Tracking)
Assignee: Zuzka Krejčová
Have you tried wrapping the dtatable in a panelgrid, and seeing if that is an acceptible
workaround?
Scheduling for review, to see if this value evaluation can be prevented.
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: Zuzka Krejčová
Fix For: 4.2.0.Tracking
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:13 a.m.
New subject: [JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
[
https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s...
]
Frederick Kämpfer commented on RF-11382:
----------------------------------------
Wrapping it in a h:panelGrid/panelGroup (with rendered=false) does not make a difference,
the value attribute is still evaluated. However, if you set the parent form's render
attribute to false it seems to work. However that's not always feasible.
My workaround currently is to return an empty collection, if the table's parent
togglePanel is not rendered.
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: Zuzka Krejčová
Fix For: 4.2.0.Tracking
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:20 a.m.
New subject: [JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
[
https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s...
]
Zuzka Krejčová commented on RF-11382:
-------------------------------------
I don't understand why you assigned it to me - I'm not RF QE and really don't
have anything in common with RichFaces as far as I know. Thanks for the trust, but better
to give it to someone on the project perhaps?
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: Zuzka Krejčová
Fix For: 4.2.0.Tracking
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:56 a.m.
New subject: [JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
[
https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s...
]
Pavol Pitonak reassigned RF-11382:
----------------------------------
Assignee: Jan Papousek (was: Zuzka Krejčová)
Jan, please verify.
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: Jan Papousek
Fix For: 4.2.0.Tracking
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:21 a.m.
New subject: [JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
[
https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s...
]
Jan Papousek commented on RF-11382:
-----------------------------------
I've tried it in Metamer with with session bean annotated as a ViewScoped.
The getter method:
{code}
public Collection<Object> getEmptyModel() {
setEmptyModelCalled(true);
logger.info("empty model called");
return new ArrayList<Object>();
}
{code}
The page:
{code}
<h:form>
<rich:dataTable id="richDataTable"
value="#{richDataTableBean.emptyModel}" rendered="false" />
</h:form>
<br />
CALLED: <h:outputText id="outputCalled"
value="#{richDataTableBean.emptyModelCalled}" />
{code}
After opening the page, the page shows "CALLED: false", but the message
"empty model called" is logged. So the getter is called, but the variable where
I store the information about calling the getter is reset somehow.
When I use h:dataTable instead of rich:dataTable, the page shows "CALLED: false"
and the message is not logged (getter is not called).
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: Jan Papousek
Fix For: 4.2.0.Tracking
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:21 a.m.
New subject: [JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
[
https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s...
]
Jan Papousek reassigned RF-11382:
---------------------------------
Assignee: Brian Leathem (was: Jan Papousek)
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
Fix For: 4.2.0.Tracking
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:33 a.m.
New subject: [JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
[
https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s...
]
Frederick Kämpfer commented on RF-11382:
----------------------------------------
FYI here is the stack trace of the getter call with 4.1.0-SNAPSHOT. Maybe it helps.
{code}
<< CALL OF GETTER >>
Information: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Information: at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
Information: at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
Information: at java.lang.reflect.Method.invoke(Method.java:601)
Information: at javax.el.BeanELResolver.getValue(BeanELResolver.java:302)
Information: at
com.sun.faces.el.DemuxCompositeELResolver._getValue(DemuxCompositeELResolver.java:176)
Information: at
com.sun.faces.el.DemuxCompositeELResolver.getValue(DemuxCompositeELResolver.java:203)
Information: at com.sun.el.parser.AstValue.getValue(AstValue.java:116)
Information: at com.sun.el.parser.AstValue.getValue(AstValue.java:163)
Information: at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:219)
Information: at
org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:55)
Information: at
com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:109)
Information: at
javax.faces.component.ComponentStateHelper.eval(ComponentStateHelper.java:194)
Information: at
javax.faces.component.ComponentStateHelper.eval(ComponentStateHelper.java:182)
Information: at org.richfaces.component.UISequence.getValue(UISequence.java:178)
Information: at
org.richfaces.component.UISequence.createExtendedDataModel(UISequence.java:112)
Information: at
org.richfaces.component.UIDataTableBase.createExtendedDataModel(UIDataTableBase.java:195)
Information: at
org.richfaces.component.UIDataAdaptor.getExtendedDataModel(UIDataAdaptor.java:467)
Information: at org.richfaces.component.UIDataAdaptor.setRowKey(UIDataAdaptor.java:278)
Information: at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1313)
Information: at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600)
Information: at javax.faces.component.UIForm.visitTree(UIForm.java:344)
Information: at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600)
Information: at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600)
Information: at
com.sun.faces.application.view.StateManagementStrategyImpl.saveView(StateManagementStrategyImpl.java:160)
Information: at
com.sun.faces.application.StateManagerImpl.saveView(StateManagerImpl.java:133)
Information: at
com.sun.faces.application.view.WriteBehindStateWriter.flushToWriter(WriteBehindStateWriter.java:225)
Information: at
com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:418)
Information: at
com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:131)
Information: at
javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288)
Information: at
javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288)
Information: at
com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:121)
Information: at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
Information: at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
Information: at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
<<SERVLET STACK >>
{code}
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
Fix For: 4.2.0.Tracking
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:35 a.m.
New subject: [JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
[
https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s...
]
Frederick Kämpfer edited comment on RF-11382 at 10/5/11 10:33 AM:
------------------------------------------------------------------
FYI here is the stack trace of the getter call with 4.1.0-SNAPSHOT. Maybe it helps.
{code}
<< CALL OF GETTER >>
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at javax.el.BeanELResolver.getValue(BeanELResolver.java:302)
at com.sun.faces.el.DemuxCompositeELResolver._getValue(DemuxCompositeELResolver.java:176)
at com.sun.faces.el.DemuxCompositeELResolver.getValue(DemuxCompositeELResolver.java:203)
at com.sun.el.parser.AstValue.getValue(AstValue.java:116)
at com.sun.el.parser.AstValue.getValue(AstValue.java:163)
at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:219)
at org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:55)
at com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:109)
at javax.faces.component.ComponentStateHelper.eval(ComponentStateHelper.java:194)
at javax.faces.component.ComponentStateHelper.eval(ComponentStateHelper.java:182)
at org.richfaces.component.UISequence.getValue(UISequence.java:178)
at org.richfaces.component.UISequence.createExtendedDataModel(UISequence.java:112)
at
org.richfaces.component.UIDataTableBase.createExtendedDataModel(UIDataTableBase.java:195)
at org.richfaces.component.UIDataAdaptor.getExtendedDataModel(UIDataAdaptor.java:467)
at org.richfaces.component.UIDataAdaptor.setRowKey(UIDataAdaptor.java:278)
at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1313)
at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600)
at javax.faces.component.UIForm.visitTree(UIForm.java:344)
at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600)
at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600)
at
com.sun.faces.application.view.StateManagementStrategyImpl.saveView(StateManagementStrategyImpl.java:160)
at com.sun.faces.application.StateManagerImpl.saveView(StateManagerImpl.java:133)
at
com.sun.faces.application.view.WriteBehindStateWriter.flushToWriter(WriteBehindStateWriter.java:225)
at
com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:418)
at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:131)
at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288)
at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288)
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:121)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
<<SERVLET STACK >>
{code}
was (Author: fkaempfer):
FYI here is the stack trace of the getter call with 4.1.0-SNAPSHOT. Maybe it helps.
{code}
<< CALL OF GETTER >>
Information: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Information: at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
Information: at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
Information: at java.lang.reflect.Method.invoke(Method.java:601)
Information: at javax.el.BeanELResolver.getValue(BeanELResolver.java:302)
Information: at
com.sun.faces.el.DemuxCompositeELResolver._getValue(DemuxCompositeELResolver.java:176)
Information: at
com.sun.faces.el.DemuxCompositeELResolver.getValue(DemuxCompositeELResolver.java:203)
Information: at com.sun.el.parser.AstValue.getValue(AstValue.java:116)
Information: at com.sun.el.parser.AstValue.getValue(AstValue.java:163)
Information: at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:219)
Information: at
org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:55)
Information: at
com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:109)
Information: at
javax.faces.component.ComponentStateHelper.eval(ComponentStateHelper.java:194)
Information: at
javax.faces.component.ComponentStateHelper.eval(ComponentStateHelper.java:182)
Information: at org.richfaces.component.UISequence.getValue(UISequence.java:178)
Information: at
org.richfaces.component.UISequence.createExtendedDataModel(UISequence.java:112)
Information: at
org.richfaces.component.UIDataTableBase.createExtendedDataModel(UIDataTableBase.java:195)
Information: at
org.richfaces.component.UIDataAdaptor.getExtendedDataModel(UIDataAdaptor.java:467)
Information: at org.richfaces.component.UIDataAdaptor.setRowKey(UIDataAdaptor.java:278)
Information: at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1313)
Information: at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600)
Information: at javax.faces.component.UIForm.visitTree(UIForm.java:344)
Information: at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600)
Information: at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600)
Information: at
com.sun.faces.application.view.StateManagementStrategyImpl.saveView(StateManagementStrategyImpl.java:160)
Information: at
com.sun.faces.application.StateManagerImpl.saveView(StateManagerImpl.java:133)
Information: at
com.sun.faces.application.view.WriteBehindStateWriter.flushToWriter(WriteBehindStateWriter.java:225)
Information: at
com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:418)
Information: at
com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:131)
Information: at
javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288)
Information: at
javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288)
Information: at
com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:121)
Information: at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
Information: at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
Information: at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
<<SERVLET STACK >>
{code}
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
Fix For: 4.2.0.Tracking
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:37 a.m.
New subject: [JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
[
https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-11382:
-------------------------------
Comment: was deleted
(was: I don't understand why you assigned it to me - I'm not RF QE and really
don't have anything in common with RichFaces as far as I know. Thanks for the trust,
but better to give it to someone on the project perhaps?)
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
Fix For: 4.2.0.Tracking
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:39 a.m.
New subject: [JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
[
https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-11382:
-------------------------------
Fix Version/s: 4.1.0.CR1
(was: 4.2.0.Tracking)
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
Fix For: 4.1.0.CR1
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:10 p.m.
New subject: [JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
[
https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-11382:
-------------------------------
Fix Version/s: 4.2.0.Tracking
(was: 4.1.0.Tracking)
If the table is nested in a conditionally rendered panel, is the table still evaluated?
If not, this may be useful workaround until we address the issue.
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
Fix For: 4.2.0.Tracking
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:48 a.m.
New subject: [JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
[
https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s...
]
Frederick Kämpfer commented on RF-11382:
----------------------------------------
The only UIComponent that works and I've found so far is h:form.
In the meantime I found a workaround in using JSTL tags. Something like
<c:if test="#{renderCondition}"> ...<r:datatable.../> </c:if>
does the trick.
In that case the table's value attribute is of course not evaluated.
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
Fix For: 4.2.0.Tracking
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:31 a.m.
New subject: [JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
[
https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s...
]
Frank Cornelis commented on RF-11382:
-------------------------------------
This is a very annoying bug. If you have RBAC enabled on the bean that is being called,
the application explodes. When rendered evaluated to false, the dataTable should not call
the bean as it might not have enough permissions in this 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-Tracking
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:41 a.m.
New subject: [JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
7:23 p.m.
New subject: [JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
[
https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-11382:
-------------------------------
Fix Version/s: 4.3.0.Milestone2
(was: 4.3-Tracking)
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.Milestone2
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
7:25 p.m.
New subject: [JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
[
https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-11382:
-------------------------------
Story Points: 4
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.Milestone2
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
9:36 a.m.
New subject: [JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
[
https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-11382:
-------------------------------
Sprint: 4.3.0.M2 - Final Sprint
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.Milestone2
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
7:18 p.m.
New subject: [JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
[
https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s...
]
Brian Leathem commented on RF-11382:
------------------------------------
The _getValue()_ call is made at
[UISequence.java#L109|https://github.com/richfaces/components/blob/develop...]
during _DataModel_ creation. This is initiated at
[UIDataAdaptor.java#L1299|https://github.com/richfaces/components/blob/dev...].
We should look at the impact of skipping row-key evaluation for non-rendered data tables.
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.M2
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
7:20 p.m.
New subject: [JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
[
https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-11382:
-------------------------------
Sprint: (was: 4.3.0.M2 - Final Sprint)
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.M2
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:23 a.m.
New subject: [JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
[
https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-11382:
-------------------------------
Fix Version/s: 4.3.0.M3
(was: 4.3.0.M2)
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
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
5:41 p.m.
New subject: [JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
[
https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-11382:
-------------------------------
Original Estimate: 4 hours
Remaining Estimate: 4 hours
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:19 a.m.
New subject: [JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
[
https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč updated RF-11382:
----------------------------
Sprint: 4.3.0.M3 - EDT and AJAX
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
4174
days inactive
4627
days old
richfaces-issues@lists.jboss.org
24 comments
12 participants
participants (12)
-
Brian Leathem (JIRA) -
Brian Leathem (Updated) (JIRA)
-
Frank Cornelis (JIRA)
-
Frederick Kämpfer (Commented) (JIRA)
-
Frederick Kämpfer (Issue Comment Edited) (JIRA)
-
Frederick Kämpfer (JIRA)
-
Jan Papousek (Assigned) (JIRA)
-
Jan Papousek (Commented) (JIRA)
-
Lukáš Fryč (JIRA)
-
Pavol Pitonak (Assigned) (JIRA)
-
SBS JIRA Integration (JIRA)
-
Zuzka Krejčová (Commented) (JIRA)