> > So, what you should volunteer to do if you are really
> interested, is to fix
> > Turbine to define a logging interface and then provide a log4j
> > implementation of that interface.
> >
> Or even better: define a logging service and write a log4j
> implementation. One
> item on my personal TODO list is a centralized logging
> facility for distributed
> Turbine apps, and a logging service would make this much easier.
> > -jon
> Christopher Elkins
Just imagine
((LogService)TurbineServices.getService("TurbineLogService")).error("ouch!");
that's lots of typing to log something. Maybe we should have a
static method in Turbine class that's wrapped around this
public class Turbine extends Servlet {
...
public static LogService log()
{
return (LogService)TurbineServices.getServices("TurbineLogService");
}
...
}
now, logging would look much neater:
Turbine.log().error("Ouch!");
and in the backend there's still a plugable implemetation layer.
just my 2c...
Rafal
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
