You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tamaya.apache.org by "Anatole Tresch (JIRA)" <ji...@apache.org> on 2018/09/28 03:08:00 UTC

[jira] [Resolved] (TAMAYA-352) Unpredictable behavior when a resolver can't resolve the value

     [ https://issues.apache.org/jira/browse/TAMAYA-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anatole Tresch resolved TAMAYA-352.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 0.4-incubating

> 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)