Jersey Getting a HTTP 405, path mapping not handled as expected?

With the 3 methods defined as above you essentially have 3 resources.

With the 3 methods defined as above you essentially have 3 resources: /{solution} /{solution}/{path:a-z0-9/\-*} {path: a-z0-9/\-*} When Jersey matches the request to resource methods, it first determines which resource (i.e. URI pattern) it should be mapped to. The third one is the most specific one that matches the request URL, so that one is matched.

Only then Jersey looks if a corresponding HTTP method is handled for that resource. This is in compliance with the JAX-RS specification - you can see the detailed description of the matching algorithm in the spec here: jsr311.java.net/nonav/releases/1.1/spec/... So, you should think about the logical resources, have the URI templates match them and then implement the corresponding HTTP methods for these. I.e.

If "/{solution}" and "/{solution}/{path:a-z0-9/\-*}" are logically two distinct resources, and both should support @DELETE, you should define two delete operations, one with the first template and the other one with the second URI template.

Thanks for that, thats what I found after playing around. I've now done like you suggested. – TedTrippin Oct 17 at 10:50.

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.