Bart Molenkamp wrote:
Ok, thanks,
But could you tell me why it catches only exceptions, and not errors?
(Just interested).
Because, quoting the Javadoc, "An Error is a subclass of Throwable that indicates serious problems that a reasonable application should not try to catch."
This has been discussed several times (dig the archives for "Throwable"), and IIRC the conclusion was that the only error that would make sense for Cocoon to catch is OutOfMemoryError.
Sylvain
-- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
