[
https://issues.apache.org/jira/browse/EXTCDI-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek resolved EXTCDI-134.
-------------------------------------
Resolution: Fixed
Fix Version/s: 0.9.3
> unified base-config
> -------------------
>
> Key: EXTCDI-134
> URL: https://issues.apache.org/jira/browse/EXTCDI-134
> Project: MyFaces CODI
> Issue Type: Improvement
> Reporter: Gerhard Petracek
> Fix For: 0.9.3
>
>
> basically codi configuration is based on cdi mechanisms.
> however, there are artifacts which have to be configured before cdi is up and
> running.
> instead of hardcoding config names,... it should be handled via
> implementations of ConfiguredValueResolver.
> that also allows to introduce custom config approaches e.g. for the project
> stage.
> via the existing @InvocationOrder annotation it should be possible to specify
> the order and via the ClassDeactivator approach it should be possible to
> deactivate existing implementations of ConfiguredValueResolver.
> optionally it should be possible to aggregate implementations (if it makes
> sense for the specific artifact)
> without custom implementations it should be possible to configure artifacts
> via:
> - system property
> - service loader
> - jndi
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
