This pull request should fix issue #103. The class DbUnitRunner will now use the overloaded findAnnotation method on the org.springframework.core.annotation.AnnotationUtils class in Spring Core that takes a Class<?> as an argument opposed to AnnotatedElement. The latter will only look for the annotation on the given class while the other methods tries to look on it's parent classes/interfaces if the annotation is not present on the given class itself.
This reintroduces the behaviour from older version of spring-test-dbunit.
Hi,
This pull request should fix issue #103. The class
DbUnitRunner
will now use the overloadedfindAnnotation
method on theorg.springframework.core.annotation.AnnotationUtils
class in Spring Core that takes aClass<?>
as an argument opposed toAnnotatedElement.
The latter will only look for the annotation on the given class while the other methods tries to look on it's parent classes/interfaces if the annotation is not present on the given class itself.This reintroduces the behaviour from older version of spring-test-dbunit.