Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Message-ID: <520288EA.4070904@apache.org>
Date: Wed, 07 Aug 2013 19:50:34 +0200
From: Mark Thomas <markt@apache.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8;
 rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: apache tomcat 8.0.0-rc1; /manager 404; NPE
References: 
 <CAArU9ibxfKWkA1hS-tENeDRwuJ3cw+QESMKGapGceJuY8RZbeg@mail.gmail.com>
 <520146D6.3030600@apache.org>
 <CAArU9ibuxNyUs6k2jAopZ2UO-6oGudyhNJmYHBLWR0bK6F6TyA@mail.gmail.com>
 <5201625E.6020701@apache.org>
 <CAArU9ibAG1u2LsHn81HaRRJLN=q4c9zMVMUzh34HP0uKfTUcrg@mail.gmail.com>
 <5201C041.7090803@christopherschultz.net>
 <CAArU9iaGwd-YamDqqvTVhY+pgAU4bXSRhXcCD3OCJvP3wXwc_Q@mail.gmail.com>
In-Reply-To: 
 <CAArU9iaGwd-YamDqqvTVhY+pgAU4bXSRhXcCD3OCJvP3wXwc_Q@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 07/08/2013 15:46, jieryn wrote:
> On Tue, Aug 6, 2013 at 11:34 PM, Christopher Schultz
> <chris@christopherschultz.net> wrote:
>> The servlet specification requires that certain services be provided
>> by the container. Among them are a) a default servlet to serve content
>> for which no other servlet mapping exists (e.g. static files, etc.)
>> and b) a servlet called "jsp" that is, by default, mapped to "*.jsp".
> 
> I was not aware of that requirement, thank you for the information.
> 
>> Tomcat chooses to provide the above services by using conf/web.xml as
>> a default. If you break that mechanism, you are going to lose some
>> functionality. The webapp should be able to rely on the default and
>> JSP servlets being available even without specifically configuring
>> them in the webapp's own web.xml.
> 
> There's actually no requirement for a web.xml for now two releases of
> the Servlet specification. How does the Apache Tomcat community feel
> about coding these core servlets with @WebServlet and let them be
> automatically discovered through the normal metadata-complete=false
> processing?

Work is in hand to move the JSP support to a ServletContainerInitializer
based configuration in Tomcat 8 onwards.

The other aspects of conf/web.xml could be moved to a similar approach
but there are associated knock-on effects in terms of increased start
times that mean it is unlikely to happen.

Mark


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