Spring MVC RequestMapping matches wrong URL?

I think it would be better not to mix the SimpleUriHandlerMapping and RequestMapping methodologies. I don't think they are meant to work together.

I think it would be better not to mix the SimpleUriHandlerMapping and RequestMapping methodologies. I don't think they are meant to work together. I think what you'd want is just a Class level RequestMapping for the /api/v1/domain and then method level mappings for the individual cases.So, in other words, remove the SimpleUrlHandlerMapping entry and do this instead: @Controller @RequestMapping(value = "/api/v1/domain") public class DomainsController { @RequestMapping(value = "/{domainId}/sessions", method=RequestMethod.

GET) public void findSessions(@PathVariable final String domainId) { ... } @RequestMapping(value = "/{domainId}/user/{username}/sessions", method=RequestMethod. GET) public void findUserSessions( @PathVariable final String domainId, @PathVariable final String username) { ... } } This tells Spring this controller is responsible for all requests starting with /api/v1/domain and then the method level request mappings are relative to this.

Well, it was not as easy as removing SimpleUrlHandlerMapping entry and adding @RequestMapping, but after some internet googling I finally managed to divorce them. (I can't totaly drop SUHM because there are other 'legacy' controllers). It works correctly now with DefaultAnnotationHandlerMapping – dvd May 16 at 12:57.

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.