PROTECTED]'
Subject: RE: Proposed name encoding patch
I was looking at this last night, by coincidence. It seems to me that the
class
name is encoding too much information. It's duplicating the
package as part
of
the class name. I suspect it's getting confused between
I was looking at this last night, by coincidence. It seems to me that the
class
name is encoding too much information. It's duplicating the package as part
of
the class name. I suspect it's getting confused between '/', '\',
File.separatorChar, etc.
It's also encoding characters that are legal
, 2001 11:40 AM
To: [EMAIL PROTECTED]
Subject: Re: Proposed name encoding patch
It's worth to mention that both JSP encoding and work dir encoding are
resolved/improved in 3.3 - and the code can be easily ported back /
reused.
I'll take a look at both patches and try to integrate them into 3.3
: Tuesday, January 16, 2001 11:06 AM
To: [EMAIL PROTECTED]
Subject: Re: Proposed name encoding patch
Hi, Tal
I have ever solved the problem already.
Try to check
http://w4.metronet.com/~wjm/tomcat/2000/Aug/msg00595.html
Thanks,
Kim
On Tue, 16 Jan 2001, Tal Dayan wrote:
Hello
It's worth to mention that both JSP encoding and work dir encoding are
resolved/improved in 3.3 - and the code can be easily ported back /
reused.
I'll take a look at both patches and try to integrate them into 3.3 also (
what is not covered already )
--
Costin
