Comments for Technophile Blog

Comment on Sawing through the Java Loggers by Übersicht über Java Logging-Frameworks | neuesausfreaktown

Übersicht über Java Logging-Frameworks | neuesausfreaktown — Sun, 07 Apr 2013 21:18:20 +0000

[...] Dickens hat in seinem Blog-Post Sawing through the Java Loggers mal die aktuellen Logging Frameworks der Java Welt [...]

Comment on Sawing through the Java Loggers by Gordon

Gordon — Tue, 02 Apr 2013 13:08:53 +0000

Unless you are including closed-source projects, you can find out what the internal logging framework. I have not found an issue with this yet.

Using Maven you can determine the dependencies via mvn dependency:tree. This is an essential tool in Maven for determining and managing transitive dependencies.

As for Tomcat, See the links for my Enterprise Spring Best Practices blog for code samples on how to use SLF4j and Logback with the Maven plugin. If you want to know how to configure Tomcat standalone, I can provide detail on that also.

Regards,
Gordon

Comment on Sawing through the Java Loggers by Frisian

Frisian — Tue, 02 Apr 2013 08:10:06 +0000

In the first paragraph you talk about applications, yet you look at the logging choices from a library author’s perspective. For libraries, SL4J and commons.logging are a reasonable choice, because one never knows, which logging framework is used inside the application that includes the library.
With an application, things are a bit different, though: especially with web applications you want to have isolated per-application settings. Surprisingly, JDK logging is your friend here. Look at the Tomcat LogManager implementation for an example on how to achieve this without hassle. Besides, x4juli provides most of the stuff log4j offers and JDK logging misses.

Comment on Sawing through the Java Loggers by Christian

Christian — Fri, 29 Mar 2013 08:53:27 +0000

Hi,

nice article, but you are wrong on your log4j impression. There is a log4j 2.0 in the making and its already pretty good:
http://logging.apache.org/log4j/2.x

Also see:
http://logging.apache.org/log4j/2.x

Cheers,
Christian

Comment on Enterprise Spring Best Practices – Part 1 – Project Config by Sawing through the Java Loggers | Technophile Blog

Sawing through the Java Loggers | Technophile Blog — Thu, 28 Mar 2013 02:09:24 +0000

[...] See: Enterprise Spring Best Practices Blog [...]

Comment on Database Configuration with Spring 3.2 Environment Profiles by Neale Upstone

Neale Upstone — Wed, 27 Mar 2013 11:27:05 +0000

Gordon, I’m finding answers on your blog far too often. As part of a conversion to use Liquibase (from manual schema management), and while part way through conversion to Java configuration, the your SpEL above inspired the following entry in my Hibernate properties:


#{ environment.acceptsProfiles('liquibase') ? 'none' : environment['hibernate.hbm2ddl'] }

Comment on Simpler JPA with Spring Data-JPA by henry harles

henry harles — Fri, 22 Mar 2013 21:09:50 +0000

Can you just provide the spring data jpa small application
Examlle using xml configuration only not with @autowire over repository it should be injected only with xml only

Comment on Simpler JPA with Spring Data-JPA by Stephane

Stephane — Fri, 15 Mar 2013 08:15:29 +0000

I’m surprised to see a: extends ProductService instead of an: implements ProductService

Comment on Spring 3.1 Environment Profiles by Database Configuration with Spring 3.2 Environment Profiles | Technophile Blog

Thu, 28 Feb 2013 19:06:01 +0000

[...] This is a followup to my previous blog Spring 3.1 Environment Profiles [...]

Comment on Spring Expression Language (SpEL) Predefined Variables by Gordon

Gordon — Thu, 28 Feb 2013 15:08:27 +0000

Jorge,

That is now part of the Environment bean which you can autowire into your Spring classes & tests.

@Autowired Environment environment