Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 93211 invoked by uid 500); 2 Oct 2001 02:50:05 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk Reply-To: tomcat-user@jakarta.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 93200 invoked from network); 2 Oct 2001 02:50:05 -0000 Date: Mon, 1 Oct 2001 19:48:08 -0700 (PDT) From: "Craig R. McClanahan" Sender: To: Subject: Re: Tomcat 4.0 specification compliance In-Reply-To: Message-ID: <20011001194622.B94105-100000@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: localhost 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Mon, 1 Oct 2001 ewright@vividsolutions.com wrote: > Date: Mon, 1 Oct 2001 15:28:44 -0700 > From: ewright@vividsolutions.com > Reply-To: tomcat-user@jakarta.apache.org > To: tomcat-user@jakarta.apache.org > Subject: Tomcat 4.0 specification compliance > > Hi There, > > How compliant is Tomcat 4.0 with the Servlet 2.3 and JSP 1.2 specifications? > If Tomcat 4 doesn't implement 100% of the "MUST" features in these specifications, that is a bug that needs to be fixed ASAP. Tomcat 4 is used as the web container portion of the J2EE 1.3 reference implementation, and it passes all the current spec compliance tests. Beyond the required features, Tomcat 4 implements a very large percentage of the optional features - details would depend on which particular feature you are interested in. Craig McClanahan