You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Andy McCright (JIRA)" <ji...@apache.org> on 2018/10/19 17:03:00 UTC

[jira] [Resolved] (CXF-7868) MP Rest Client does not honor providers registered via MP Config

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

Andy McCright resolved CXF-7868.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 3.2.7
                   3.3.0

Test and fix that providers registered via MP Config are correctly registered when invoking the MP Rest Client.  Also tests that properties specified in RestClientBuilder are honored.  Lastly, adds the "invokedMethod" property to the ClientRequestContext - this is an MP Rest Client 1.2 requirement.

> MP Rest Client does not honor providers registered via MP Config
> ----------------------------------------------------------------
>
>                 Key: CXF-7868
>                 URL: https://issues.apache.org/jira/browse/CXF-7868
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 3.2.6
>            Reporter: Andy McCright
>            Assignee: Andy McCright
>            Priority: Major
>             Fix For: 3.3.0, 3.2.7
>
>
> The MP Rest Client spec says that I should be able to specify providers via MP Config using comma-separated provider class names with the config key of {{<clientInterfaceName>/mp-rest/providers}}. It also specifies that provider priorities can be set using MP Config with the config key of {{<clientInterfaceName>/mp-rest/providers/<providerClassName>/priority}}.
> Neither of these properties have any effect in CXF.
> Note that the MP Rest Client spec mentions this requirement for implementors, but does not currently test it in the TCK - this is being addressed in MP Rest Client Issue [126|https://github.com/eclipse/microprofile-rest-client/issues/126].



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)