Is there a specific reason why you are not using the preferred @Controller model with the RequestMappingHandlerAdapter? This adapter is much more powerful and flexible than the others. Typically you should not need to implement any Spring interfaces or extend any Spring classes (like AbstractController) with the newer model. This decreases coupling to the framework.
The simple URL mapping requires explicit configuration for each controller and does not auto detect mappings. Using this approach will lead to very large config files if you have a large number of controllers.