commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Narciso Oliveira Junior (JIRA)" <>
Subject [jira] Commented: (CONFIGURATION-239) setDelimiterParsingDisabled doesn't work for 'new PropertiesConfiguration(filePath)'
Date Thu, 30 Nov 2006 19:57:22 GMT
Narciso Oliveira Junior commented on CONFIGURATION-239:


Actually what I think needs to be done is to make the method setDelimiterParsingDisabled has
the same behavior if you create an object using the PropertiesConfiguration(filePath)  constructor
as it does for the constructor PropertiesConfiguration(). What do you think??

I don't know about the code, but I think when it loads the properties file, the code already
loads the properties once an then if you use the method setDelimiterParsingDisabled after
that , it doesn't affect anything....understand?? So if it is true It would be good to have
a warning in java doc for this situation.



> setDelimiterParsingDisabled doesn't work for 'new PropertiesConfiguration(filePath)'
> ------------------------------------------------------------------------------------
>                 Key: CONFIGURATION-239
>                 URL:
>             Project: Commons Configuration
>          Issue Type: Bug
>    Affects Versions: 1.3 Final
>         Environment: Win XP SP2, IBM Java 1.4.2.x
>            Reporter: Narciso Oliveira Junior
> Hi!
> just would like to report an issue I found with a new (and very helpful) improvement
on version 1.3 of commons configuration, the issue is that setDelimiterParsingDisabled method
doesn't work if first creates PropertiesConfiguration object using PropertiesConfiguration(filePath)
constructor. I needed to create the PropertiesConfiguration object using PropertiesConfiguration(),
use setDelimiterParsingDisabled(true) and then load the configration file using load(filePath)
> Please let me know if you need more details.
> thanks for all your work on this fabulous library...commons rocks!
> Narciso

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message