cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven D. Majewski" <sd...@virginia.edu>
Subject Re: Forcing error in sitemap
Date Fri, 11 Aug 2006 22:39:27 GMT
Well: how about just throwing an error from flowscript ?

( or from java. The problem with flowscript is that the sitemap uses  
java exceptions,
   and I think all of the rhino exceptions are going to get mapped  
into JavaScriptException's
   in java. )

-- Steve Majewski


On Aug 11, 2006, at 6:24 PM, footh wrote:

>
> The problem, this sitemap snippet is three deep in the
> chain.  The first pipeline calls the javaflow which
> forwards to the second pipeline which contains an
> "aggregation" tag that aggregrates the header,
> sidebars, and main content into one big xml page.
> Each of these is a separate internal pipeline.  It's
> the "main content" internal pipeline that bombs on a
> bad URL (the header and sidebar content is always in
> the same spot regardless of the URL).
>
> So, if I serialize with 404 error, nothing happens
> (had already tried this) because this pipeline is only
> one piece of the eventual response.  That's why I need
> to "force" the error so the handle-errors block deals
> with it.


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


Mime
View raw message