Actually, I think I found a solution...by not even
trying.
Before, I was trying different things in the
"otherwise" block. But then I just left it blank and
forgot about it. Then, I mistakenly went to a bad URL
and the 404 error showed up!
So, basically, if a pipeline doesn't return anything,
I
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:
Thanks for the reply.
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 se
You can generate the 404 error by specifying a status-code for
serialize:
But you'll also need some sort of dummy/error document to be serialized.
Or (I think) you can do a cocoon.sendStatus( 404 ) from flowscript.
But I thought that the error handler would only catch exceptions.
Thi
I have a sitemap that first goes through a javaflow,
then is forwarded to an aggregation of several
different pieces.
One of those pieces is the main content. If a URL is
requested that doesn't exist, grabbing the main
content will cause a null error in the pipeline (but
since it "matches" a pipe
