Re: [Babeldoc-devel] PipelineStageFactory

[Dejan K. <dej...@nb...>]

I agree with you that these two methods should throw exceptions. These =
are serious problems and exception should not be discarded. If you =
asking me, feel free to implement this.=20

Dejan

----- Original Message -----=20
  From: ek...@ba...=20
  To: bab...@li...=20
  Sent: Tuesday, April 22, 2003 3:48 PM
  Subject: Re: [Babeldoc-devel] PipelineStageFactory



  <<=20
  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().
  >>=20

  Here is the call stack as I can trace it:=20

  PipelineFeeder.process( ) throws PipelineException, JournalException=20
          PipelineFactoryFactory.process( ) throws PipelineException=20
                  PipelineFactory.process( ) throws PipelineException=20
                          PipelineStageFactory.process( ) **which throws =
nothing**=20

  PipelineStageFactory.process( ) calls the following methods, which =
discard the exceptions they catch:=20
  -- getPipelineStage=20
  -- trackDocument=20

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

  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??"=20

  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?=20

  Erik=20
  =
________________________________________________________________________
  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.