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

Oliver Heger resolved CONFIGURATION-238.
----------------------------------------

       Resolution: Won't Fix
    Fix Version/s: 1.4

Got no more feedback on this issue, so closing it. IMO there is nothing we can 
do about this because the underlying XML parser or the XSLT engine are handling 
this.

> XMLConfiguration.save() - illegal new line char in xml comment
> --------------------------------------------------------------
>
>                 Key: CONFIGURATION-238
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-238
>             Project: Commons Configuration
>          Issue Type: Bug
>    Affects Versions: 1.2
>         Environment: Windows XP x64
>            Reporter: Janusz Studzizba
>             Fix For: 1.4
>
>
> I have the following conf.xml.
> <?xml version="1.0" encoding="UTF-8"?>
> <report-server-config>
>     <!-- comment 
>    new line in comment -->
>     <param>value</param>
> </report-server-config>
> Edited with Vim looks nice.
> I use XMLConfiguration to process it.
> I perform the following operations:
>     XMLConfiguration config = new XMLConfiguration("c:\\conf.xml");
>     config.save();
> BUG:
> After config.save(); my conf.xml file, when edited in Vim, contains 
> additional ^M char at the end of each line. This is very disturbing.
> REASON:
> There must be a bug in XMLConfiguration when operating on <!-- --> xml 
> comments which contain new line characters - as in my example.
>     <!-- comment 
>    new line in comment -->
> My original conf.xml contained 0D 0A chars as a new line in comment,
> after calling config.save();  there is ONLY 0A char there!

-- 
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]

Reply via email to