MVC migration from 2.0 inheritance-based to 3.0 annotation

[Owen Corpening]

I want to migrate my existing 2.0 inheritance based application to Spring 3.0 REST annotations, preferably one controller at a time keeping it functional the whole time. It would be handy if I could add to what I have so I could asynchronously modify the client side: in other words maintain the existing controller while adding the new RESTful ones, but that is nice-to-have: if I must modify the client side simultaneously then that's fair.

I see much documentation of how to write new controllers, but how do I repair what I have got?

If my app has an existing inheritance hierarchy of controllers - do I just remove the "extends Asynchronous..." from the baseclass? That would make me modify hundreds of controllers at once right there. Does it hurt to both leave the "extends" and add "@Controller"? What about applicationContext, leave the old mappings while adding that new search-one?

I could not find posts/articles addressing this, thanks,
owen

[David Newton]

I'm curious what happened you tried it--seems a quick-enough test.

[Mark Spritzler]

For URL Mapping you can define multiple mappers in your configuration and set an index to say which one to use first. So you can go one by one on the Controllers and change them.

http://static.springsource.org/spring/docs/3.0.x/spring-framework-reference/html/ch15s04.html

and previous version

http://static.springsource.org/spring/docs/2.5.x/reference/mvc.html#mvc-handlermapping

The order attribute is what you use to say use one HandlerMapping class first before the other. A lower number is used before a higher number.

Hope that helps.

Mark