I have Spring 3.2 web app and i have controller with following request mappings:
@RequestMapping(value = \"/test/{param1}\", method = RequestMethod.GET)
publ
I'm afraid it is not the expected answer, but as it is not specified in the documentation it should be regarded as undefined.
You could just try (eventually with putting "/test/logging" method first if source file), but even if it worked, you could not be sure that it will still work with another version of Spring Framework.
My advice is: if you can, avoid such ambiguous URLs, if you cannot, just have a single catchall @RequestMapping and forward from it by hand:
@RequestMapping(value = "/test/{param1}", method = RequestMethod.GET)
public String method0(@PathVariable(value = "param1") String param1, ...
) { // union of all parameters for both method1 and method2
String ret;
if ("login".equals(param1)) {
ret = method2(/* pass parameters for method 2 */ ...);
}
else {
ret = method1(/* params for method1 */ param1, ...);
}
return ret;
}
public String method1(String param1, ..
public String method2(//..
That way, you have full control on what method processes what url. Not necessarily the nicest way, but it is at least robust ...