have you tried using the resource exists action?
Geoff
> -----Original Message-----
> From: Ben Young [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 12, 2003 11:04 AM
> To: [EMAIL PROTECTED]
> Subject: Fault tolerance...
>
>
> In my current work with the aggregation option in Cocoon
> 2.0.4 it seems that
> the aggregation options are not very fault tolerant. If one of the
> map:part's of my map:aggregate section points to a file that
> does not exist,
> all map:part's after that one do not get returned even if
> their files exist.
>
> With a cinclude transformer the error is a bit worse. If the
> file requested
> does not exist in the pipeline, I get a NullPointerException
> from line 180
> in the CIncludeTransformer.java. That line contains the
> source.recycle()
> call. Since the source is never created, there is nothing to
> recycle. Hence
> the error. <breath/>
>
> Would it be possible to make the map:aggregate continue on
> it's merry way
> even if one of the map:part's doesn't resolve to anything?
>
> Would it also be possible to add some fault tolerance to the
> CincludeTransformer? It seems to that the cinclude's done using the
> cocoon:// protocol don't follow any map:redirect-to's. That's probably
> somewhat unrelated, but worth mentioning I guess. 8o)
>
> Thank you for your thoughts and time,
> Ben
>
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
>
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>
>
>
>
