Hello

I complety agree with Roman, a new library dependency is not a good idea if there is not a clear need.

About the checks in the logging, please review the code. All the logging statements checks if logging is enabled. Because this
is a driver and performance must be as good as posible, the check use a local variable that is null if logging is not enabled, this
way we get the best performance when logging is disabled.

Regards
Blas Rodriguez Somoza

----- Original Message -----
From: "rrokytskyy" <rrokytskyy@...>
To: <Firebird-Java@yahoogroups.com>
Sent: Thursday, July 18, 2002 6:01 PM
Subject: [Firebird-Java] Re: fixed bug in logging


> Hi,
>
> > I was also wondering it might be appropriate to use the Jakarta
> > Commons Logging package to introduce an abstraction layer between
> > the driver and the actual logging mechanism (eg, Log4J, or the host
> > application's native logging facility). I think this would be a
> > very developer-friendly thing to do. It would certainly play more
> > nicely with my own application.
> >
> > http://jakarta.apache.org/commons/logging.html
> >
> > Any thoughts? I have some cycles available and would be willing to
> > lead the charge on this. (I'd also like to take a stab at tweaking
> > the exception architecture to give better diagnostics, to help
> > alleviate the pain many of us have felt debugging configuration
> > problems).
>
> Please, contact Blas Rodriguez Somoza directly. He did this logging
> stuff, so he is the best person to discuss with. We do have home-
> grown logging abstraction layer, and personally I would reuse it to
> avoid introducing yet another library dependency.
>
> Best regards,
> Roman Rokytskyy
>
>
>
> To unsubscribe from this group, send an email to:
> Firebird-Java-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>