cxf-issues mailing list archives

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

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

Romain Manni-Bucau commented on CXF-7229:
-----------------------------------------

clarification: *this* jira was just to slowly ensure CXF uses a single overridable by the
user "unwrapper" (kind of merge ClassHelper and ClassUnwrapper). The other one (https://issues.apache.org/jira/browse/CXF-7228)
was about ensuring providers are proxy friendly

> 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