You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by "Gerhard Petracek (Created) (JIRA)" <ji...@apache.org> on 2011/12/28 03:47:30 UTC
[jira] [Created] (DELTASPIKE-37) type-safe DeltaSpikeConfig
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
[jira] [Resolved] (DELTASPIKE-37) type-safe DeltaSpikeConfig
Posted by "Gerhard Petracek (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DELTASPIKE-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gerhard Petracek resolved DELTASPIKE-37.
----------------------------------------
Resolution: Fixed
Fix Version/s: 0.1-SNAPSHOT
> 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
> Fix For: 0.1-SNAPSHOT
>
>
> 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
[jira] [Commented] (DELTASPIKE-37) type-safe DeltaSpikeConfig
Posted by "Gerhard Petracek (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DELTASPIKE-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13176418#comment-13176418 ]
Gerhard Petracek commented on DELTASPIKE-37:
--------------------------------------------
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
[jira] [Issue Comment Edited] (DELTASPIKE-37) type-safe
DeltaSpikeConfig
Posted by "Gerhard Petracek (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Closed] (DELTASPIKE-37) type-safe DeltaSpikeConfig
Posted by "Gerhard Petracek (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DELTASPIKE-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gerhard Petracek closed DELTASPIKE-37.
--------------------------------------
> 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
> Fix For: 0.1-incubating
>
>
> 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