Berin Loritsch wrote:
>
>>-----Original Message-----
>>From: Berin Loritsch [mailto:[EMAIL PROTECTED]]
>>Sent: Wednesday, July 17, 2002 11:05 AM
>>To: Avalon Developer's List
>>Subject: Simplifying Error Reporting (FW: doc generation woes)
>>
>>
>>Enclosed below is a message we received from Stephen McConnel
>>regarding the Avalon doc generation. The problem isn't so
>>much that Cocoon couldn't get working but that he had to sift
>>through mountains of stacktraces.
>>
>>To that end, I suggest we look at a smarter way of dealing
>>with errors. There are certain types of errors that are
>>common enough to really be simplified. Also, there are a
>>number of exceptions in the log files that seem to have no
>>real affect on Cocoon's ability to output the proper result.
>>
>>My suggestion is this:
>>
>>1. Identify common potential errors, following is a short list:
>> * Bad markup (XML document malformed)
>> * Resource not available
Yes.
>>2. Provide a really simple message WITHOUT a stacktrace for
>>these types
>> of errors. It is more helpful to know that "index.xml" is not well
>> formed than it is to know exactly which line of code the
>>error occurred.
>> Same with the fact that "index.xml" might not exist.
This has been discussed very recently, and in fact I thought I had
already removed the stacktrace from RNF errors except in DEBUG mode...
>>3. Stop using exceptions to control program flow. We need
>>another mechanism
>> for that.
>>
>>Stack traces in the log files and printed to the screen
>>should document real exceptions. They should represent
>>things that Cocoon *really* did not expect, or cannot handle
>>gracefully.
I think that the best thing is to put hands in Main and such, ie the
commandline stuff.
Lokking it now...
--
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]
