[
https://issues.apache.org/jira/browse/TAMAYA-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626072#comment-16626072
]
ASF GitHub Bot commented on TAMAYA-352:
---------------------------------------
GitHub user alexsuter opened a pull request:
https://github.com/apache/incubator-tamaya-extensions/pull/10
/TAMAYA-352 Unpredictable behavior when a resolver can't resolve the …
…value
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/alexsuter/incubator-tamaya-extensions patch-2
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-tamaya-extensions/pull/10.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #10
----
commit fc9bfaf0f2d8d6555a7a581a9263795d0d2f05be
Author: Alex <alexander.suter@...>
Date: 2018-09-24T16:08:53Z
/TAMAYA-352 Unpredictable behavior when a resolver can't resolve the value
----
> 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)
