|
From: Bruce M. <br...@mc...> - 2003-04-22 13:52:21
|
It can be explained by not having your set of requirements at the time of writing. You will probably need to implement the changes you need yourself. On Tuesday 22 April 2003 09:48 am, ek...@ba... wrote: > << > Then probably process method of PipelineStageFactory should throw > exception, right? I guess it is not enough if you use another > PipelineStageErrorHandler since it is used only for handling errors that > occurs in PipelineStage.process(). > > > Here is the call stack as I can trace it: > > PipelineFeeder.process( ) throws PipelineException, JournalException > PipelineFactoryFactory.process( ) throws PipelineException > PipelineFactory.process( ) throws PipelineException > PipelineStageFactory.process( ) **which throws > nothing** > > PipelineStageFactory.process( ) calls the following methods, which discard > the exceptions they catch: > -- getPipelineStage > -- trackDocument > > As I looked at the programs above, I found more examples of exceptions > being caught and then either being discarded or having Error Log messages > generated. > > I guess the question I have is: "If something is important enough to cause > an exception to be thrown, why is it so frequently sufficient to discard > the exception or replace it with a logged error message??" > > I am going to search for more examples of this ... the production system I > implement cannot afford to have low-level exceptions discarded and I will > not be writing log-scanning software to search for errors in logs when it > could just as easily be identified by a thrown exception. Can anyone > explain this? > > Erik > > ________________________________________________________________________ > The information in this e-mail, and any attachment therein, is confidential > and for use by the addressee only. If you are not the intended recipient, > please return the e-mail to the sender and delete it from your computer. > Although The Bank of New York attempts to sweep e-mail and attachments for > viruses, it does not guarantee that either are virus-free and accepts no > liability for any damage sustained as a result of viruses. |