[
https://issues.apache.org/jira/browse/MYFACES-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969918#action_12969918
]
Leonardo Uribe commented on MYFACES-2945:
-----------------------------------------
I think it is not necessary to pass FacesConfigurationProvider as param for
getFacesConfigData, because in theory we don't do anything with it before pass
it and wrappers will not do anything with it later. I think it looks good to
load it using
FacesConfigurationProviderFactory.getFacesConfigurationProvider(ExternalContext).
> Make a way to get the FacesConfig from a provider
> -------------------------------------------------
>
> Key: MYFACES-2945
> URL: https://issues.apache.org/jira/browse/MYFACES-2945
> Project: MyFaces Core
> Issue Type: Improvement
> Components: SPI
> Affects Versions: 2.0.2
> Reporter: Ivan
> Assignee: Leonardo Uribe
> Fix For: 2.0.3-SNAPSHOT
>
> Attachments: MYFACES-2945-2.patch, MYFACES-2945-3.patch,
> MYFACES-2945-FacesConfigurationMerger.patch
>
>
> Currently, MyFaces startup listener will parse the all the faces
> configuration files and sort them on each startup time, and it will be better
> to do it once in the deployment time, and get those data structure instances
> from a provider. One possible way is to make those FacesConfig class
> serializable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
