Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 8652 invoked from network); 6 Dec 1999 00:02:39 -0000 Received: from prv-mail20.provo.novell.com (137.65.82.195) by apache.org with SMTP; 6 Dec 1999 00:02:39 -0000 Received: from INET-PRV-Message_Server by prv-mail20.provo.novell.com with Novell_GroupWise; Sun, 05 Dec 1999 17:02:10 -0700 Message-Id: X-Mailer: Novell GroupWise Internet Agent 5.5.2.1 Date: Sun, 05 Dec 1999 17:02:07 -0700 From: "Danno Ferrin" To: Subject: Jasper and Servlet 2.1 Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Is there any desire to make Jasper compatible with a 2.1 Servlet engine? The advantage with this is that Jasper can be dropped into an existing Servlet 2.1 Servlet Engine and replace or supplement the existing JSP Servlet in those engines which almost universally do not support Tag libraries, hence allowing tag libraries to be supported immediately on a wider range of platforms immediately.=20 Looking at the spec and grepping the jasper code I believe that there are only four lines that prevent 2.1 backward compatibility. All of these use HttpSession.getAttribute instead of HttpSession.getValue. Even though Servlet 2.2 deprecates the getValue group of methods they should still work properly in the 2.2 spec. Specifically the lines are : org/apache/jasper/runtime/pagecontextimpl.java:187: = return session.getAttribute(name); org/apache/jasper/runtime/pagecontextimpl.java:262: if (session.g= etAttribute(name) !=3D null) org/apache/jasper/runtime/pagecontextimpl.java:281: o =3D = session.getAttribute(name); org/apache/jasper/runtime/pagecontextimpl.java:300: = return session.getAttributeNames(); thanks, --Danno