Cocoon is one the most awesome tools out there - my compliments to
everyone! Congratulations on the 2.0.1 release!
I've been using it since 1.3, and now that I've really been able to
dive into 2.0, it is awesome to see the massive, grand vision and promise
Stefano and others put forth now running as a product. I love it! you all
make MY job SOO much easier...I hope to be able to arrange to contribute at
some point as well.
However, I finally found a (minor) criticism of Cocoon 2 - error
reporting. I haven't hit one that I haven't gotten past, however most of the
time when I get the error page, it has so little meaningful informaiton, it
is the equivalent of telling me "Something went wrong somewhere, and it
probably had to do with XML"
Maybe it is just me, but I would love it if the page instead said
perhaps, which pipeline compoenent threw the exception, and maybe even
proivded some SAX stream context for the point at which it died. Maybe this
is there and I just haven't flipped the right switch...but it would save me
a lot of time, and I am sure I am not alone.
Thanks!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
