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

Posted to dev@deltaspike.apache.org by "Mark Struberg (JIRA)" <ji...@apache.org> on 2016/05/17 17:16:12 UTC

[jira] [Resolved] (DELTASPIKE-1147) TypedResolver behaves different than ConfigResolver

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

Mark Struberg resolved DELTASPIKE-1147.
---------------------------------------
    Resolution: Fixed

> TypedResolver behaves different than ConfigResolver
> ---------------------------------------------------
>
>                 Key: DELTASPIKE-1147
>                 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1147
>             Project: DeltaSpike
>          Issue Type: Bug
>          Components: Configuration
>    Affects Versions: 1.6.1
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
>             Fix For: 1.6.2
>
>
> We have some cases where the TypedResolver return different values than performing the same operation via the legacy ConfigResolver API.
> 1.) default values of 'null' get handled different
> 2.) ProjectStage specific empty values abort the resolver chain in older versions. In 1.6.1 it continues the evaluation. This leads to different values.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)