cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mratl...@collegenet.com
Subject Re: [RT] Cocoon Exception Handling Infrastructure
Date Tue, 21 May 2002 06:52:48 GMT

All,

> 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 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.

Users perspective:  Cocoon stack traces are intimidating, and sometimes useless.
Searching
through log files is more helpful, but sometimes Cocoon just dumps its errors
into
the browser window and there is nothing in the log files (or maybe I just can't
find it).

Components (like Transformers) that don't report enough information to locate
simple
syntax errors are especially frustrating.  I use incremental development
approach:  change
as few lines as possible, then retest. If I get a null ponter error resulting
from a simple typo,
I can at least home in on the error.

--Michael


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message