There's no doubt that annotations and inheritance can get a little tricky, but I think that should work. Try explicitly adding the AnnotationMethodHandlerAdapter to your servlet context. static.springframework.org/spring/docs/2... If that doesn't work, a little more information would be helpful.
Specifically, are the two annotated controller methods from the interface? Is Foo supposed to be RegistrationController?
What I needed to do was replace with This forces aspectj to use CGLIB for doing aspects instead of dynamic proxies - CGLIB doesn't lose the annotation since it extends the class, whereas dynamic proxies just expose the implemented interface.
The true reason you need to use 'proxy-target-class="true"' is in DefaultAnnotationHandlerMapping#determineUrlsForHandler() method: though it uses ListableBeanFactory#findAnnotationOnBean for looking up a @RequestMapping annotation (and this takes care about any proxy issues), the additional lookup for @Controller annotation is done using AnnotationUtils#findAnnotation (which does not handles proxy issues).
I am working with Spring 3.0. X and I am having exactly the same problem: Everything works fine, until I add an interface to my controller-class! I am using the namespace-configuration, like in the examples in the documentation.
But in 3.0. X the -statement does not have a "proxy-target-class"-property anymore! I tried to push all annotations to interfaces but that did not help either :( I'm lost!
Sorry! The solution () still works with 3.0. X -- I just confused and!
– Kai Moritz Sep 10 '10 at 12:22.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.