Introducing Spring Framework

Chapter 18 ■ Spring and Groovy
class MyDocumentsTest {
private static final Logger log = LoggerFactory.getLogger(MyDocumentsTest.class)
private final RECORDS = 6
private final ID = "1acbb68a-a859-49c9-ac88-d9e9322bac55"
private final ctx = new GenericGroovyApplicationContext("classpath:META-INF/groovy/
mydocuments.groovy")
@Test
@Ignore
void testJDBC(){
log.info "Testing JDBC..."
assertNotNull ctx
def documentFacade = ctx.getBean("documentFacade")
assertNotNull documentFacade
int size = documentFacade.allDocuments.size()
assertEquals RECORDS,size
}
assertNotNull documentFacade.findDocumentById(ID)
@Test
public void testProducer(){
log.debug("Testing RabbitMQ Producer...");
def documentFacade = ctx.getBean("documentFacade")
def rabbitmqProducer = ctx.getBean("rabbitmqProducer")
assertNotNull(rabbitmqProducer)
assertNotNull(documentFacade)
}
}
documentFacade.allDocuments.each{
rabbitmqProducer.send it
}
sleep 5000
Listing 18-7 shows the unit test. In this case, you wrote the unit test using Groovy, but you can use Java and
still make the use of the Groovy scripts. So, what is the difference between this unit test versus the ones you did in
previous chapters? The first big difference is that all your bean definitions are using the Spring DSL, and the second
is that you are using the GenericGroovyApplicationContext class (that will load the groovy DSL files) instead of the
ClassPathXmlApplicationContext class that loads only XML files.
Run this test with
gradle :ch18:test
You will have the same output as in Chapter 16 because you are using the same bean descriptions and doing
RabbitMQ messaging (don’t forget to have the RabbitMQ up and running).
Take a moment and do a last review of the unit test and the Spring DSL. You will find that you got rid of all the
XML verbosity and simplified the bean definitions, thanks to the Groovy programing language.
258