[
https://issues.apache.org/jira/browse/CXF-7229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837715#comment-15837715
]
Sergey Beryozkin commented on CXF-7229:
---------------------------------------
That method - I must've added it to bypass Spring AOP Cglib issues, I can see
it from Spring ClassHelper, otherwise it just returns the actual 'cls'.
I don't see though that 'unwrapping' the class is needed for the response
serialization, as far as the runtime is concerned.
This code is only used twice, once in the ContainerResponseContext
implementation, and once - during the serialization.
So I'd like to ask: do you actually *see* something failing :-) ? Or you only
think it will fail ?
thanks
> 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
>
> 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)
