Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <559275826.1206991465746.JavaMail.jira@brutus>
Date: Mon, 31 Mar 2008 12:24:25 -0700 (PDT)
From: "David Felsenthal (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Commented: (CONFIGURATION-314) Allow custom separator
 characters when writing out PropertiesConfiguration
In-Reply-To: <1571403269.1204048731298.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CONFIGURATION-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583806#action_12583806 ] 

David Felsenthal commented on CONFIGURATION-314:
------------------------------------------------

As well as a custom separator on write, a custom separator on read is needed.

I have to deal with legacy non-standard ini files , with # in the text fields, not quoted or escaped.

I would have preferred to be able to override and extend  INIConfiguration, but could not. Instead, I too, had to copy and modify chunks of code.


> Allow custom separator characters when writing out PropertiesConfiguration
> --------------------------------------------------------------------------
>
>                 Key: CONFIGURATION-314
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-314
>             Project: Commons Configuration
>          Issue Type: Improvement
>    Affects Versions: 1.5
>            Reporter: Kenny MacLeod
>             Fix For: 1.6
>
>
> While PropertiesConfiguration is tolerant of several different key/value separator characters when reading a properties stream, it is hard-wired to use an "=" character when writing them out again.
> Can we please have a way to customise this?  Seems like a perfect use for the PropertiesConfigurationLayout.
> Sadly, because of the way that PropertiesWriter has been implemented, it's impossible to extend and override this behaviour without copying large chunks of code.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.