|
From: Stefan K. <ste...@co...> - 2003-06-24 18:03:40
|
The service/config approach is the right way. The "method override" would
only work for all self-developed stages and not for the babeldoc standard
stages. So, this won't really help us. I haven't recognized this fact
earlier.
Stefan
----- Original Message -----
From: "Dejan Krsmanovic" <dej...@nb...>
To: <bab...@li...>
Sent: Tuesday, June 24, 2003 8:49 AM
Subject: Re: [Babeldoc-devel] Making PipelineStage.getErrorHandler()
protected
> Maybe better idea is using service/config.properties file. We could add
new
> property with name defaultErrorHandler and value of the class wich should
> be used as default error handler... By default this value should be
> com.babeldoc.core.pipeline.DefaultPipelineStageErrorHandler but you you
> could put whatever value you want...
>
> That way you don't need to change code...
>
> We could also made getErrorHandler protected so it can be overiden. I
guess
> it became private during refactoring, that is - Eclipse made it private
not
> me! ;)
>
> Note that you could also use errorStage property to change processing
order
> in case of exceptions. So you can route to SmtpWriter in case of
> exceptions...
>
> What do you think, which solution is best for you?
>
> Dejan
>
>
>
>
> ----- Original Message -----
> From: "Stefan Krieger" <ste...@co...>
> To: <bab...@li...>
> Sent: Monday, June 23, 2003 10:51 PM
> Subject: [Babeldoc-devel] Making PipelineStage.getErrorHandler() protected
>
>
> > Hello,
> >
> > We am using babeldoc in a document transformation project in a J2EE
> > environment.
> > We would like to send eMails in case of exceptions during PipelineStage
> > processing. This should be the default ErrorHandler for all
PipelineStages
> > we are running. Unfortunately, the method getErrorHandler() in
> PipelineStage
> > is private. So, we are forced to configure our ErrorHandler for alle
> > PipelineStages otherwise DefaultPipelineStageErrorHandler is always
> > returned. Can you make this method "protected" ?
> > Or, even better: provide a factory method for the DefaultErrorHandler:
> >
> > protected IPipelineStageErrorHandler createDefaultErrorHandler() {
return
> > new DefaultPipelineStageErrorHandler() ; }
> >
> > Then we can reuse the configuration part in getErrorHandler().
> >
> > Thanks,
> > Stefan
> >
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: INetU
> > Attention Web Developers & Consultants: Become An INetU Hosting Partner.
> > Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
> > INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> > _______________________________________________
> > Babeldoc-devel mailing list
> > Bab...@li...
> > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
> INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> _______________________________________________
> Babeldoc-devel mailing list
> Bab...@li...
> https://lists.sourceforge.net/lists/listinfo/babeldoc-devel
>
|