Re: Tomcat-as-a-reference implementation?

[Vince Bonfanti]

Yes, I'm concerned about this from the perspective of the vendor of a servlet/JSP engine that strives to faithfully implement the specs. My concern is that people will apply the following logic to non-spec features:       1. Tomcat is the Reference Implementation of servlets/JSP.     2. Tomcat implements Feature X.     3. Vendor Y's servlet engine doesn't implement Feature X, or implements it differently than Tomcat.     4. Therefore, Vendor Y's servlet engine isn't spec-compliant.   We saw this faulty logic applied to Java Web Server (JWS). Some people incorrectly believed that JWS was the reference implementation of servlets (some still do), and insisted that features such as the <SERVLET> tag, servlet chains, and response filters were part of the servlet spec (they're not). At least with JWS we could point to the JSDK and say, "No, the JSDK is the real reference implementation." With Tomcat there's a real danger of confusion.   Therefore, I would also like to see a clean separation between the servlet/JSP reference implementation, and the "commercial quality" servlet engine produced by the Apache group. Vince Bonfanti New Atlanta Communications, LLC -----Original Message----- From: A mailing list for discussion about Sun Microsystem's Java Servlet API Technology. [mailto:[EMAIL PROTECTED]] On Behalf Of Ted Neward Sent: Wednesday, February 16, 2000 1:38 AM To: [EMAIL PROTECTED] Subject: Tomcat-as-a-reference implementation? Does anybody else have a problem with a "production-quality" servlet engine also serving as the reference implementation for servlets and/or JSP?   I have always operated under the belief that a "reference implementation" was supposed to be plain-vanilla, no optimizations, stick-to-the-letter-of-the-spec, if-it-ain't-in-the-spec-it-ain't-in-here kind of implementation. JSWDK was precisely this--it demonstrated servlets simply, cleanly (IMHO), without a lot of bells-n-whistles to get in the way.   My concern is that Sun's stated intent (by calling it a reference implementation) is at cross-purposes with Apache's stated intent (to make it a production-quality engine). These are, for the most part, mutually-exclusive goals.   I applaud Sun's release of the JSWDK code to OpenSource, but does JSWDK, as a reference implementation, have to cede existence to Tomcat/JServ? Why not keep both? That is, have Tomcat use those parts of JSWDK-the-reference-imp where it sees a potential for reuse, and optimize those areas that need optimization?   Comments?   Ted Neward Java Instructor, DevelopMentor ( http://www.develop.com ) http://www.javageeks.com/~tneward