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 2013/11/01 03:04:17 UTC
[jira] [Created] (MYFACES-3814) Integrate default
ServiceProviderFinder into FacesConfig
Leonardo Uribe created MYFACES-3814:
---------------------------------------
Summary: Integrate default ServiceProviderFinder into FacesConfig
Key: MYFACES-3814
URL: https://issues.apache.org/jira/browse/MYFACES-3814
Project: MyFaces Core
Issue Type: Task
Components: JSR-344
Reporter: Leonardo Uribe
The code inside ServiceProviderFinder usually involves classpath scanning and read files from different locations. That code is ok, but it would be great if we can put that into FacesConfig as a configuration information.
The idea is just list all SPI interfaces we are using in MyFaces Core, and do the scanning of everything we need right at startup and finally store that information into FacesConfig, just like it was done for Facelet tag lib configuration.
If FacesConfig is serialized and deserialized, that scanning will not be necessary and the startup will be faster.
--
This message was sent by Atlassian JIRA
(v6.1#6144)