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 Wed, 25 Jan 2017 11:55:26 GMT

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

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

there still are some cases where classhelper is used but not the unwrapper. Since unwrapper
is per bus it should always override the helper which is static (and not designed to be overriden).
Idea of this task is to ensure ClassHelper can be deleted and replaced by a default unwrapper
more or less to ensure applications setting an unwrapper doesnt need to hack the helper as
well. It is typically the case for the response (if you return a proxied jpa entity for instance
your unwrapper is bypassed)

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

Mime
View raw message