You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Leonardo Uribe (Created) (JIRA)" <de...@myfaces.apache.org> on 2012/01/11 02:42:39 UTC

[jira] [Created] (MYFACES-3443) [perf] cache Method and Field instances when PostConstruct processing is done and default LifecycleProvider is set

[perf] cache Method and Field instances when PostConstruct processing is done and default LifecycleProvider is set
------------------------------------------------------------------------------------------------------------------

                 Key: MYFACES-3443
                 URL: https://issues.apache.org/jira/browse/MYFACES-3443
             Project: MyFaces Core
          Issue Type: Improvement
          Components: JSR-314
            Reporter: Leonardo Uribe
            Assignee: Leonardo Uribe


Each time a managed bean is created, it is inspected for PostConstruct/PreDestroy annotations. The default algorithm does not cache that information. Usually the container do that, so this effect is not seen in containers like Tomcat and others (MyFaces provide a LifecycleProvider for them).

By default, we can use the same trick for MetaRulesetImpl, that has a WeakHashMap<ClassLoader, Map<..., ...> > so when the application is undeployed, no cyclic reference is hold.

--
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

        

[jira] [Resolved] (MYFACES-3443) [perf] cache Method and Field instances when PostConstruct processing is done and default LifecycleProvider is set

Posted by "Leonardo Uribe (Resolved) (JIRA)" <de...@myfaces.apache.org>.
     [ https://issues.apache.org/jira/browse/MYFACES-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leonardo Uribe resolved MYFACES-3443.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1.6
                   2.0.12
    
> [perf] cache Method and Field instances when PostConstruct processing is done and default LifecycleProvider is set
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: MYFACES-3443
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3443
>             Project: MyFaces Core
>          Issue Type: Improvement
>          Components: JSR-314
>            Reporter: Leonardo Uribe
>            Assignee: Leonardo Uribe
>             Fix For: 2.0.12, 2.1.6
>
>
> Each time a managed bean is created, it is inspected for PostConstruct/PreDestroy annotations. The default algorithm does not cache that information. Usually the container do that, so this effect is not seen in containers like Tomcat and others (MyFaces provide a LifecycleProvider for them).
> By default, we can use the same trick for MetaRulesetImpl, that has a WeakHashMap<ClassLoader, Map<..., ...> > so when the application is undeployed, no cyclic reference is hold.

--
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