You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Carsten D (Jira)" <ji...@apache.org> on 2019/08/23 09:49:00 UTC
[jira] [Created] (CXF-8097) Equal candidates for handling the
current request (HEAD / GET)
Carsten D created CXF-8097:
------------------------------
Summary: Equal candidates for handling the current request (HEAD / GET)
Key: CXF-8097
URL: https://issues.apache.org/jira/browse/CXF-8097
Project: CXF
Issue Type: Bug
Components: JAX-RS
Affects Versions: 3.3.3, 3.3.2
Reporter: Carsten D
I have just migrated a very outdated Spring backend to Spring 5 and with it upgraded CXF to first 3.3.2 and just now 3.3.3. I have a REST service class defining two different methods with the same path defined via {{javax.ws.rs.Path}} annotation, differentiated by {{javax.ws.rs.HEAD}} and {{javax.ws.rs.GET}} annotations. Both methods are annotated with {{@Produces(MediaType.APPLICATION_OCTET_STREAM)}}.
When this method is called I get (redacted):
{{WARN [JAXRSUtils.compare:129] Both ServiceRestImpl#getFile and ServiceRestImpl#getFileAsHeadRequest are equal candidates for handling the current request which can lead to unpredictable results}}
The differentiation works: HEAD requests are handled by the {{@HEAD}} annotated and GET requests by the {{@GET}} annotated one (this has always worked). Therefore the warning is false but will severely clutter production log output, possibly affect performance.
Relevant dependencies:
* Spring framework 5.1.8
* "org.apache.cxf", "cxf-rt-rs-service-description", "3.3.3"
* "javax.servlet", "javax.servlet-api", "4.0.1"
* "javax.ws.rs", "javax.ws.rs-api", "2.0.1"
I'd appreciate support. May be linked to:
* CXF-7670
* CXF-6684
--
This message was sent by Atlassian Jira
(v8.3.2#803003)