Joe Hertz wrote:
> Because like I said before, as long as these deprecated methods are being
> used, Tomcat's javax.servlet.* implementation's days are numbers. The next
> JDK won't have these methods. Then it's game over. No compilation under the
> next JDK. If the spec hasn't changed, nor your
> Second, why require something stricter if we don't have to?
> Especially now, in what would be the 18th release of Tomcat 5.5,
> thereby causing pain those users who do run on JDK 1.3, just to get
> rid of some deprecation warnings that don't make any difference to
> anyone except you two apparen
>Second, why require something stricter if we don't have to?
>Especially now, in what would be the 18th release of Tomcat 5.5,
>thereby causing pain those users who do run on JDK 1.3, just to get
>rid of some deprecation warnings that don't make any difference to
>anyone except you two apparently?
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of Yoav Shapira
> Sent: Thursday, May 18, 2006 2:21 PM
> To: Tomcat Developers List
> Subject: Re: Deprecation Warnings in ServletRequestWrapper
>
> Hola,
> First, I read
Hola,
First, I read it as the container must be compile-able under J2SE 1.3,
so maybe we have a different understanding of minimum.
Second, why require something stricter if we don't have to?
Especially now, in what would be the 18th release of Tomcat 5.5,
thereby causing pain those users who do
