[ https://issues.apache.org/jira/browse/CXF-7218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829698#comment-15829698 ]
Dmitry Murashenkov commented on CXF-7218: ----------------------------------------- Sure, but perhaps at least in some cases (like mine) we can tell that this is probably a mistake and and log message during startup that annotated method will be ignored altogether. At least people will know possible cause, otherwise I was first checking jetty to see if I should explicitly enable DELETE method on it. > @PathParam on both class and interface disables method > ------------------------------------------------------ > > Key: CXF-7218 > URL: https://issues.apache.org/jira/browse/CXF-7218 > Project: CXF > Issue Type: Bug > Affects Versions: 3.1.9 > Reporter: Dmitry Murashenkov > Assignee: Sergey Beryozkin > > I have jax rs method in interface: > @DELETE > @Path("/role/{id}") > void deleteRole(@PathParam("id") String id); > And implementation: > @Override > public void deleteRole(String id) > This works well, but if I leave annotation on the implementation method: > > @Override > public void deleteRole(@PathParam("id") String id) > Then I get 405 method not allowed, from viewing JAXRSUtils.findTargetMethod I > can see that resource.getMethodDispatcher().getOperationResourceInfos() > doesn't return this method in this case. > Seems to be a bug. > Note that IntelliJ Idea IDE adds argument annotations to overriden methods by > default (if code is generated via IDE) and that makes it more important issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)