incubator-deltaspike-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gerhard Petracek (Commented) (JIRA)" <>
Subject [jira] [Commented] (DELTASPIKE-36) config-service
Date Tue, 27 Dec 2011 22:30:31 GMT


Gerhard Petracek commented on DELTASPIKE-36:

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)
> config-service
> --------------
>                 Key: DELTASPIKE-36
>                 URL:
>             Project: DeltaSpike
>          Issue Type: New Feature
>          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:!default.jspa
For more information on JIRA, see:


View raw message