[jira] [Commented] (MYFACES-3918) DefaultFaceletsStateManagementStrategy: keep list of removed client IDs stable over time

["Marc H. (JIRA)" <de...@myfaces.apache.org>]

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

Marc H. commented on MYFACES-3918:
----------------------------------

I've juste tested it using the current svn head and the problem seems indeed gone.

We will be switching to myfaces 2.1.16 as soon as it is released.

Huge thanks for your reactivity!

> DefaultFaceletsStateManagementStrategy: keep list of removed client IDs stable over time
> ----------------------------------------------------------------------------------------
>
>                 Key: MYFACES-3918
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3918
>             Project: MyFaces Core
>          Issue Type: Improvement
>    Affects Versions: 2.1.15, 2.1.16-SNAPSHOT
>            Reporter: Marc H.
>            Assignee: Leonardo Uribe
>             Fix For: 2.0.22, 2.1.16, 2.2.5
>
>
> As described in this thread: http://markmail.org/thread/ayo7ooo3nzpzahd4
> Clearing part of the component tree (calling getChildren().clear()) several time while staying on the same view (through Ajax requests) causes the list of removed client IDs (maintained in org.apache.myfaces.view.facelets.DefaultFaceletsStateManagementStrategy) to grow endlessly, which in turns degrades performances.
> In our situation, a form with approximately 400 components took ~250ms on the first request to more than 1 second after ~15 update.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)