[jira] [Commented] (EXTCDI-174) Introduce @PropertyActivated or @ConfigActivated
[
https://issues.apache.org/jira/browse/EXTCDI-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13034834#comment-13034834
]
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: https://issues.apache.org/jira/browse/EXTCDI-174
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: http://www.atlassian.com/software/jira
[jira] [Commented] (EXTCDI-174) Introduce @PropertyActivated or @ConfigActivated
[
https://issues.apache.org/jira/browse/EXTCDI-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13034837#comment-13034837
]
Gerhard Petracek commented on EXTCDI-174:
-
@PropertyActivated(user.database, mysql) is imo too error prone
any expression is a placeholder. by default i would suggest to support
@ActivatedOn(user.database==mysql;property2==value2)
later on we can extend the syntax e.g. to
@ActivatedOn(user.database==mysql || property2==value2)
that isn't possible with your @PropertyActivated suggestion.
by default it is as easy as your suggestion! and if an advanced user would
like to extend the syntax s/he can simply do it by providing a custom
interpreter implementation.
so we don't have to support all edge cases.
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
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
[jira] [Commented] (EXTCDI-174) Introduce @PropertyActivated or @ConfigActivated
[
https://issues.apache.org/jira/browse/EXTCDI-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13030753#comment-13030753
]
Gerhard Petracek commented on EXTCDI-174:
-
suggestion:
@ActivatedOn(any expression)
... by default it would be interpreted by ConfiguredValueInterpreter which
delegates to the existing ConfiguredValueResolver (which also allows to add
custom resolvers to the lookup chain).
as an alternative it would be possible to overrule the default interpreter via:
@ActivatedOn(value = any expression, interpreter = CustomInterpreter.class)
- per default it's simple but still very extensible
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: Mark Struberg
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
