The JSF2 Facelets API provides applications/frameworks with control over how Facelets files are
located/loaded via the javax.faces.view.facelets.ResourceResolver. We leverage this API to allow loading
of user-specific, personalized/customized Facelets files from an external source (eg. from a rdbms).
While ResourceResolver allows us to load these user-specific views, we run into scalability problems
due to the default caching strategy for Facelet objects. In particular, DefaultFaceletFactory (now an
internal/implementation class) caches all Facelet objects forever. This does not work for our use case.
We need the ability to prune user-specific Facelet objects from the cache in response to application
Logging this issue to request that we expose a new API that allows applications/frameworks to control
Facelet object caching behavior.