[jira] [Resolved] (EXTCDI-174) Introduce @PropertyActivated or @ConfigActivated

["Gerhard Petracek (JIRA)" <de...@myfaces.apache.org>]

     [ https://issues.apache.org/jira/browse/EXTCDI-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gerhard Petracek resolved EXTCDI-174.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.0.0

name of the annotation: @ExpressionActivated

supported expressions:

"key1==value1;key2!=value2"

and it's possible to mark required keys - e.g.:
"key2==*;key2!=value2"

> Introduce @PropertyActivated or @ConfigActivated
> ------------------------------------------------
>
>                 Key: EXTCDI-174
>                 URL: https://issues.apache.org/jira/browse/EXTCDI-174
>             Project: MyFaces CODI
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Mark Struberg
>            Assignee: Gerhard Petracek
>             Fix For: 1.0.0
>
>
> While at JAX, I got pretty often asked if there is a way to configure <alternatives> automatically via configuration. I pointed them to @ProjectStageActivated and this solved 60% of the problems.
> But there are pretty often more complex scenarios where users like to switch between e.g. database vendors based on an external configuration.
> This could e.g. be a normal java properties file and something like
> {code}
> @PropertyActivated("user.databyse", "mysql")
> {code}
> where the first parameter is the name and the 2nd is the value which must be set.
> Please add further ideas for ways to change those configurations.
> The actual implementation should be trivial as we have most of the work done already in ProjectStageActivationExtension.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira