[prev in list] [next in list] [prev in thread] [next in thread] 

List:       myfaces-dev
Subject:    [jira] [Resolved] (MYFACES-3555) [perf] store location key in composite component just once
From:       "Leonardo Uribe (JIRA)" <dev () myfaces ! apache ! org>
Date:       2012-05-30 16:12:24
Message-ID: 332207497.16861.1338394344843.JavaMail.jiratomcat () issues-vm
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/MYFACES-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Leonardo Uribe resolved MYFACES-3555.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1.8
                   2.0.14
    
> [perf] store location key in composite component just once
> ----------------------------------------------------------
> 
> Key: MYFACES-3555
> URL: https://issues.apache.org/jira/browse/MYFACES-3555
> Project: MyFaces Core
> Issue Type: Improvement
> Components: JSR-314
> Reporter: Leonardo Uribe
> Assignee: Leonardo Uribe
> Fix For: 2.0.14, 2.1.8
> 
> 
> In CompositeComponentDefinitionTagHandler, there are some lines that store the \
> Location object inside the composite component, that is used later for EL \
> resolution (CompositeComponentELUtils.LOCATION_KEY), but each time the algorithm \
> pass over that part when the view is refreshed, the same value is stored over and \
> over again. With as simple check we can avoid that and minimize the state size when \
> composite component are used.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: \
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more \
information on JIRA, see: http://www.atlassian.com/software/jira

        


[prev in list] [next in list] [prev in thread] [next in thread]