You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cxf.apache.org by "Sergey Beryozkin (JIRA)" <ji...@apache.org> on 2015/01/20 13:17:34 UTC

[jira] [Resolved] (CXF-6208) Support registering JAX-RS providers as Classes in all cases

     [ https://issues.apache.org/jira/browse/CXF-6208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergey Beryozkin resolved CXF-6208.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 3.1.0
                   3.0.4
         Assignee: Sergey Beryozkin

http://git-wip-us.apache.org/repos/asf/cxf/commit/ec9df9cd

> Support registering JAX-RS providers as Classes in all cases
> ------------------------------------------------------------
>
>                 Key: CXF-6208
>                 URL: https://issues.apache.org/jira/browse/CXF-6208
>             Project: CXF
>          Issue Type: Improvement
>          Components: JAX-RS
>            Reporter: Sergey Beryozkin
>            Assignee: Sergey Beryozkin
>            Priority: Minor
>             Fix For: 3.0.4, 3.1.0
>
>
> Sometimes providers can be registered not as concrete custom objects but just as Class and furthemore, they may have constructors expecting JAX-RS contexts being injected. This is currently supported in the implementation of JAX-RS 2.0 Client API, in all other cases a provider is registered either as an instance or as a specific Constructor. Support for registering such providers as Class in all the cases would make things simpler



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)