Andrea Aime a écrit :
> Ideally the Geotools library should allow for
> both setups, both the fall back on commons logging
> and the one on log4j, thought since commons logging
> was there to allow a chioce between java logging
> and log4j, we could probably go and code a
> Log4JLogger only.
Given that common-logging is reputed to have classloader problems (in my
understanding Hibernate is migrating from common-loggin to SLF4J because of
that), I would be in favor of skipping common-logging. I see a choice between
two possibilities:
- SLF4JLogger (i.e. same plan using SLF4J instead of common-logging).
- Log4JLogger as suggested by Andrea
The former would allow the choice of logging frameworks other than Log4J and
java logging, but I don't know if there is a demand for that. The later may be
less prone to unexpected issues because there is one less intermediate step, and
we may also loose less informations because there is more matches for the java
logging API in Log4J than in commons-logging.
I'm fine with boths of the above approachs, at your choice.
Martin
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>
http://get.splunk.com/_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@...
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
