So I am trying to get some integration testing of JMS processing, Spring (v4.1.6) based code.
It\'s a very standard Spring setup with @JmsListener
annotate
In order to avoid having to change your actual @JmsListener method, you could try and use AOP in your test...
First create an aspect class like this:
@Aspect
public static class JmsListenerInterceptor {
@org.aspectj.lang.annotation.After("@annotation(org.springframework.jms.annotation.JmsListener)")
public void afterOnMessage(JoinPoint jp) {
// Do countdown latch stuff...
}
}
Then add it in your application context configuration you're using for testing, like this:
If everything goes as planned, the JmsListenerInterceptor will count down and you don't have to change your actual code.
IMPORTANT: I just found out that using AOP and Mockito to verify if certain methods in your @JmsListener have been called is a bad combination. The reason seems to be the extra wrapping into CGLib classes resulting in the wrong/actual target instance to be invoked instead of the Mockito proxy.
In my test, I have an @Autowired, @InjectMocks Listener object and a @Mock Facade object for which I want to verify that a certain method has been called.
With AOP:
Without AOP:
This goes to show that you'll need to watch out using AOP the way I tried to, as you might end up with different instances in both Threads...