cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CXF-1994) An attempt to deregister custom providers fails.
Date Tue, 20 Jan 2009 15:52:59 GMT

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

Sergey Beryozkin commented on CXF-1994:
---------------------------------------

I actually  removed this method in 2.2. In tests one can do ProfiderFactory.getInstance().clearProviders().


Are you thinking of dynamically registering/unregistering custom providers at runtime ?
Or would you like to do some more fine-grained unregistration during tests ?


> An attempt to deregister custom providers fails.
> ------------------------------------------------
>
>                 Key: CXF-1994
>                 URL: https://issues.apache.org/jira/browse/CXF-1994
>             Project: CXF
>          Issue Type: Bug
>          Components: REST
>            Reporter: Chaitanya Choleti
>         Attachments: sources.zip, tests.war
>
>
> 1) The method ProviderFactory.deregisterEntityProvide(Object o) does not actually derigister
a custom provider.
> 2) Consider that the first problem is fixed. Now, if a custom provider which implements
both MessageBodyReader and MessageBodyWriter is set and the method deregisterEntityProvide
is called it deregisters it as a MessageBodyReader and returns without deregistering it as
a MessageBodyWriter.
> 3) There is no provision to deregister providers which implement ExceptioMapper.
> Please open the attached zip file to find the suggested fix.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message