After the issues last night with Tomcat, I feel like trout-slapping anyone who even mentions clogging.
Just needed to get that off my chest - sorry for the noise. -- Jeremy Jim Marino wrote: > In the SCA Java runtime, we've implemented a logging approach where a > class that needs to perform logging requests a "monitor" that > implements a particular interface. This interface has methods for > logging that are strongly typed, i.e. "serverStartError(InitException > e)". The runtime is responsible for injecting either injecting a > concrete monitor instance or factory for creating them into the > requesting component. The concrete instance can choose which logging > framework to use. The runtime can be reconfigured to use a different > logging mechanism by changing the logging factory. > > This avoids many of the logging problems associated with things such as > commons logging (please don't use that one :-) ) > > Jim > > > On Apr 5, 2006, at 7:50 AM, Fuhwei Lwo wrote: > >> I couldn't find anywhere in the SDO 2.0 specification mentioning >> about the logging capability for error or trace. This is probably >> SDO implementation details but I think it's important to have some >> kind of logging capability in SDO 2.0 implementation. >> >> Any comments? >> >> Fuhwei >> >
