Manik Surtani
> Sent: Thursday, April 06, 2006 10:33 PM
> To: jboss-development@lists.sourceforge.net
> Cc: [EMAIL PROTECTED]
> Subject: Re: [JBoss-dev] JBossCache 1.3.0.GA released + a
> change to how we deal with java.util.properties
>
> Escaping single backslashes is probably not a
AIK.
-Ben
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Manik Surtani
Sent: Thursday, April 06, 2006 10:33 PM
To: jboss-development@lists.sourceforge.net
Cc: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] JBossCache 1.3.0.GA released + a change to how we
Escaping single backslashes is probably not a good idea. What if I
want to pass in (for some obscure reason) a \n ? I'd expect this to
be translated to a new line, not the string "\\n".
I think we just mandate that users passing in backslashes as a part
of a path construct use double-back
It turns out that the root cause behind JBCACHE-531 is deeper than I
thought.
After fixing a minor international character support issue in
org.jboss.cache.config.CacheLoaderConfig (we were calling
String.getBytes() without specifying an encoding). I then came across
the same issue in
org.jboss.u
