[
https://issues.apache.org/jira/browse/WINK-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731828#action_12731828
]
Nadav Fischer commented on WINK-103:
------------------------------------
I agree with this, so I committed the patch but with slight changes, mainly
that the verification that a method has either @Path or an http method
designator occurs in createMethodMetadata instead of parseMethods and a warning
is issued in such a case. I hope it's ok with you.
> Method invoked but no HttpMethod
> --------------------------------
>
> Key: WINK-103
> URL: https://issues.apache.org/jira/browse/WINK-103
> Project: Wink
> Issue Type: Bug
> Components: Server
> Affects Versions: 0.1
> Reporter: Bryant Luk
> Assignee: Nadav Fischer
> Fix For: 0.1
>
> Attachments: WINK-103.patch
>
>
> If a non-HttpMethod annotated annotation is not present but a JAX-RS regular
> annotation is present, then the method will get invoked for any matching
> method. wink-server/EncodedTest will fail one test because of this but ran
> into it during one of the integration tests.
> {code}
> @Path("/abcd")
> public class Resource {
> @Produces("text/plain")
> public Response invokeMeAnytime() {
> }
> }
> {code}
> Invoke a GET to /abcd with Accept header of text/plain.
> The problem is with a) Method metadata records are added to the root resource
> even if there isn't a HttpMethod (which is the easy if check fix) and b) the
> filtering HTTP method algorithm assumes that if you don't have a HttpMethod,
> you must be a subresource locator I think.
> The real fix to me is to get rid of the Set returned of HttpMethod since it
> is not possible with JAX-RS to have a method be annotated with greater than 1
> @HttpMethod annotated annotations.
> I consider this a must fix for 0.1 so I'll go ahead and mark it that way.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
