[
https://issues.apache.org/jira/browse/CONFIGURATION-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494703
]
Emmanuel Bourg commented on CONFIGURATION-268:
----------------------------------------------
That looks a bit weird to introduce a secondary list delimiter to disable the
primary list delimiter. Why not letting the user change the delimiter himself ?
We might add a note in the javadoc suggesting that
setDelimiterParsingDisabled(true) is not recommended if list properties are
used in attributes, and that changing the list delimiter to an untypical
character is preferred.
> XMLConfiguration does not fully support disabled delimiter parsing
> ------------------------------------------------------------------
>
> Key: CONFIGURATION-268
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-268
> Project: Commons Configuration
> Issue Type: Bug
> Affects Versions: 1.4
> Reporter: Oliver Heger
> Assigned To: Oliver Heger
> Fix For: 1.5
>
>
> A call to setDelimiterParsingDisabled(true) should completely turn off the
> mechanism for searching for list delimiters and splitting property values.
> However XMLConfiguration.save() escapes list delimiters even in this mode.
> When later such a configuration file is loaded and delimiter parsing is
> turned off, the values of affected properties will contain the escape
> character.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
