Error-handling issue with complex sitemap

[footh <fo...@yahoo.com>]

I have a site map that calls a javaflow, then uses
multiple internal pipelines to aggregate content
together.  The problem is, when a resource that
doesn't exist is requested, a 404 error is not
generated.

The url of the requested resource is used to determine
the source of one of the pieces in the aggregation. 
However, if the source doesn't exist, a different type
of exception is returned (lands in the "otherwise"
block).  I believe a NullPointerException occurs.

Is there any way within an aggregation to capture a
404 error?



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

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