You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2004/03/22 17:35:01 UTC
DO NOT REPLY [Bug 27775] -
[configuration] Comma-escaping and backslash-parsing in PropertiesConfiguration broken
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=27775>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=27775
[configuration] Comma-escaping and backslash-parsing in PropertiesConfiguration broken
christian@siefkes.net changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[configuration] Comma- |[configuration] Comma-
|escaping in |escaping and backslash-
|PropertiesConfiguration |parsing in
|broken |PropertiesConfiguration
| |broken
------- Additional Comments From christian@siefkes.net 2004-03-22 16:35 -------
Actually, things are worse: looks like *every* single backslash in a properties
file is silently ignored and you always need to write two backslashes in the
file to get a single backslash in the parsed property.
E.g. when adding these properties to the properties file:
test.prob = pro\perty
test.prob2 = pro\\perty
// returns "property" instead of "pro\perty"
System.out.println(pc.getString("test.prob"));
// returns "pro\perty"
System.out.println(pc.getString("test.prob2"));
This breaks the old behavior where you would get "pro\perty" in the first case.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org