[
https://issues.apache.org/jira/browse/TAMAYA-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16631289#comment-16631289
]
Anatole Tresch commented on TAMAYA-352:
---------------------------------------
Basically the idea is that ${ENV} can directly be resolved to system or
environment props without using an explicit resolver. I updated the
implementation to do exactly this as a fallback. This result in similar
behaviour, despite that no other resolver is actively called.
> 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
>
> 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)
