The problem with Exceptions is how programmers use them, not if they are checked or not.
Our problem is that we log, wrap, hide, and rethrow exceptions without need, and this is very bad. But this has nothing to do with checked-unchecked, just about how they are handled.
Let's not make all the same thing and decide what we are talking about. I'd focus on discussing the exceptions that the Cocoon components/blocks can throw. They should throw only what the caller can deal with, not more, not less. Now, diggin in the container and it's contracts, one can see what the container should do and what the component should do: the exception(s) that the components can throw will be part of this contract.
Just remember that in defining this contract, usual Java exceptions should be used, ie an IOException for I/O errors, not generic "cocoon" exceptions that don't mean anything.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------