Introducing Spring Framework

Chapter 5 ■ Working with Collections and Custom Types
public Document[] getAll() {
if(log.isDebugEnabled())
log.debug("Start Params: ");
Document[] result = documents.toArray(new Document[documents.size()]);
}
if(log.isDebugEnabled())
log.debug("End Result:" + result);
return result;
}
You need to remember that in your previous DocumentDAO implementation you had several Document objects
defined in your implementation. In this new DocumentRepository class (see Listing 5-1) you have removed those
documents: doc1, doc2, and so on; you have also added a collection, in this case a List of type Document. Note that
you are adding more logs to your class so you know what is going on. Let’s review Listing 5-2 and continue with the
other classes.
Listing 5-2. TypeDataDAO.java
package com.apress.isf.spring.data;
import com.apress.isf.java.model.Type;
public interface TypeDataDAO {
public Type[] getAll();
public Type findById(String id);
}
In the TypeDataDAO (see Listing 5-2) interface, you have just added a new method, findById. This method will
help you just to get the Type based on your id. With this new change, let’s modify the classes and implement this
method. Now let’s take a look at Listing 5-3, your TypeDataDAO implementation.
Listing 5-3. TypeDataRepository.java
package com.apress.isf.spring.data;
import java.util.Map;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import com.apress.isf.java.model.Type;
public class TypeDataRepository implements TypeDataDAO{
private static final Logger log = LoggerFactory.getLogger(TypeDataRepository.class);
private Map types = null;
public Map getTypes() {
return types;
}
54