[
https://issues.apache.org/jira/browse/DELTASPIKE-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13176342#comment-13176342
]
Gerhard Petracek edited comment on DELTASPIKE-36 at 12/27/11 11:30 PM:
-----------------------------------------------------------------------
in myfaces codi it's handled via:
ConfiguredValueResolver [1], ConfiguredValueDescriptor [2] and internally it
uses the Aggregatable api to support multiple values.
a ConfiguredValueResolver can be configured via the std. spi mechanism provided
by java1.6+. (with @InvocationOrder it's possible to define an order)
[1] http://s.apache.org/ht
[2] http://s.apache.org/ZaL
was (Author: gpetracek):
in myfaces codi it's handled via:
ConfiguredValueResolver, ConfiguredValueDescriptor and internally it uses the
Aggregatable api to support multiple values.
a ConfiguredValueResolver can be configured via the std. spi mechanism provided
by java1.6+. (with @InvocationOrder it's possible to define an order)
> review and discuss ConfiguredValueResolver
> ------------------------------------------
>
> Key: DELTASPIKE-36
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-36
> Project: DeltaSpike
> Issue Type: Task
> Components: Core
> Reporter: Gerhard Petracek
> Assignee: Gerhard Petracek
>
> for several features we need a pluggable config-service which has to be
> independent of cdi because it's needed e.g. during the bootstrapping process
> of a cdi container.
> an implementation is aware of a config source like property-files or xml
> files or jndi values and has to return 1-n configured values for a given key.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
