The EL implementation that I would be rolling in was one I wrote for the JSP-EG/WebTier alignment and was licensed within Sun's Glassfish server and used within Sun's Facelets technology for JavaServer Faces. It's a complete depart from commons-el in implementation and optimized for expression serialization and some of the new EL-API concerns.
-- Jacob Bill Barker <[EMAIL PROTECTED]> wrote on 12/20/2005, 09:51:18 PM: > > > > -----Original Message----- > > From: Remy Maucherat [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, December 20, 2005 12:32 PM > > To: dev@tomcat.apache.org > > Subject: Tomcat 6 plans (JSP 2.1) > > > > Hi, > > > > Besides adding support for Servlet 2.5 which does not seem too > > overwhelming, most of the specification work is on support of > > JSP 2.1. I > > am happy to report that Jacob Hookom is willing to contribute code to > > add the necessary JSP support in Tomcat (he has done such an > > implementation already, and owns the copyright on that code). To host > > the code, a new branch is going to be needed for Jasper (as well as a > > new folder in servletapi). > > > > Does this mean that we'll be hosting EL? IMHO, resurrecting commons-el to > bring it up to JSP 2.1 was always going to be the hardest part of TC 6. > > I agree that the changes for Servlet 2.5 aren't that bad, but we might as > well branch Container while we are at it. > > > For testing the implementation, Jacob is going to need access > > to the JSP > > 2.1 TCK (I suppose he'll need to be a committer to do that, but it > > should be ok by then). > > > > We'll have to get access to the TCK ourselves first ;-). > > > Comments ? > > > > Rémy > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > This message is intended only for the use of the person(s) listed above as > the intended recipient(s), and may contain information that is PRIVILEGED and > CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, > or distribute this message or any attachment. If you received this > communication in error, please notify us immediately by e-mail and then > delete all copies of this message and any attachments. > > > > In addition you should be aware that ordinary (unencrypted) e-mail sent > through the Internet is not secure. Do not send confidential or sensitive > information, such as social security numbers, account numbers, personal > identification numbers and passwords, to us via ordinary (unencrypted) e-mail. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
