cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giacomo Pati <giac...@apache.org>
Subject Re: [PROPOSAL] Extending Sitemap Error Handling
Date Sun, 14 Jul 2002 11:31:13 GMT
On Wed, 10 Jul 2002, Michael Melhem wrote:

> > Currently, an implicit <map:generate type="!notifying-generator!"/> is
> > added as the first statement of <handle-errors> (see
> > HandleErrorsNode.invoke() in treeprocessor).
> >
> > What about making this explicit so we can choose other generators as
> > well, such as a standard file generator to display for example a nice
> > "page not found" page using some site-wide stylesheets ?
> >
> > <handle-errors>
> >  <match type="error" pattern="not-found">
> >    <generate type="file" src="notfound.xml"/>
> >    <transform src="skin/doc2html.xsl"/>
> >    <serialize/>
> >  </match>
> >  <!-- fallback -->
> >  <generate type="notifying"/>
> >  <transform src="system/error2html.xsl"/>
> >  <serialize/>
> > </handle-errors>
>
> I like the idea of an explicit generator in the handle-errors...but
> doesnt this open up the sitemap handle-errors block for abuse?

Oh god, this discussion is old as hell.

http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=96942814002458&w=2

> Wouldnt the ability to have custom handle-errors generators make it more
> likely that the handle-errors pipe would throw the very error/exception
> thats its trying to handle..and wouldnt this cause an infinate loop?

Giacomo


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message