360 and 412 look like they might cause me some headaches. Are you -1 on
fixing them, or -0? That is, should I bother or not?
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Sunday, April 22, 2001 2:25 PM
To: [EMAIL PROTECTED]
Subject: Bugs <500
Hi,
I finished reviewing bugs marked as LATER with ID<500.
There are 5 bugs that we should fix for 3.3:
345 - Date header
348 - Security roles
375 - // security checking - revert to paranoid path checks
454 - mod_jk spawning (hunged ) apache processes when tomcat is down
( maybe later - tomcat should be running or be restart )
486 - rusian in jsp @include
There are 8 jasper bugs I think we should leave open, I wouldn't change
jasper before refactoring:
75 - translation time attrs
105 - custom tag attrs
143 - tag handlers
360 - jsp:include expressions
366 - doAfterBody if no body
376 - Jsp error messages in some cases ( no setter )
387 - special tokens in tag name ( extend to jsp files )
412 - JSPC and \ paths ( it may be easy to fix )
4 bugs are fixed in 3.3, we should close them:
149 - log, fixed
295 - config generation, fixed
296 - "can't happen", fixed
485 - cookies, fixed
Also, 4 bugs I don't think we'll cover in 3.3:
166 - spaces on nt ( has workarounds )
962 - redirect sys out, err; config in server.xml, rotate ( RFE )
471 - mod_jk and spaces in dir name on windows ( has workarounds )
112 - BAT script on windows - bin/ as default
Costin
<><><><><><><><><><><><><><><><><><><><><>This electronic mail transmission
may contain confidential information and is intended only for the person(s)
named. Any use, copying or disclosure by any other person is strictly
prohibited. If you have received this transmission in error, please notify
the sender via e-mail. <><><><><><><><><><><><><><><><><><><><><>
