deltaspike-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Struberg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DELTASPIKE-195) create default-value handling for ConfigResolver
Date Wed, 13 Jun 2012 11:11:43 GMT

    [ https://issues.apache.org/jira/browse/DELTASPIKE-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294351#comment-13294351
] 

Mark Struberg commented on DELTASPIKE-195:
------------------------------------------

We will also need to set the default for eager to false. This is also the behaviour you get
by using the programmatic lookup. It also works much better together with the new defaultValue.
People can set eager to true manually if they like.
                
> create default-value handling for ConfigResolver
> ------------------------------------------------
>
>                 Key: DELTASPIKE-195
>                 URL: https://issues.apache.org/jira/browse/DELTASPIKE-195
>             Project: DeltaSpike
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 0.3-incubating
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
>             Fix For: 0.3-incubating
>
>
> currently we only support getPropertyValue(String key). 
> We should also provide a way to specify a default value in case no value is configured
by the user.
> This is very useful if you like to use the configuration mechanism to override default
behaviour.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message