Comments on: Logging Dependencies in Spring http://blog.springsource.org/2009/12/04/logging-dependencies-in-spring/ The voice of SpringSource Wed, 08 Feb 2012 17:31:53 +0000 hourly 1 http://wordpress.org/?v=3.1.1 By: Peter http://blog.springsource.org/2009/12/04/logging-dependencies-in-spring/comment-page-1/#comment-174764 Peter Tue, 03 Aug 2010 09:24:56 +0000 http://blog.springsource.com/?p=3513#comment-174764 Is it possible to have spring logging work with the config file not directly on the class path? I usually stick things like log4j.xml in a config directory and would like to do the same with this. I've tried using org.springframework.util.Log4jConfigurer and this gets logging working for my application, but spring itself is still silent. Thanks, Peter Is it possible to have spring logging work with the config file not directly on the class path?

I usually stick things like log4j.xml in a config directory and would like to do the same with this.

I've tried using org.springframework.util.Log4jConfigurer and this gets logging working for my application, but spring itself is still silent.

Thanks,
Peter

]]> By: Robert Glover http://blog.springsource.org/2009/12/04/logging-dependencies-in-spring/comment-page-1/#comment-170435 Robert Glover Thu, 17 Dec 2009 20:40:45 +0000 http://blog.springsource.com/?p=3513#comment-170435 I immediately stopped using my own (inferior) solution in favor of Tony Dalbrekt's far better solution as soon as I saw his post. In fact, just today I added the following to a maven parent pom I was modifying: <!-- See the blog entry at the following address for an explanation how/why slf4j is being used instead of commons-logging: http://blog.springsource.com/2009/12/04/logging-dependencies-in-spring/ --> <dependency> <groupId>commons-logging</groupId> <artifactId>commons-logging</artifactId> <version>1.1.1</version> <scope>provided</scope> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-api</artifactId> <version>1.5.8</version> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>jcl-over-slf4j</artifactId> <version>1.5.8</version> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-log4j12</artifactId> <version>1.5.8</version> </dependency> <dependency> <groupId>log4j</groupId> <artifactId>log4j</artifactId> <version>1.2.12</version> </dependency> I immediately stopped using my own (inferior) solution in favor of Tony Dalbrekt's far better solution as soon as I saw his post. In fact, just today I added the following to a maven parent pom I was modifying:

<!–
See the blog entry at the following address for
an explanation how/why slf4j is being used instead of
commons-logging:
http://blog.springsource.com/2009/12/04/logging-dependencies-in-spring/
–>
<dependency>
<groupId>commons-logging</groupId>
<artifactId>commons-logging</artifactId>
<version>1.1.1</version>
<scope>provided</scope>
</dependency>

<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
<version>1.5.8</version>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>jcl-over-slf4j</artifactId>
<version>1.5.8</version>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-log4j12</artifactId>
<version>1.5.8</version>
</dependency>
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>1.2.12</version>
</dependency>

]]> By: Rusty Wright http://blog.springsource.org/2009/12/04/logging-dependencies-in-spring/comment-page-1/#comment-170430 Rusty Wright Thu, 17 Dec 2009 19:53:16 +0000 http://blog.springsource.com/?p=3513#comment-170430 As an addendum to what Dave suggested to Tom, if you're using maven, you can see where a dependency is coming from by doing "mvn dependency:tree". The rule of thumb with maven is that if you're explicitly using some package/jar/dependency, then you should explicitly list it in your maven dependencies; don't just let arrive in your project as a side effect of it being pulled in by something else. As an addendum to what Dave suggested to Tom, if you're using maven, you can see where a dependency is coming from by doing "mvn dependency:tree". The rule of thumb with maven is that if you're explicitly using some package/jar/dependency, then you should explicitly list it in your maven dependencies; don't just let arrive in your project as a side effect of it being pulled in by something else.

]]> By: Dave Syer http://blog.springsource.org/2009/12/04/logging-dependencies-in-spring/comment-page-1/#comment-170420 Dave Syer Thu, 17 Dec 2009 15:47:10 +0000 http://blog.springsource.com/?p=3513#comment-170420 @Robert: I edited your post because Wordpress ate your XML formatting. I had to gues what the original said, but it looks to me like the same set of dependencies as in the main article, unless I missed something. You just replaced the exlcusion with an empty jar (which is the "version 99" approach). @Tom: someone on the forum reported the same issue and I think it turned out that log4j wasn't being used because of another logging library that was pulled in by Hibernate (or another external library). Check your classpath carefully. @Robert: I edited your post because WordPress ate your XML formatting. I had to gues what the original said, but it looks to me like the same set of dependencies as in the main article, unless I missed something. You just replaced the exlcusion with an empty jar (which is the "version 99" approach).

