[
https://issues.apache.org/jira/browse/MYFACES-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe resolved MYFACES-3814.
-------------------------------------
Resolution: Fixed
Fix Version/s: 2.2.0
> Allow ServiceProviderFinder to be initialized at startup
> --------------------------------------------------------
>
> Key: MYFACES-3814
> URL: https://issues.apache.org/jira/browse/MYFACES-3814
> Project: MyFaces Core
> Issue Type: Task
> Components: JSR-344
> Reporter: Leonardo Uribe
> Assignee: Leonardo Uribe
> Fix For: 2.2.0
>
>
> 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.4#6159)
