Hi Kim,
That's great. I have few questions:
1. Have you submitted the patch to the Tomcat repository ? If so,
do you know in what version it will be released ?
2. Also, the encoding that you use is of the form %hh where 'hh' is an hex
value. I had the implression that for public classes, the .class file name
should match the file name. Don't you have a problem with that (since a
class name cannot contain '%') ?
3. In what part of the code did you made the change, was it in mangleChar()
method ?
Thanks
Tal
> -----Original Message-----
> From: Pilho Kim [mailto:[EMAIL PROTECTED]]
> Sent: 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,
> >
> > This is my first posting to this list so please bare with me.
> >
> > We are having problems with the jsp name mangling (bug 330 at
> > http://znutar.cortexity.com/BugRatViewer/ShowReport/330).
> >
> > Every '/' or '_' char in the jsp path is converted to 6 chars
> which easily
> > extend the file path beyond Win NT limitation of 256 chars. As
> a result, the
> > JSP compilation fails with the following error:
> >
> > org.apache.jasper.JasperException: Unable to compile class for JSPerror:
> > Can't write:
> >
> >
> D:\tomcat\appserv\work\localhost_8080\system\admin\modes\start\acc
> ount\_0002
> >
> fsystem_0002fadmin_0002fmodes_0002fstart_0002faccount_0002fpage_00
> 05fadmin_0
> >
> 005fstart_0005faccount_0005fpassword_0002ejsppage_0005fadmin_0005f
> start_0005
> > faccount_0005fpassword_jsp_0.class
> >
> > A quick look at the code reveals that the mangling is done by the method
> > CommandLineCompiler.mangleChar() so we plan to modify the
> method to generate
> > a more compact encoding, especially for common chars such as
> '/', '_', and
> > '.'.
> >
> > What is the view of the list regarding the proposed modification and how
> > should we proceed to maximize the changes that our patch will
> be included in
> > the official Tomcat code ?
> >
> > Thanks,
> >
> > Tal
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, email: [EMAIL PROTECTED]
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
