[
https://issues.apache.org/jira/browse/TAMAYA-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16631291#comment-16631291
]
ASF subversion and git services commented on TAMAYA-352:
--------------------------------------------------------
Commit ac45f107b16ee01d7aea3dc26285e93be157ff13 in
incubator-tamaya-extensions's branch refs/heads/master from [~anatole]
[
https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya-extensions.git;h=ac45f10
]
TAMAYA-352 Added fallback calling of other resolvers, only trying system and
env props as a fallback.
> Unpredictable behavior when a resolver can't resolve the value
> --------------------------------------------------------------
>
> Key: TAMAYA-352
> URL: https://issues.apache.org/jira/browse/TAMAYA-352
> Project: Tamaya
> Issue Type: Improvement
> Reporter: Alexander Suter
> Assignee: Anatole Tresch
> Priority: Major
> Fix For: 0.4-incubating
>
>
> If a resolver can't resolve the value, then all other resolvers acts as
> fallback.
> * For example: FileResolver can't resolve the value, because the file does
> not exist. Now my DecryptResolver resolves that value and just decrypt it.
> I think that is a really strange and unpredictable behavior. I recommend to
> remove that fallback. Because when I targeting a specific resolver, then I
> want that, that resolver resolvs my value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
