You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Mateusz Mieszkowski (JIRA)" <ji...@apache.org> on 2013/11/21 10:24:43 UTC

[jira] [Commented] (WICKET-5422) ComponentRenderer.renderComponent() adds a page to DataStore

    [ https://issues.apache.org/jira/browse/WICKET-5422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13828630#comment-13828630 ] 

Mateusz Mieszkowski commented on WICKET-5422:
---------------------------------------------

Martin Grigorov's comment from users-list:
"The page should be marked as stateless to avoid storing it."

> ComponentRenderer.renderComponent() adds a page to DataStore
> ------------------------------------------------------------
>
>                 Key: WICKET-5422
>                 URL: https://issues.apache.org/jira/browse/WICKET-5422
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 6.12.0
>            Reporter: Mateusz Mieszkowski
>
> I'm using ComponenetRenderer withing CustomTooltipBehavior (wicket-jquery-ui) to generate tooltip content. I add this to about 50 rows in my table so I run renderComponent() method as many times.
> All worked fine but there was a problem with performance when I used Fragment component with markup attached to the WebPage. I did some digging and finally checked http://localhost:8080/context/wicket/internal/debug/diskDataStore and it appeared that for one request, Wicket stores 51 pages in it. All of the size of the whole page (about 300kB) and all of them named org.apache.wicket.core.util.string.ComponentRenderer$RenderPage.
> I changed implementation from Fragment to Panel componenet and the size was reduced to (1kB) but still all of these items were stored in the DataStore.
> It seems that this method is creating a dummy page in order to create the markup, but how can I avoid storing these pages?



--
This message was sent by Atlassian JIRA
(v6.1#6144)