On Sat, Feb 24, 2001 at 01:51:52PM +0100, Rafal Krzewski wrote:
> Sam Ruby wrote:
>
> > Either:
> >
> > 1) We need to make the abstraction for logging independent of Turbine and a
> > Jakarta "standard".
>
> Logging system needs some means of configuration. If we deteach it from
> Turbine, it will need a separate config file, and some way of finding
> it.
> In servlet env, this probably means accessing ServletContext... I don't
> see a clean way of dealing with that.
Well if reusable components just have a pluggable standard logging
interface, then it can be up to the provider of the logging interface
(i.e. the application) to deal with configuration of the logging system.
So in our case we just write a wrapper around the LoggingService which
gets plugged into the connection pool as a default, but non-Turbine
users of the connection pool can plug in their own implementation of the
same interface.
Avalon's logging framework may be a candidate for this standard logging
interface... I haven't looked at it, so I don't know.
--
Sean Legassick
[EMAIL PROTECTED]
Ek is 'n man: niks menslik is vreemd vir my nie
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
