[
https://issues.apache.org/jira/browse/DELTASPIKE-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek updated DELTASPIKE-390:
----------------------------------------
Description:
@ViewMetaData#preProcessor is predefined per view-meta-data.
it should be possible to replace the default implementations globally (via the
config mechanism of deltaspike).
example:
org.apache.deltaspike.jsf.api.config.view.View$ViewConfigPreProcessor=org.custom.CustomViewConfigPreProcessor
-> org.custom.CustomViewConfigPreProcessor should be used instead of
org.apache.deltaspike.jsf.api.config.view.View$ViewConfigPreProcessor
was:
@ViewMetaData#preProcessor is predefined per view-meta-data.
it should be possible to replace the default implementations globally.
> optional custom ConfigPreProcessor
> ----------------------------------
>
> Key: DELTASPIKE-390
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-390
> Project: DeltaSpike
> Issue Type: Improvement
> Components: JSF-Module
> Affects Versions: 0.4
> Reporter: Gerhard Petracek
> Fix For: 0.5
>
>
> @ViewMetaData#preProcessor is predefined per view-meta-data.
> it should be possible to replace the default implementations globally (via
> the config mechanism of deltaspike).
> example:
> org.apache.deltaspike.jsf.api.config.view.View$ViewConfigPreProcessor=org.custom.CustomViewConfigPreProcessor
> -> org.custom.CustomViewConfigPreProcessor should be used instead of
> org.apache.deltaspike.jsf.api.config.view.View$ViewConfigPreProcessor
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
