[
https://issues.apache.org/jira/browse/TAMAYA-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626409#comment-16626409
]
ASF GitHub Bot commented on TAMAYA-352:
---------------------------------------
Github user alexsuter commented on the issue:
https://github.com/apache/incubator-tamaya-extensions/pull/10
Before I fix the test and contribute new test, I want first to talk about
the idea behind this pull request. What do you think about that?
> 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
> Priority: Major
>
> 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)
