[
https://issues.apache.org/jira/browse/CXF-6847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15230071#comment-15230071
]
Sergey Beryozkin edited comment on CXF-6847 at 4/7/16 10:54 AM:
----------------------------------------------------------------
Hi Jim
Do you have @Options set on a sub-resource ? If yes - does the main resource
have some other non-subresource locator method (GET, POST, etc) which matches
the request path ?
If yes - then @Options will not be matched and the worst part about it will be
spec-compliant. I'll explain later if it is indeed the case.
was (Author: sergey_beryozkin):
Hi Jim
Do you have @Options set on a sub-resource ? If yes - does the main resource
have some other non-subresource locator method (GET, POST, etc) which matches
the request path ?
> Http OPTIONS doesn't work when keep.subresource.candidates is set to true
> value
> -------------------------------------------------------------------------------
>
> Key: CXF-6847
> URL: https://issues.apache.org/jira/browse/CXF-6847
> Project: CXF
> Issue Type: Task
> Affects Versions: 3.1.5
> Reporter: Jim Ma
> Fix For: 3.2.0
>
>
> From JAXRS 2.0 Spec section 3.5, it requires the following behavior .
> On receipt of an OPTIONS request an implementation MUST either:
> 1. Call a method annotated with a request method designator for OPTIONS or,
> if none present,
> 2. Generate an automatic response using the metadata provided by the JAX-RS
> annotations on the match-
> ing class and its methods.
> This doesn't work when we set keep.subresource.candidates flag to true
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
