cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Torsten Curdt <>
Subject Re: [RT] Cocoon Exception Handling Infrastructure
Date Tue, 21 May 2002 07:47:43 GMT
> XSLT Transformer is obviously one of the most popular Cocoon components.
> As such it carries the extra burden of serving as example to people writing
> other components.
> In the sake of fairness, exception reporting is much friendlier in 2.1 than
> before. However much remains to be improved.
> I was wondering if someone else shares my observations and thinks it's time
> to lay out a design for better exception reporting infrastructure.

I just stumbled over the same thing... see

...altough this was a more technical issue - unfortunately noone responded :-(

I think we should really make sure there is really a single of point of 
failure where the exceptions bubble up and where it is defined if they are 
presented to the user or not. (This should be configurable since error 
reporting can also be security issue when it comes to deployment)

To have a more useful output than just a stacktrace I have modified the 
LanguageException to present the error part of an failed XSP compilation to 
the user as you (might have noticed). Of course this is only useful for 
developement but it should lower the barrier for newbies...

> I think that one of the biggest psychological barriers for Cocoon users is
> that they can't easily start writing simple apps. Cocoon is not very
> forgiving with bad input, while at the same time its exception reporting is
> often misleading the developer instead of pinpointing the problem.


To unsubscribe, e-mail:
For additional commands, email:

View raw message