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 (JIRA)" <de...@myfaces.apache.org> on 2011/01/21 04:57:43 UTC

[jira] Resolved: (MYFACES-3021) javax.faces.view.facelets.ComponentHandler initializes TagHandlerDelegate on startup, but it should be on demand

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

Leonardo Uribe resolved MYFACES-3021.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.4-SNAPSHOT

> javax.faces.view.facelets.ComponentHandler initializes TagHandlerDelegate on startup, but it should be on demand
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: MYFACES-3021
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3021
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: JSR-314
>    Affects Versions: 2.0.3
>            Reporter: Leonardo Uribe
>            Assignee: Leonardo Uribe
>             Fix For: 2.0.4-SNAPSHOT
>
>
> Call TagHandlerDelegateFactory.createComponentHandlerDelegate on ComponentHandler constructor is not a good idea. The reason is we are creating over and over unnecessary instances of ComponentHandler through the factory that in the end they could never be used.
> It also causes a problem when it is required to wrap a ComponentHandler instance for a composite component (using TagHandlerDelegateFactory)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.