Tomcat and Log4jConfigListener don't mix

At least not if you want to load your log4j.properties with classpath:log4j.properties. What happens is that Tomcat internally uses commons-logging, which finds log4j on your classpath and thinks "Hey, I'll use log4j". Log4j then finds your log4j.properties and reads it before Log4jConfigListener ever gets instantiated.

The result?

log4j:ERROR setFile(null,true) call failed.
java.io.FileNotFoundException: /logs/spring.log (No such file or directory)
      at java.io.FileOutputStream.openAppend(Native Method)
      at java.io.FileOutputStream.(FileOutputStream.java:177)
      at java.io.FileOutputStream.(FileOutputStream.java:102)
      at org.apache.log4j.FileAppender.setFile(FileAppender.java:289)
      at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:163)
      at org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:256)
      at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:132)
[...]

No worries, though; the application comes up just fine, and logs where you expect... If you're lucky and don't have a security manager.

With a security manager, you get a nice, fatal AccessControlException.

Bah.

The fix is simple: move log4j.properties away from the classpath root, e.g. into /WEB-INF.

Spring Security 2.0 + Spring 2.5 + Maven

If you're a Mavenite Spring 2.5 user, you'll need to jump through some extra hoops to use Spring Security 2, just as you had to when using Acegi with Spring 2.0.

First off you'll want to exclude org.springframework:spring-remoting and org.springframework:spring-support, as these two artifacts no longer exist in Spring 2.5.

In addition, you will most likely need to include org.springframework:spring-aop and org.springframework:spring-orm as dependencies, unless you're already using them.

That said, Spring Security's new config is nice. One particular security config file went from 118 lines to 24!

Generics makes DAOs easy

We've all been there. You're developing a medium-to-large application that uses a POJO persistence engine such as Hibernate. Good software design advocates that you have a DAO for each type of POJO, so off you go writing some. But after five–ten iterations of writing CRUD methods, it gets boring, doesn't it?

Here's how to make it easy.


Assumptions

This article uses generics; generics are supported starting with Java 5. My examples use classes from the Spring framework and assume that you're using Hibernate as your persistence engine, but the techniques illustrated should be applicable to other setups.

The interface

The standard DAO

Every DAO should support the basic CRUD methods:

• Create
  
• Retrieve
  
• Update
  
• Destroy

I tend to have three methods:

save
Saves an object, updating if it is already present; this handles C and U.

get
Fetches an object by id; this handles R.

remove
Deletes an object from the persistent store; this handles D.

In addition, I like to define methods to remove an object by its id, load all objects of the type, and to reassociate an object with the persistence layer. This last method is useful in an MVC environment, where your persistent object may make several round-trips to the view layer before you're done. So we end up with the following interface:

 public interface BaseDAO {
     void save(Object o);

     Object get(Serializable id);

     void remove(Object o);
 
     void remove(Serializable id);

     List loadAll();

     void reassociate(Object o);
 }

The generic DAO interface, version 1

Adding generics

Notice all the Object references in that interface? That's not very modern, and it means that we have to litter our code with potentially unsafe casts. Let's add some generics.

 public interface BaseDAO<T> {
     void save(T o);

     T get(Serializable id);

     void remove(T o);

     void remove(Serializable id);

     List<T> loadAll();

     void reassociate(T o);
 }

The generic DAO interface, version 2

A concrete DAO

With this interface defined, we can define a concrete DAO interface for the fictitious Order class:

 public interface OrderDAO extends BaseDAO<Order> { }

The OrderDAO interface

Yes, that is all there is to it. This interface now has methods to do CRUD operations on Order objects, with compile-time type safety.

The implementation

Implementing the generic DAO

The implementation of the generic DAO is straightforward:

 public abstract class BaseDAOHibernate<T>
     extends HibernateDaoSupport
     implements BaseDAO<T> {
     public void save(T object) {
         getHibernateTemplate().saveOrUpdate(object);
     }

     public T get(Serializable id) {
         return getModelClass().cast(getHibernateTemplate().get(getModelClass(), id));
     }

     public void remove(T object) {
         getHibernateTemplate().delete(object);
     }

     public void remove(Serializable id) {
         remove(get(id));
     }

     @SuppressWarnings("unchecked")
     public List<T> loadAll() {
         return getHibernateTemplate().loadAll(getModelClass());
     }

     public void reassociate(T object) {
         getHibernateTemplate().lock(object, LockMode.NONE);
     }

     protected abstract Class<T> getModelClass();
 }

Implementing BaseDAO

I added the @SuppressWarnings annotation to get rid of a compiler warning about an unchecked cast.

Implementing OrderDAO

Now comes the reason for doing all this:

 public class OrderDAOHibernate
     extends BaseDAOHibernate<Order>
     implements OrderDAO {
     protected Class<Order> getModelClass() {
         return Order.class;
     }
 }

Implementing OrderDAO

And there you have it, a complete DAO for Order objects in seven neatly-formatted lines of code.

Conclusion

Generics can be a difficult subject to grasp, but when the benefits are as major as shown here, it is well worth the effort to get to grips with it.

Writing less code is always a big win. Not only is there less work to do (meaning that you get to go home early), but it is easier to debug the code that is present.