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

Amitabh Pandey commented on CONFIGURATION-700:
----------------------------------------------

Can you share the output which you have generated. Can we not avoid the 
escaping as you have mentioned also.

I assume that you are talking about common configuration version 2.2.

I just let you know that this property file will be used by some other 
application. That's why i don't want any change in any other tag with escaping. 
This property file belongs to that system and all the values which are inside 
used by them. So it would not work if any this will be changed in escaping 
character.

> Issue With backslash(\) and Forwardslash(/)
> -------------------------------------------
>
>                 Key: CONFIGURATION-700
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-700
>             Project: Commons Configuration
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 1.10
>            Reporter: Amitabh Pandey
>            Priority: Major
>             Fix For: 1.10
>
>         Attachments: Getting Output.jpg, Original Property File Contenet.jpg
>
>
> Dear Team,
> I am using commons-configuration-1.10.jar for updating property file in java.
> I have achieve all my requirement(Preserve comment, White space) with this 
> API.But stuck at one point.It is not working as per my expectations with 
> slash.Below is one example.
> I have below url in my properties file.
> *C\:ABC.net/wsdl*
> Now it is getting change to below after modification
> *C:ABC.net\/wsdl*
> Means it is removing the backslash and changing forwardslash to \/.I know it 
> is escaping character. But is there any way to prevent this. I cant not 
> change any thing in property file. I have to handle through code only. 
> Because of only this issue I again moved to Java util API.
> Please check fix of this. Rest is excellent.



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

Reply via email to