[
https://issues.apache.org/jira/browse/CXF-8174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995272#comment-16995272
]
Andriy Redko commented on CXF-8174:
-----------------------------------
Hey [~kopkar2], could you please submit test case(s) or test project so we
could reproduce the issue? I am not able to reconstruct the case from the
description, the `TestService` methods are not even taken into consideration
(due to https://issues.apache.org/jira/browse/CXF-7670) so I am not able to
observe the behavior you are reporting. The test case or small project would be
very helpful. Thank you.
> Incorrect service method resolution
> -----------------------------------
>
> Key: CXF-8174
> URL: https://issues.apache.org/jira/browse/CXF-8174
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
> Affects Versions: 3.2.8, 3.3.0
> Reporter: Rafał Kopka
> Priority: Major
>
> Assume JAX-RS resource classes:
> {code}
> public interface TestService<REQ extends com.test.BaseRequest, RES extends
> com.test.BaseResponse> {
> RES process(REQ request);
> }
> {code}
> {code}
> public interface MyTestService extends
> TestService<com.test.MyTestServiceRequest, com.test.MyTestServiceResponse> {
> @Override
> @POST
> @Path("record")
> @Valid
> com.test.MyTestServiceResponse process(com.test.MyTestServiceRequest
> request);
> }
> {code}
> When we call MyTestService, CXF resolves method from TestService
> {code}
> com.test.BaseResponse process(com.test.BaseRequest request)
> {code}
> This causes Jackson deserialization error due to unknown properties sent in
> {code}
> com.test.MyTestServiceResponse
> {code}
> This occurs due to changes in OperationResourceInfoComparator (CXF-7946)
> where parameter class names are compared.
> Explicit package in the sample is due to the fact that there is an easy
> workaround - remove all extends from parent interface. This won't work if
> your package is anything after java.lang
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
