You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tamaya.apache.org by "Oliver B. Fischer (JIRA)" <ji...@apache.org> on 2016/11/20 16:04:58 UTC
[jira] [Assigned] (TAMAYA-198) tamaya-formats blindly tries (and
failes) to parse a config file with multiple formats
[ https://issues.apache.org/jira/browse/TAMAYA-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oliver B. Fischer reassigned TAMAYA-198:
----------------------------------------
Assignee: Oliver B. Fischer
> tamaya-formats blindly tries (and failes) to parse a config file with multiple formats
> --------------------------------------------------------------------------------------
>
> Key: TAMAYA-198
> URL: https://issues.apache.org/jira/browse/TAMAYA-198
> Project: Tamaya
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 0.3-incubating
> Reporter: Thomas Liebetraut
> Assignee: Oliver B. Fischer
> Attachments: TAMAYA-198.patch
>
>
> BaseFormatPropertySourceProvider can handle multiple formats registered. This is useful in my project because we actually support multiple formats for a certain type of config file and this way we can implement one Provider which can provide PropertySources for all of them.
> But {{getPropertySources()}} will
> # blindly try all files with all formats. E.g. if both, "properties" and "ini" formats are registered, it will try all files with both formats without checking {{format.accepts()}} first.
> # try all the formats with the same {{InputStream}}. If the previous format does not reset the input stream, it is already at the end of the file and the following formats don't have anything left to read, returning {{null}}. This leads to some {{NullPointerException}}s being logged.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)