Introducing Spring Framework

Chapter 3 ■ Applying Different Configurations
}
public Document getDoc3() {
return doc3;
}
public void setDoc3(Document doc3) {
this.doc3 = doc3;
}
public Document getDoc4() {
return doc4;
}
public void setDoc4(Document doc4) {
this.doc4 = doc4;
}
public Document[] getAll() {
return new Document[] { doc1, doc2, doc3, doc4 };
}
Well, now this looks a little better. You are separating the way you are extracting the data, but how are you
doing this? Well, if you recall, you were using some kind of storage method to retrieve the information, right?
(See Listing 3-2.) Then you decided to reimplement your SearchEngine interface by adding a new way to get the data,
and the solution was to create an interface that will be injected independent of its implementation, making your class
more robust and easy to maintain. But let’s see how you are going to modify the XML so the Spring container knows
about all of these new modifications. Listing 3-6 is an example of your new modified mydocuments-context.xml
configuration file. This configuration holds all the information about your new DocumentDAO class implementation
(DocumentRepository) and how it’s being injected in your SearchEngine implementation.
Listing 3-6. mydocuments-context.xml
30