@Tom: someone on the forum reported the same issue and I think it turned out that log4j wasn't being used because of another logging library that was pulled in by Hibernate (or another external library). Check your classpath carefully.

]]> By: Ryan http://blog.springsource.org/2009/12/04/logging-dependencies-in-spring/comment-page-1/#comment-170185 Ryan Sat, 12 Dec 2009 05:25:19 +0000 http://blog.springsource.com/?p=3513#comment-170185 I've recently started using logback as an alternative to log4j. It has native support for slf4j, and the config/api is very similar to log4j as an added bonus. I've recently started using logback as an alternative to log4j. It has native support for slf4j, and the config/api is very similar to log4j as an added bonus.

]]> By: TomS http://blog.springsource.org/2009/12/04/logging-dependencies-in-spring/comment-page-1/#comment-170134 TomS Thu, 10 Dec 2009 19:42:57 +0000 http://blog.springsource.com/?p=3513#comment-170134 When I upgraded my logging from Spring 2.5 to 3.0 it appears that log4j.xml is read and configured when log4j.debug is on, but even though I turned off all the INFO level messages from org.springframework these all now appear in 3.0 where as they did not in 2.5. When I upgraded my logging from Spring 2.5 to 3.0 it appears that log4j.xml is read and configured when log4j.debug is on, but even though I turned off all the INFO level messages from org.springframework these all now appear in 3.0 where as they did not in 2.5.

]]> By: uberVU - social comments http://blog.springsource.org/2009/12/04/logging-dependencies-in-spring/comment-page-1/#comment-169954 uberVU - social comments Sat, 05 Dec 2009 22:55:00 +0000 http://blog.springsource.com/?p=3513#comment-169954 <strong>Social comments and analytics for this post...</strong> This post was mentioned on Twitter by Ibrahim Saracoglu: Logging Dependencies in Spring http://blog.springsource.com/2009/12/04/logging-dependencies-in-spring/ #java #spring #jcl #slf4j #log4j... Social comments and analytics for this post…

This post was mentioned on Twitter by Ibrahim Saracoglu: Logging Dependencies in Spring http://blog.springsource.com/2009/12/04/logging-dependencies-in-spring/ #java #spring #jcl #slf4j #log4j…

]]> By: Robert Glover http://blog.springsource.org/2009/12/04/logging-dependencies-in-spring/comment-page-1/#comment-169912 Robert Glover Fri, 04 Dec 2009 21:42:12 +0000 http://blog.springsource.com/?p=3513#comment-169912 Because of a need to develop locally in Tomcat but later deploy to IBM Websphere 6.1, I wrote a 31 page Power Point Presentation named "HOW_TO_CONFIGURE_commons-logging-for-artifactory_with_slf4j.pptx". Unfortunately there is no way to attached it to this comment. What I basically did was devise an "Artifactory port" of the concepts of the solution explained at the link in the comment before this one and at the following two links: http://stubbisms.wordpress.com/2008/07/27/death-to-commons-logging-long-live-slf4j/ http://www.slf4j.org/legacy.html The gist of the solution was to create within "Artifactory" a “dummy” commons-logging jar file to replace the “real” commons-logging jar file. The dummy JCL jar file contains the same "MANIFEST-MF" file as the real commons-logging jar file and one dummy java class. When doing a local maven build, the "dummy" version of the JCL jar gets copied from Artifactory into the local maven repository on the local hard drive. The changes in the Pom file of the Spring Webapp were to add the following: <code lang="xml"> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-api</artifactId> <version>1.5.8</version> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>jcl-over-slf4j</artifactId> <version>1.5.8</version> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-log4j12</artifactId> <version>1.5.8</version> </dependency> <dependency> <groupId>log4j</groupId> <artifactId>log4j</artifactId> <version>1.2.9</version> </dependency> </code> With this solution JCL works okay in IBM Websphere 6.1, and there is no need to change the "parent last" setting. In the past, changing that setting didn't work for me, which is why I took the time to devise this solution. Because of a need to develop locally in Tomcat but later deploy to IBM Websphere 6.1, I wrote a 31 page Power Point Presentation named "HOW_TO_CONFIGURE_commons-logging-for-artifactory_with_slf4j.pptx". Unfortunately there is no way to attached it to this comment.

What I basically did was devise an "Artifactory port" of the concepts of the solution explained at the link in the comment before this one and at the following two links:

http://stubbisms.wordpress.com/2008/07/27/death-to-commons-logging-long-live-slf4j/

http://www.slf4j.org/legacy.html

The gist of the solution was to create within "Artifactory" a “dummy” commons-logging jar file to replace the “real” commons-logging jar file. The dummy JCL jar file contains the same "MANIFEST-MF" file as the real commons-logging jar file and one dummy java class. When doing a local maven build, the "dummy" version of the JCL jar gets copied from Artifactory into the local maven repository on the local hard drive.

The changes in the Pom file of the Spring Webapp were to add the following:



org.slf4j
slf4j-api
1.5.8


org.slf4j
jcl-over-slf4j
1.5.8


org.slf4j
slf4j-log4j12
1.5.8


log4j
log4j
1.2.9

With this solution JCL works okay in IBM Websphere 6.1, and there is no need to change the "parent last" setting. In the past, changing that setting didn't work for me, which is why I took the time to devise this solution.

]]> By: Rusty Wright http://blog.springsource.org/2009/12/04/logging-dependencies-in-spring/comment-page-1/#comment-169907 Rusty Wright Fri, 04 Dec 2009 19:30:13 +0000 http://blog.springsource.com/?p=3513#comment-169907 Great tip Tony; I've been using the 99.0-does-not-exist hack for a while now and it's nice to not need that. Great tip Tony; I've been using the 99.0-does-not-exist hack for a while now and it's nice to not need that.

]]> By: Dave Syer http://blog.springsource.org/2009/12/04/logging-dependencies-in-spring/comment-page-1/#comment-169905 Dave Syer Fri, 04 Dec 2009 19:19:14 +0000 http://blog.springsource.com/?p=3513#comment-169905 Thanks for the additional suggestion. There's always more than one way, as they say, to skin a cat. I updated your comment and added back the XML that the blog machine helpfully stripped out when you posted. Hope that's OK. Thanks for the additional suggestion. There's always more than one way, as they say, to skin a cat.

I updated your comment and added back the XML that the blog machine helpfully stripped out when you posted. Hope that's OK.

]]>