myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Blake Sullivan (JIRA)" <>
Subject [jira] [Resolved] (TRINIDAD-2273) Allow scheme for application to control UIViewRoot caching logic
Date Wed, 27 Jun 2012 23:41:42 GMT


Blake Sullivan resolved TRINIDAD-2273.

       Resolution: Fixed
    Fix Version/s: 2.0.0-core
> Allow scheme for application to control UIViewRoot caching logic
> ----------------------------------------------------------------
>                 Key: TRINIDAD-2273
>                 URL:
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>    Affects Versions:  1.2.12-core, 2.0.1-core
>         Environment: all
>            Reporter: Blake Sullivan
>            Assignee: Blake Sullivan
>             Fix For: 2.0.0-core
>         Attachments: trin_2273_2_1.patch
>   Original Estimate: 48h
>  Remaining Estimate: 48h
> When UIViewRoot caching is enabled, the cached UIViewRoots can consume considerable memory
across all of the users.  The proposal is to extend the allowed values of the Servlet Initialization
>     <param-name>org.apache.myfaces.trinidad.CACHE_VIEW_ROOT</param-name>
> to support, in addition to the current "true", and "false" values, the values of:
> "strong" UIViewRoot caching is enabled and always uses strong references to the cached
> "soft" UIViewRoot caching is enabled and always uses soft references to the cached UIViewRoot,
allowing the cached UIViewRoots to be purged if under memory pressure
> <classname> The fully qualified classname of an implementation of org.apache.myfaces.trinidad.util.ref.PseudoReferenceFactory
returning any desired PseudoReference implementation.
> In addition, the value of "true" now uses the value of a PseudoReferenceFactory implementation
registered under the service name "org.apache.myfaces.trinidad.CACHE_VIEW_ROOT" if one is
registered, otherwise, it uses a strong reference, to duplicate the current functionality

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message