Needing help to externalize url mappings for @RequestMapping

[cgarman1]

I'm creating an email form that will be used in multiple applications and multiple places in the same application on different url patterns. Ideally I would like to create it as an @MVC controller that is autowired and automatically starts itself up via a component scan when the servlet container starts.

Here is my problem. I need the @RequestMapping(value={"/url1","url2","..."}) to be configurable outside the java in a xml file (sort of the way you use to be able to do using the SimpleFormController and SimpleUrlHanderMapping). I need to be able to inject my url mappings so that each application can have a completely separate set of url mappings. Can someone tell me if this is possible?

I could use SimpleFormController to accomplish this (minus the component scan) but I really wanted to use @MVC because I was told that the old controller hierarchy is or will soon be deprecated.

[maheshguruswamy]

AFAIK ..i dont think its possible out of the box. Maybe your email functionality should be a service and not a controller? This way you can let consumers define the controllers.

[Marten Deinum]

Actually it is available..

Simple mark your method with @RequestMapping and use a SimpleUrlHandlerMapping to explicitly configure the urls which are handled by this controller. That should basically do it.

[cgarman1]

You're right, I could and probably should create a service that handles all the email functionality but I was also trying to create a component to duplicate current functionality we have with a struts email form.

Am I correct that the old controllers have been deprecated? I'm trying to figure out what my options are...I obviously don't want to code something that won't work in the next version of spring.

[maheshguruswamy]

Actually it is available..

Simple mark your method with @RequestMapping and use a SimpleUrlHandlerMapping to explicitly configure the urls which are handled by this controller. That should basically do it.

I thought the OP wanted to pull URLs from a properties file and use it in his annotated controllers something like

@RequestMapping(pullvaluefrompropertyfile)
@Controller

Maybe i am mistaken?

[Marten Deinum]

He wants to externalize configuration, which you can do by explicitly configure the urls and create a single @RequestMapping method. If he wants to stay with properties files and @RequestMapping that isn't going to work...

[cgarman1]

Actually it is available..

Simple mark your method with @RequestMapping and use a SimpleUrlHandlerMapping to explicitly configure the urls which are handled by this controller. That should basically do it.

So can my controller only have two methods - one marked as @RequestMapping(method=RequestMethod.GET) and one marked @RequestMapping(method=RequestMethod.POST)? Otherwise how does it know which url calls with method in your controller?

[cgarman1]

He wants to externalize configuration, which you can do by explicitly configure the urls and create a single @RequestMapping method. If he wants to stay with properties files and @RequestMapping that isn't going to work...

I don't need it in a properties file...the SimpleUrlHandlerMapping works just fine. I believe I have it working...I'm just not sure why it works

[Marten Deinum]

So can my controller only have two methods - one marked as @RequestMapping(method=RequestMethod.GET) and one marked @RequestMapping(method=RequestMethod.POST)? Otherwise how does it know which url calls with method in your controller?

If there is only one with only @RequestMapping then that method will always be called, if you want to make it a bit more flexible you could add one for a GET and a POST.

I don't need it in a properties file...the SimpleUrlHandlerMapping works just fine. I believe I have it working...I'm just not sure why it works

What is it you doubt? It is simply a Handler and you can use any means of HandlerMapping to map a URL to a Handler. Execution is done by a HandlerAdapter which knows how to handle a Controller (SimpleControllerHandlerAdapter) or a @Controller (DefaultAnnotationHandlerAdapter). So the mapping and execution of a handler are 2 different things and shouldn't be confused.

[Marten Deinum]

So can my controller only have two methods - one marked as @RequestMapping(method=RequestMethod.GET) and one marked @RequestMapping(method=RequestMethod.POST)? Otherwise how does it know which url calls with method in your controller?

If there is only one with only @RequestMapping then that method will always be called, if you want to make it a bit more flexible you could add one for a GET and a POST.

I don't need it in a properties file...the SimpleUrlHandlerMapping works just fine. I believe I have it working...I'm just not sure why it works

What is it you doubt? It is simply a Handler and you can use any means of HandlerMapping to map a URL to a Handler. Execution is done by a HandlerAdapter which knows how to handle a Controller (SimpleControllerHandlerAdapter) or a @Controller (DefaultAnnotationHandlerAdapter). So the mapping and execution of a handler are 2 different things and shouldn't be confused.