On 14 April 2011 01:10, Justin Randall wrote:
>
> Hi Chris,
>
>> Of course. I was wondering about other exceptions or errors that maybe I
>> cannot control from that code.
>
> Are you referring to internal exceptions within Tomcat's own code or simply
> unexpected exceptions within the servlet's
Chris,
--- On Wed, 4/13/11 at 1:11 PM, Christopher Schultz
wrote:
> Basically, I want two defaults.
>
> If the servlet spec allowed for to
> include a
> filter, that's what I would use. But it doesn't :(
>
Would an Exception marker interface help to differentiate Servlet and other
Excepti
.
Regards,
Justin Randall
Sent from my BlackBerry device
-Original Message-
From: Martin Gainty
Date: Wed, 13 Apr 2011 21:47:51
To: Tomcat Users List
Reply-To: "Tomcat Users List"
Subject: RE: [OT] servlet-specific error pages
in web.xml for your webapp
map a custom jsp for each ret
accepter aucune responsabilité
pour le contenu fourni.
> From: ran...@hotmail.com
> To: users@tomcat.apache.org
> Subject: RE: [OT] servlet-specific error pages
> Date: Wed, 13 Apr 2011 20:10:48 -0400
>
>
> Hi Chris,
>
> > Of course. I was wondering about other ex
programming mistakes as an example.
Regards,
Justin Randall
> Date: Wed, 13 Apr 2011 16:11:09 -0400
> From: ch...@christopherschultz.net
> To: users@tomcat.apache.org
> Subject: Re: [OT] servlet-specific error pages
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Justin,
On 4/13/2011 9:17 AM, Justin Randall wrote:
> Hi Chris,
>
> I'm assuming the servlet is in control of generating all of the
> errors you are implying?
Yes and no:
> For example, if the servlet doesn't load properly and a 404 would be
> gene
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
János,
On 4/13/2011 11:37 AM, János Löbb wrote:
> I was thinking about this section in the FM 10.9.2:
>
> Error-page declarations using the exception-type element in
> the deployment descriptor must be unique up to the class name of the
> exception-
Chris,
I was thinking about this section in the FM 10.9.2:
Error-page declarations using the exception-type element in the deployment
descriptor must be unique up to the class name of the exception-type.
Similarly, error-page declarations using the status-code element must be unique
in the de
chema associated with it but that's just for
brevity of the example.
I hope this helps!
Justin Randall
> Date: Tue, 12 Apr 2011 16:38:25 -0400
> From: ch...@christopherschultz.net
> To: users@tomcat.apache.org
> Subject: [OT] servlet-specific error pages
>
> -BEGIN
On Wed, Apr 13, 2011 at 00:17, Christopher Schultz
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> János,
>
> On 4/12/2011 4:56 PM, János Löbb wrote:
>> Look the 10.9 Error Handling in the 3.0 specifications. It is maya
>> to me but you might find what you are looking for.
>
> Being
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
János,
On 4/12/2011 4:56 PM, János Löbb wrote:
> Look the 10.9 Error Handling in the 3.0 specifications. It is maya
> to me but you might find what you are looking for.
Being somewhat familiar with the servlet specification, I was hoping for
somethi
On Apr 12, 2011, at 4:38 PM, Christopher Schultz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> All,
>
> I have a webapp where some of the servlets are expected to return XML
> all the time, even for error conditions. I'd like to be able to set an
> error page for those servlets s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
I have a webapp where some of the servlets are expected to return XML
all the time, even for error conditions. I'd like to be able to set an
error page for those servlets so the response will be in XML instead of
HTML like you'd get with the defa
13 matches
Mail list logo
