Sean Legassick wrote:
> So where should this stuff go? I'm inclined to think that the _proper_ way
> to do it is to have a service - ExceptionHandlerService with a default
> implementation that does what Turbine.handleException currently does and
> gets invoked by Turbine.handleException. Or does that seem like overkill
> for the task. The other option would be to have an interface and default
> implementation in org.apache.turbine.util (ExceptionHandler and
> DefaultExceptionHandler).
I don't recommend making this a service - when there is
something wrong with our service broker or the properties
file could not be loaded - the exception handler should
still work and send proper error messages in the browser/log.
On the other hand, if it's implemented as a service,
the default implemetnation could be instantiated directly
if the TurbineSerices fails to work. This is not very
clean but some sort of safeguard is neccesary.
Rafal
--
--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
