[JBoss JIRA] (RF-12601) Memory leak (permgen) in combination with xerces
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12601?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-12601.
--------------------------------
Resolution: Rejected
> Memory leak (permgen) in combination with xerces
> ------------------------------------------------
>
> Key: RF-12601
> URL: https://issues.jboss.org/browse/RF-12601
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.2.2.Final
> Environment: Tomcat 6.0.36
> myFaces 2.1.9
> xerces 2.9.0
> Reporter: Michael Heinen
> Labels: memoryleak, waiting_on_user
> Attachments: leak.war
>
>
> I created a simple web app without any classes, xhtml files, config files.
> There are only some jars, including xerces, in the lib folder only.
> A "java.lang.OutOfMemoryError: PermGen space" occurs if this app is started, stopped and restarted.
> It does not occur if either richfaces-components-XXX hars OR xerces are removed from the webApp,
--
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, 5 months
[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 resolved RF-11382.
--------------------------------
Resolution: Done
> 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, 5 months
[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 reopened RF-11382:
--------------------------------
> 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, 5 months
[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 closed RF-11382.
------------------------------
Resolution: Done
Changed the UIDataAdaptor#requiresRowIteration to use the VisitHint.SKIP_ITERATION enum intorduced in JSF 2.1
> 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, 5 months
[JBoss JIRA] (RF-12611) rich:dataTable doesn't call restoreState() on a row-level composite component
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12611?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-12611.
--------------------------------
Resolution: Done
Changed the UIDataAdaptor#requiresRowIteration to use the VisitHint.SKIP_ITERATION enum intorduced in JSF 2.1
> rich:dataTable doesn't call restoreState() on a row-level composite component
> -----------------------------------------------------------------------------
>
> Key: RF-12611
> URL: https://issues.jboss.org/browse/RF-12611
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.2.3.Final
> Environment: Debian Wheezy, Linux, amd64
> Reporter: Mark Cave-Ayland
> Assignee: Brian Leathem
> Fix For: 4.3.0.M3
>
> Attachments: RFStateBug1.tar.gz
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> I currently have a row-level composite component that works well within a h:dataTable which I am looking to migrate to rich:dataTable for more flexibility with layout. However when embedded within a rich:dataTable, the component state is not preserved during the RESTORE_VIEW phase.
> Further investigation with a debugger shows that the problem is within UIDataAdapter::restoreState() in that requiresRowIteration() returns false during the RESTORE_VIEW phase, and so the restoreState() function within the row-level composite component is never called.
> The related transcript from IRC can be found here: http://transcripts.jboss.org/channel/irc.freenode.org/%23richfaces/2012/%....
> Many thanks,
> Mark.
--
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, 5 months
[JBoss JIRA] (RF-10154) UIDataAdaptor vs. UIData visitTee small difference
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-10154?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-10154.
--------------------------------
Resolution: Done
Changed the UIDataAdaptor#requiresRowIteration to use the VisitHint.SKIP_ITERATION enum intorduced in JSF 2.1
> UIDataAdaptor vs. UIData visitTee small difference
> --------------------------------------------------
>
> Key: RF-10154
> URL: https://issues.jboss.org/browse/RF-10154
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.0.0.Milestone5
> Environment: RichFaces 4.0.X trunk, svn rev. 20913
> Reporter: Martin Kočí
> Assignee: Brian Leathem
> Priority: Minor
> Labels: jsf21
> Fix For: 4.3.0.M3
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> {code}
> <r:extendedDataTable var="zeile">
> <r:column>
> <h:outputText rendered="#{fasole.method(zeile)}"
> </r:column>
> </r:extendedDataTable>
> {code}
> +
> org.richfaces.component.UIDataAdaptor.visitTree(VisitContext, VisitCallback) with VisitHint SKIP_UNRENDERED (in render response phase for example)
> Problem: org.richfaces.component.UIDataAdaptor.visitDataChildren(VisitContext, VisitCallback, boolean) calls visitComponents(getFacetsAndChildren(), visitContext, callback);-> it will visit h:outputText component and test if is rendered -> #{fasole.method(zeile)} but no row available -> calls fasole.method with null parameter and causes an unexpected NPE
> j.f.c.UIData does not visit column chidren for -1 rowIndex (null rowKey in RichFaces), UIData.visitTree JavaDoc says: "Take no action on non-UIColumn children".
--
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, 5 months
[JBoss JIRA] (RF-10154) UIDataAdaptor vs. UIData visitTee small difference
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-10154?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-10154:
-------------------------------
Sprint: 4.3.0.M3 - EDT and AJAX
> UIDataAdaptor vs. UIData visitTee small difference
> --------------------------------------------------
>
> Key: RF-10154
> URL: https://issues.jboss.org/browse/RF-10154
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.0.0.Milestone5
> Environment: RichFaces 4.0.X trunk, svn rev. 20913
> Reporter: Martin Kočí
> Assignee: Brian Leathem
> Priority: Minor
> Labels: jsf21
> Fix For: 4.3.0.M3
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> {code}
> <r:extendedDataTable var="zeile">
> <r:column>
> <h:outputText rendered="#{fasole.method(zeile)}"
> </r:column>
> </r:extendedDataTable>
> {code}
> +
> org.richfaces.component.UIDataAdaptor.visitTree(VisitContext, VisitCallback) with VisitHint SKIP_UNRENDERED (in render response phase for example)
> Problem: org.richfaces.component.UIDataAdaptor.visitDataChildren(VisitContext, VisitCallback, boolean) calls visitComponents(getFacetsAndChildren(), visitContext, callback);-> it will visit h:outputText component and test if is rendered -> #{fasole.method(zeile)} but no row available -> calls fasole.method with null parameter and causes an unexpected NPE
> j.f.c.UIData does not visit column chidren for -1 rowIndex (null rowKey in RichFaces), UIData.visitTree JavaDoc says: "Take no action on non-UIColumn children".
--
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, 5 months
[JBoss JIRA] (RF-10154) UIDataAdaptor vs. UIData visitTee small difference
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-10154?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-10154:
-------------------------------
Original Estimate: 1 hour (was: 1 minute)
Remaining Estimate: 1 hour (was: 1 minute)
> UIDataAdaptor vs. UIData visitTee small difference
> --------------------------------------------------
>
> Key: RF-10154
> URL: https://issues.jboss.org/browse/RF-10154
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.0.0.Milestone5
> Environment: RichFaces 4.0.X trunk, svn rev. 20913
> Reporter: Martin Kočí
> Assignee: Brian Leathem
> Priority: Minor
> Labels: jsf21
> Fix For: 4.3.0.M3
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> {code}
> <r:extendedDataTable var="zeile">
> <r:column>
> <h:outputText rendered="#{fasole.method(zeile)}"
> </r:column>
> </r:extendedDataTable>
> {code}
> +
> org.richfaces.component.UIDataAdaptor.visitTree(VisitContext, VisitCallback) with VisitHint SKIP_UNRENDERED (in render response phase for example)
> Problem: org.richfaces.component.UIDataAdaptor.visitDataChildren(VisitContext, VisitCallback, boolean) calls visitComponents(getFacetsAndChildren(), visitContext, callback);-> it will visit h:outputText component and test if is rendered -> #{fasole.method(zeile)} but no row available -> calls fasole.method with null parameter and causes an unexpected NPE
> j.f.c.UIData does not visit column chidren for -1 rowIndex (null rowKey in RichFaces), UIData.visitTree JavaDoc says: "Take no action on non-UIColumn children".
--
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, 5 months
[JBoss JIRA] (RF-12611) rich:dataTable doesn't call restoreState() on a row-level composite component
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12611?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12611:
-------------------------------
Sprint: 4.3.0.M3 - EDT and AJAX
> rich:dataTable doesn't call restoreState() on a row-level composite component
> -----------------------------------------------------------------------------
>
> Key: RF-12611
> URL: https://issues.jboss.org/browse/RF-12611
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.2.3.Final
> Environment: Debian Wheezy, Linux, amd64
> Reporter: Mark Cave-Ayland
> Assignee: Brian Leathem
> Fix For: 4.3.0.M3
>
> Attachments: RFStateBug1.tar.gz
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> I currently have a row-level composite component that works well within a h:dataTable which I am looking to migrate to rich:dataTable for more flexibility with layout. However when embedded within a rich:dataTable, the component state is not preserved during the RESTORE_VIEW phase.
> Further investigation with a debugger shows that the problem is within UIDataAdapter::restoreState() in that requiresRowIteration() returns false during the RESTORE_VIEW phase, and so the restoreState() function within the row-level composite component is never called.
> The related transcript from IRC can be found here: http://transcripts.jboss.org/channel/irc.freenode.org/%23richfaces/2012/%....
> Many thanks,
> Mark.
--
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, 5 months
[JBoss JIRA] (RF-12611) rich:dataTable doesn't call restoreState() on a row-level composite component
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12611?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12611:
-------------------------------
Original Estimate: 1 hour
Remaining Estimate: 1 hour
> rich:dataTable doesn't call restoreState() on a row-level composite component
> -----------------------------------------------------------------------------
>
> Key: RF-12611
> URL: https://issues.jboss.org/browse/RF-12611
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.2.3.Final
> Environment: Debian Wheezy, Linux, amd64
> Reporter: Mark Cave-Ayland
> Assignee: Brian Leathem
> Fix For: 4.3.0.M3
>
> Attachments: RFStateBug1.tar.gz
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> I currently have a row-level composite component that works well within a h:dataTable which I am looking to migrate to rich:dataTable for more flexibility with layout. However when embedded within a rich:dataTable, the component state is not preserved during the RESTORE_VIEW phase.
> Further investigation with a debugger shows that the problem is within UIDataAdapter::restoreState() in that requiresRowIteration() returns false during the RESTORE_VIEW phase, and so the restoreState() function within the row-level composite component is never called.
> The related transcript from IRC can be found here: http://transcripts.jboss.org/channel/irc.freenode.org/%23richfaces/2012/%....
> Many thanks,
> Mark.
--
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, 5 months