cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicola Ken Barozzi" <baro...@nicolaken.com>
Subject Re: I finally found one....
Date Thu, 31 Jan 2002 13:43:36 GMT
From: "Lewis, Andrew J" <Andrew.Lewis@jbosc.ksc.nasa.gov>

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

You are completely right.
Some progress has been done in this release although not yet properly
documented (my fault :-/ ) to fix this thing.
A lot still needs to be done. For this I sent this mail to the users list:

<mail>
  <header>
----- Original Message -----
From: "Nicola Ken Barozzi" <barozzi@nicolaken.com>
To: <cocoon-users@xml.apache.org>
Sent: Wednesday, January 30, 2002 6:37 PM
Subject: Let's make error notification be correct and helpful
  </header>


> Some work has been done to make errors from Cocoon be more helpful for the
> programmer, but more has to be done.
>
> Since I see that many errors are still undescriptive of the real cause of
> the error, we need to track them down one by one.
> Please send errors that you think are not descriptive enough or plainly
> wrong to Bugzilla (http://nagoya.apache.org/bugzilla/) and starting the
> "Summary" line with [STRANGE-ERROR]. Please add as "Attachments" all
> relevant sitemap snippets and files, along with an indication of how to
> reproduce the error. All these are automatically reported to developers by
> Bugzilla.
> My goal is to kill these bugs at most for 2.1 release.
</mail>

> Maybe it is just me, but I would love it if the page instead said
> perhaps, which pipeline compoenent threw the exception,

It does/should do it. The new error reporting reports the class that
notified the exception and the class that threw it.
It contains also the full original stacktrace of the original error.

> and maybe even
> proivded some SAX stream context for the point at which it died.

This is in the output before the notification content. You can look at the
source of the page, it should be there.

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

The main infrastructure is there, we just need to ensure that errors are
rethrown correctly, that means using cascading exceptions in wrapping. But
this needs to be done for every component, hence my request to specific
indications.

Thank you.

--
Nicola Ken Barozzi                 xml-cocoon@nicolaken.com
These are the days of miracle and wonder...
          ...so don't cry baby, don't cry...
                                                  Paul Simon


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


Mime
View raw message