[prev in list] [next in list] [prev in thread] [next in thread] 

List:       james-dev
Subject:    [jira] [Resolved] (JAMES-2547) Replace concrete PropertiesConfiguration type by Configuration interf
From:       "Antoine Duprat (JIRA)" <server-dev () james ! apache ! org>
Date:       2018-09-17 6:36:00
Message-ID: JIRA.13184907.1536846821000.88018.1537166160305 () Atlassian ! JIRA
[Download RAW message or body]


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

Antoine Duprat resolved JAMES-2547.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 3.2.0

merged

> Replace concrete PropertiesConfiguration type by Configuration interface in \
>                 PropertiesProvider
> ----------------------------------------------------------------------------------------------
>  
> Key: JAMES-2547
> URL: https://issues.apache.org/jira/browse/JAMES-2547
> Project: James Server
> Issue Type: Improvement
> Components: configuration
> Reporter: Jean Helou
> Priority: Major
> Fix For: 3.2.0
> 
> 
> This makes testing configuration components easier.
> For exemple   subclassing   PropertiesProvider to make it return  an in memory \
> configuration such as a MapConfiguration instead of being bound to the concrete \
> PropertiesConfiguration implementation. I have found no place in the project where \
> relying on the concrete type is actually useful. All uses were replaceable by the \
> interface or by a static call to the top of the hierarchy (AbstractConfiguration).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]