cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-7229) ClassHelper usages not replacable by ClassUnwrapper
Date Fri, 27 Jan 2017 17:23:25 GMT

    [ https://issues.apache.org/jira/browse/CXF-7229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15843146#comment-15843146
] 

Sergey Beryozkin commented on CXF-7229:
---------------------------------------

As we've discussed earlier here, ClassUnwrapper, if registered as a bus property, is used
for unwrapping proxy classes whenever the classes unwrapping is done via ClassHelper and as
I said I'm not sure what else we can do. 

CXF-7228 was about ensuring providers (as opposed to entities) get their classes unwrapped
- the code you mentioned was updated.

In this JIRA you also referred to the code which might cause the entity serialization issues
due to the possible loss of the annotations which might help MBW to do the work, which so
far we can't reproduce, you have your test working :-).


> 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)

Mime
View raw message