On Tue, Aug 6, 2013 at 11:34 PM, Christopher Schultz
ch...@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,
From: jieryn [mailto:jie...@gmail.com]
Subject: Re: apache tomcat 8.0.0-rc1; /manager 404; NPE
so what is the point of keeping the global conf/web.xml..
To allow Tomcat to work. If we changed the name to conf/do_not_delete.xml,
would that satisfy you?
- Chuck
THIS COMMUNICATION MAY
Greetings,
On Wed, Aug 7, 2013 at 9:58 AM, Caldarale, Charles R
chuck.caldar...@unisys.com wrote:
To allow Tomcat to work. If we changed the name to conf/do_not_delete.xml,
would that satisfy you?
I think you've quite severely missed the point of the entire
discussion which I've raised.
On 07/08/2013 15:46, jieryn wrote:
On Tue, Aug 6, 2013 at 11:34 PM, Christopher Schultz
ch...@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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jieryn,
On 8/7/13 10:02 AM, jieryn wrote:
Greetings,
On Wed, Aug 7, 2013 at 9:58 AM, Caldarale, Charles R
chuck.caldar...@unisys.com wrote:
To allow Tomcat to work. If we changed the name to
conf/do_not_delete.xml, would that satisfy you?
When I try to hit the /manager application from a browser without
specifying /html, the following NPE ends up in the log, but the
browser sees what appears to be a typical tomcat 404 error page
without exposing the full trace:
== logs/access_log.2013-08-06 ==
a.b.c.d - - [06/Aug/2013:14:37:52
On 06/08/2013 20:46, jieryn wrote:
When I try to hit the /manager application from a browser without
specifying /html, the following NPE ends up in the log, but the
browser sees what appears to be a typical tomcat 404 error page
without exposing the full trace:
I can't repeat this with a
Greetings,
On Tue, Aug 6, 2013 at 2:56 PM, Mark Thomas ma...@apache.org wrote:
On 06/08/2013 20:46, jieryn wrote:
When I try to hit the /manager application from a browser without
specifying /html, the following NPE ends up in the log, but the
browser sees what appears to be a typical tomcat
On 06/08/2013 21:53, jieryn wrote:
Greetings,
On Tue, Aug 6, 2013 at 2:56 PM, Mark Thomas ma...@apache.org wrote:
On 06/08/2013 20:46, jieryn wrote:
When I try to hit the /manager application from a browser without
specifying /html, the following NPE ends up in the log, but the
browser
Greetings,
On Tue, Aug 6, 2013 at 4:53 PM, Mark Thomas ma...@apache.org wrote:
The Tomcat 7.0.x behaviour is identical to Tomcat 8.0.x.
The root cause of the stack trace in both versions is the missing
configuration for the JSP servlet.
Ok, since the manager application already provides a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jieryn,
On 8/6/13 10:00 PM, jieryn wrote:
Greetings,
On Tue, Aug 6, 2013 at 4:53 PM, Mark Thomas ma...@apache.org
wrote:
The Tomcat 7.0.x behaviour is identical to Tomcat 8.0.x. The root
cause of the stack trace in both versions is the
11 matches
Mail list logo