In any case, what I see is that Cocoon has gotten many contracts wrong. In particular it has been coded using generic Cocoonish exceptions that were meant to gobble up the source exceptions from the start. In fact we can say that what seems now as an error was deemed in the beginning as a feature, that was probably done to achieve that RuntimeExceptions do rather than to have what we have now.
I would like to note BTW that my -1 is a vote, not a veto. It is based on the fact that I don't believe that using RuntimeExceptions will bring us that cleaness we need without unwanted consequences, but this is just MHO and I may well again be wrong, as it happens :-)
Same here. The change to RuntimeExceptions only circumvents the inherent problem of Cocoon.
Joerg
