Introducing Spring Framework

Chapter 3 ■ Applying Different Configurations
@Before
public void setup(){
context = new AnnotationConfigApplicationContext(MyDocumentsContext.class);
engine = context.getBean(SearchEngine.class);
webType = context.getBean(Type.class);
}
@Test
public void testWithBeanConfigurationFindByType() {
List documents = engine.findByType(webType);
assertNotNull(documents);
assertTrue(documents.size() == 1);
assertEquals(webType.getName(),documents.get(0).getType().getName());
assertEquals(webType.getDesc(),documents.get(0).getType().getDesc());
assertEquals(webType.getExtension(),documents.get(0).getType().getExtension());
}
}
@Test
public void testWithBeanConfigurationListAll() {
List documents = engine.listAll();
assertNotNull(documents);
assertTrue(documents.size() == 4);
}
In Listing 3-12, you are now using the AnnotationConfigApplicationContext class to load your Java configuration
class. This will tell the Spring container that the configuration will be based on a class and not on an XML file.
Running your unit test (see Listing 3-12) will be the same as running the gradle command:
gradle test
Using the GroovyBeanDefinitionReader Class
The new Spring Framework 4 introduces a new way to configure beans using the Groovy programming language. This
new feature was based on the Grails Framework, introducing a DSL (domain-specific language) for creating beans.
Let’s examine the following example in Listing 3-13.
Listing 3-13. mydocuments.groovy
import com.apress.isf.spring.service.ServiceSearchEngine
import com.apress.isf.spring.data.DocumentRepository
import com.apress.isf.java.model.Document
beans {
engine(ServiceSearchEngine){
documentDAO = ref("documentDAO")
}
40