myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Struberg (JIRA)" <>
Subject [jira] [Commented] (EXTCDI-174) Introduce @PropertyActivated or @ConfigActivated
Date Tue, 17 May 2011 15:54:47 GMT


Mark Struberg commented on EXTCDI-174:

Interpreter is a neat idea, but most probably way to complicated for casual users. Also the
name should really match with the already existing @ProjectStageActivated.

Btw, what do you mean with 'any expression' ?

> Introduce @PropertyActivated or @ConfigActivated
> ------------------------------------------------
>                 Key: EXTCDI-174
>                 URL:
>             Project: MyFaces CODI
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Mark Struberg
>            Assignee: Gerhard Petracek
> 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:

View raw message