[
https://issues.apache.org/jira/browse/TAMAYA-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16631368#comment-16631368
]
Alexander Suter commented on TAMAYA-352:
----------------------------------------
Ah ok!
Basically I like the idea, that ${ENV} can directly be resolved to system or
environment props.
My opinion: Only resolve that in that way when *no resolver prefix* is defined.
I would expect no other resolver to come into play if I specify an explicit
resolver.
For example:
* ${file:/myfile} -> only file resolver can resolve that, no
fallback to env props or sys prop
* ${myprop} -> only resolve that with env or sys prop
resolver. other thougths: only when those property sources are active? ordinal
should be respected?
P.S: Javadoc of the method is not up to date. ;)
> 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)
