Introducing Spring Framework

Chapter 3 ■ Applying Different Configurations
}
public List listAll() {
return Arrays.asList(documentDAO.getAll());
}
Let’s compare Listing 3-2 and Listing 3-3. In Listing 3-3, you got rid of the hard-coded code, you got rid of the
storage method, and you are including a new attribute, documentDAO, which will be injected through its setter method,
but you need to help the Spring container to know about this new attribute and the class that will contain the data.
Next, let’s create the new classes, DocumentDAO and DocumentRepository. See Listing 3-4 and Listing 3-5. Listing 3-4
shows the DocumentDAO, which is the class that holds all the information about your documents that, for now, will be
in memory. Of course, the DocumentRepository (see Listing 3-5) is your implementation of it.
Listing 3-4. DocumentDAO.java
package com.apress.isf.spring.data;
import com.apress.isf.java.model.Document;
public interface DocumentDAO {
public Document[] getAll();
}
Listing 3-5 shows your DocumentRepository with four Document properties with their own setters and getters.
And yes, you are going to inject four documents through their setters.
Listing 3-5. DocumentRepository.java
package com.apress.isf.spring.data;
import com.apress.isf.java.model.Document;
public class DocumentRepository implements DocumentDAO {
private Document doc1;
private Document doc2;
private Document doc3;
private Document doc4;
public Document getDoc1() {
return doc1;
}
public void setDoc1(Document doc1) {
this.doc1 = doc1;
}
public Document getDoc2() {
return doc2;
}
public void setDoc2(Document doc2) {
this.doc2 = doc2;
}
29