Ben Young <[EMAIL PROTECTED]> writes: > 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?
I would prefer a slightly different behavior. The CIncludeTranformer could add a short error message in XML, so the next transformer could either remove the error message or transform it to a user friendly form. Martin -- Martin Holz <[EMAIL PROTECTED]> Softwareentwicklung / Vernetztes Studium - Chemie FIZ CHEMIE Berlin Franklinstrasse 11 D-10587 Berlin --------------------------------------------------------------------- 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]>
