Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
From: "Mike Curwen" <g_dev9xq@globallyboundless.com>
To: "'Tomcat Users List'" <tomcat-user@jakarta.apache.org>
Subject: RE: custom error pages
Date: Thu, 5 Aug 2004 13:44:08 -0500
Message-ID: <00a801c47b1c$46a3b0d0$6f00000a@BALTHAZAR>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <9C5166762F311146951505C6790A9CF80229BDFE@US-VS1.corp.mpi.com>
Importance: Normal

I think the essence of the request is to get Tomcat to not show a tomcat
error page under any circumstances.  For those using Tomcat stand-alone,
(ie: they do not have the benefit of being able to use custom apache =
error
pages), is there a solution?

If you say that errorpages specified in web.xml are part of the web app, =
and
so are not available unless the app is available, would this be more
appropriately handled by a customized Connector? ie:=20

com.foo.my.Connector extends org.apache.coyote.tomcat4.CoyoteConnector
=20
and then I can set up customized pages for 404, 500, etc, etc ?


> -----Original Message-----
> From: Shapira, Yoav [mailto:Yoav.Shapira@mpi.com]=20
> Sent: Thursday, August 05, 2004 8:11 AM
> To: Tomcat Users List
> Subject: RE: custom error pages
>=20
>=20
>=20
> Hi,
> The stuff in conf/web.xml is virtually appended to your=20
> web.xml.  If your web.xml is inactive or non-existent the=20
> stuff in conf/web.xml is not applicable and not consulted.
>=20
>=20
> Yoav Shapira
> Millennium Research Informatics
>=20


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