[jboss-user] [JBoss Tools] - Re: Use Log4j logging instead of apache commons logging

Denis Golovin do-not-reply at jboss.com
Mon Jul 22 18:37:16 EDT 2013

Denis Golovin [https://community.jboss.org/people/dgolovin] created the discussion

"Re: Use Log4j logging instead of apache commons logging"

To view the discussion, visit: https://community.jboss.org/message/829186#829186

Considering what is stated in apache common logging documentation:
> The commons-logging.jar file includes the JCL API, the default LogFactory implementation and thin-wrapper Log implementations for  http://logging.apache.org/log4j/docs/index.html Log4J,  http://avalon.apache.org/logkit/index.html Avalon LogKit, the Avalon Framework's logging infrastructure, JDK 1.4, as well as an implementation of JDK 1.4 logging APIs (JSR-47) for pre-1.4 systems.
> In most cases, including commons-logging.jar and your preferred logging implementation in the classpath should be all that is required to use JCL.
you probably do not need to change anything, because generated classes should youse log4j through common logging interface. If you need do use log4j classes directly, then there is a workaround for that, which includes:
1. Copying dao/daohome.ftl template from hibernate-tools.jar to ${externalfolder}
2. Change it to your needs
3. Configure template location property for exporter in Hibernate Coge Generatiion Configuration dialog and point it to ${externalfolder} which contans dao/daohome.ftl file in it

Reply to this message by going to Community

Start a new discussion in JBoss Tools at Community

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-user/attachments/20130722/38366a5a/attachment-0001.html 

More information about the jboss-user mailing list