Vadim Gritsenko wrote:
> Nicola Ken Barozzi wrote:
> ...snip...
>
>> No developer in Cocoon except
>
> ... every day you learn something new ... apparently, I was not *really*
> interested in error reporting.
Oops ...
IIRC it's the second time I write this and the second time you correct
me, it's becoming a ritual! ;-)
>> me and Sylvain really has ever been interested in error reporting.
>> It became my first itch with Cocoon, since with 1.0 you never knew how
>> the installation had failed.
>>
>> I did my best, and it worked, but things inside Cocoon keep breaking it.
>
> ... snip ...
>
>> -oOo-
>>
>> Also, Cocoon.java error handling is currently undefined.
>> When it encounters a problem, it sometimes returns null, sometimes go
>> silent, and sometimes throw an error.
>>
>> What should it do in case it doesn't use a <handle-errors>?
>
>
>
> Another issue is "double exception": when handle-errors fails, what
> exception should be reported?
Hmmm... if Cocoon has access to the Context, it can report the
handle-exceptions one and include also the other when rethrowing.
It should throw a CocoonException, that is Notifying.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
