cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Wallez <>
Subject Re: [PROPOSAL] Extending Sitemap Error Handling
Date Wed, 10 Jul 2002 16:43:06 GMT
Piroumian Konstantin wrote:

>>From: Sylvain Wallez [] 
>>Nicola Ken Barozzi wrote:
>>>>>Other thoughts?
>Reading this thread and thinking: is it really needed in sitemap? 
>Why do not use the <error-page> element in web.xml and point it to a page
>that is handled by Cocoon?
>Additional data about the exception can be retrieved from special request
>attributes (see Servlet 2.3 Specification, Chapter 9.9).
>Won't this be enough for most of the cases?

Using <error-page> in web.xml means that <handle-errors> raises a 
servlet error and that the container calls the corresponding page.

IMO, this has several drawbacks :
- it hides the way errors are handled from the sitemap, which is the 
central location to define the site's behaviour,
- web.xml is applicable to the entire webapp context, meaning you cannot 
have different error response in different sitemaps.

Note also that this is currently not possible because of the implicit 
generator that is put in the pipeline by <handle-errors>. But it can be 
possible if we decide to make this generator explicit, meaning total 
control on the error-handling pipeline.

>>>Guess so, and because we are sooooo much verbooose and fast ;-)
>>Yes, and I'm sooooo late on my urgent paid-work because of this ;-)
>Not only writers, but the readers as well ;)

Ooops, sorry !


Sylvain Wallez
  Anyware Technologies                  Apache Cocoon 

To unsubscribe, e-mail:
For additional commands, email:

View raw message