On Mon, Aug 25, 2008 at 3:39 AM, Julien Vermillard
<[EMAIL PROTECTED]>wrote:

> LoggingFilter is a debug tool, in no production application you will
> log all the sent/rcvd message.
>
> The only usage could be exception & connec/disconnet
>
> So I think we could :
>
> hardcode created/sent/rcvd log level to trace/debug which is always
> used for debug
>
> hardcode close/connect to info
>
> hardcode exception to error
>
> use a logger per event type, so the final user use log4j/wathever
> facilities to change the log level for hide/show messages, and not
> configure the LoggingFilter for changing the loglevel to the hidden
> one :)
>

I like the idea of it simply sitting on top of underlying logging framework
configuration to figure out the log level.  Points above that are pretty
reasonable.  Maarten below also makes some good points with respect to even
possibly getting rid of it.

Alex

Reply via email to