cxf-issues mailing list archives

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


Romain Manni-Bucau commented on CXF-7229:

The loss of custom annotations is expected by several frameworks so this is not something
which will change I fear (or that CXF can control). Regarding your point, if you take my previous
answer you will see it is ok since the MBW will keep current behavior by default until an
unwrapper is register and in such a case the unwrapping belongs to the impl so it sounds perfectly
valid to me. Most of the time the unwrapper will remove well know proxies the MBW will never
handle like spring, weld, owb proxies. If you worry about this case (once again I think the
risk it breaks anything is very very low) we can still enrich the ClassUnwrapper with a dedicated
method probably.

> ClassHelper usages not replacable by ClassUnwrapper
> ---------------------------------------------------
>                 Key: CXF-7229
>                 URL:
>             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

View raw message