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 2015/02/04 21:09:34 UTC
[jira] [Created] (MYFACES-3954) [perf] Use ResourceLoaderCache for
ResourceHandler.libraryExists(...)
Leonardo Uribe created MYFACES-3954:
---------------------------------------
Summary: [perf] Use ResourceLoaderCache for ResourceHandler.libraryExists(...)
Key: MYFACES-3954
URL: https://issues.apache.org/jira/browse/MYFACES-3954
Project: MyFaces Core
Issue Type: Improvement
Components: JSR-344
Reporter: Leonardo Uribe
Assignee: Leonardo Uribe
Priority: Minor
Thinking about some stuff for JSF 2.3 and checking how ResourceHandler is implemented, I notice the call to ResourceHandler.libraryExists(...) does not take advantage of ResourceLoaderCache and instead call every ResourceLoader and ContractResourceLoader. The problem is these loaders has some calls that are slow, while a cache lookup can be fast.
Most of the time. ResourceHandler.libraryExists(...) is called when a facelet is compiled and it requires a composite components. Since there is already a cache for compiled facelets, the impact is seen only when the facelet is compiled, but this step is done for every facelet that makes a reference to the same composite component.
It is a minor improvement, but it will improve the speed of the compilation step.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)