[
https://issues.apache.org/jira/browse/CXF-7229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15842864#comment-15842864
]
Sergey Beryozkin commented on CXF-7229:
---------------------------------------
That has never been a problem with CXF JAX-RS, and why should we start
unwrapping them all now ? That may break some custom MBWs which do expect the
objects in the form returned by the service code. And any custom MBW which does
need to unwrap the object can do it itself anyway it is not a CXF-level
decision because it does not know how the object is expected to processed by a
custom MBW. We can do an optional unwrapping of the object before passing to
MBW but ClassUnwrapper does not even have a method yet for unwrapping the
objects, hence we'd break those who have already implemented CXF
ClassUnwrapper.
IMHO, the issue which may indeed need to be fixed is to prevent a loss of the
custom annotations.
> ClassHelper usages not replacable by ClassUnwrapper
> ---------------------------------------------------
>
> Key: CXF-7229
> URL: https://issues.apache.org/jira/browse/CXF-7229
> Project: CXF
> Issue Type: Bug
> Reporter: Romain Manni-Bucau
> Assignee: Andriy Redko
> Attachments: proxy-test-case.txt
>
>
> ClassUnwrapper and ClassHelper are pretty close and for an app setting a
> single one should be enough (in particular cause ClassHelper overriding is
> hacky)
> Spotted org.apache.cxf.jaxrs.utils.InjectionUtils#getRawResponseClass for
> instance
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
