Introducing Spring Framework

Chapter 4 ■ Using Beans Scopes
import com.apress.isf.java.model.Document;
import com.apress.isf.java.model.Type;
import com.apress.isf.java.service.SearchEngine;
public class MyDocumentsTest {
private ClassPathXmlApplicationContext context;
private SearchEngine engine;
private Type webType;
@Before
public void setup(){
context = new ClassPathXmlApplicationContext("META-INF/spring/mydocuments-context.xml");
}
@Test
public void testAll() {
engine = context.getBean(SearchEngine.class);
webType = context.getBean("webType",Type.class);
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());
engine = context.getBean(SearchEngine.class);
}
documents = engine.listAll();
assertNotNull(documents);
assertTrue(documents.size() == 4);
}
In Listing 4-2, you have simply created one test method that contains the call of the getBean method. In this case,
you want to know how the Spring container can deal with the creation of the SearchEngine and the injection of your
DocumentDAO implementation.
If you run Listing 4-2 without modifying the XML file (mydocuments-context.xml), then you should see the
following output:
$ gradle -Dtest.single=MyDocumentsTest test
DEBUG [main] ServiceSearchEngine created: com.apress.isf.spring.service.ServiceSearchEngine@1aee419f
DEBUG [main] Document DAO set: com.apress.isf.spring.data.DocumentRepository@53b97d73
47