[
https://issues.apache.org/jira/browse/DELTASPIKE-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13176418#comment-13176418
]
Gerhard Petracek edited comment on DELTASPIKE-37 at 12/28/11 2:53 AM:
----------------------------------------------------------------------
we need a final name before the first release. for now we are using
DeltaSpikeConfig for the marker interface.
(alternative configuration mechanisms (config via xml, properties file,...) can
be provided via @Alternative (btw. @DefaultBean) annotated beans or directly as
additional option by the default impl. - we will discuss this topic later on.)
was (Author: gpetracek):
we need a final name before the first release. for now we are using
DeltaSpikeConfig for the marker interface.
(alternative configuration mechanisms (config via xml, properties file,...) can
be provided via @Alternative annotated beans or directly as additional option
by the default impl. - we will discuss this topic later on.)
> type-safe DeltaSpikeConfig
> --------------------------
>
> Key: DELTASPIKE-37
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-37
> Project: DeltaSpike
> Issue Type: New Feature
> Components: Core
> Reporter: Gerhard Petracek
> Assignee: Gerhard Petracek
>
> deltaspike itself can be configured via config classes which are std.
> (application scoped) cdi beans. DeltaSpikeConfig is the marker interface for
> all those config classes. for providing custom values, users have to extend
> the config class, annotate it with @Specializes and provide the custom value
> by overriding the corresponding getter method.
> we need a final name before the first release. for now we are using
> DeltaSpikeConfig for the marker interface
--
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
