Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of jhertz@speakeasy.net designates
 69.17.117.49 as permitted sender)
From: "Joe Hertz" <jhertz@speakeasy.net>
To: dev@tomcat.apache.org
Importance: Normal
Sensitivity: Normal
Message-ID: <W9066327186149381147991085@webmail2>
Date: Thu, 18 May 2006 22:24:45 +0000
Subject: RE: Deprecation Warnings in ServletRequestWrapper
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

> 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?
>
>And, more to the point, the deprecated methods are still part of the 2.5=

>spec :), and so still must be included.  What would be possible in TC 6 =
is
>to do:
>   @SuppressWarnings("deprecation")
>   public void setStatus(int sc, String sm) { ...
>
>This would at least allow compiling the servlet-api without deprecation
>warnings.  Of course, you are free to annotate your own classes anyway y=
ou
>want :).

Interesting you point that out, as comments in the bug claims it's being =
fixed in TC 6. 

If the logic is, "We didn't read the spec right and then we ignored the b=
ug when it was first reported too, and in the time since we have acquired=
 users everywhere who are now dependent on our error", there are two opti=
ons.

1) Fix it, tell the 1.3 JDK people they got lucky to have support this fa=
r.

2) Mark the bug WONTFIX, not INVALID. You take your chances with the next=
 JDK.

Because like I said before, as long as these deprecated methods are being=
 used, Tomcat's javax.servlet.* implementation's days are numbers. The ne=
xt JDK won't have these methods. Then it's game over. No compilation unde=
r the next JDK. If the spec hasn't changed, nor your interpretation of it=
, then it's no left-turn, no right-turn, whaddyadoo..

So are you guys _REALLY_ sure this is what the spec is saying with regard=
 to JDK 1.3 support?

-Joe


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org