You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Chaitanya Choleti (JIRA)" <ji...@apache.org> on 2009/03/04 06:49:56 UTC

[jira] Closed: (CXF-1994) An attempt to deregister custom providers fails.

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

Chaitanya Choleti closed CXF-1994.
----------------------------------

    Resolution: Invalid

This method is removed now.

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