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

Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2013/04/22 11:29:15 UTC

[jira] [Resolved] (DIRAPI-130) The extended responses are not decoded into their respective type

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

Emmanuel Lecharny resolved DIRAPI-130.
--------------------------------------

    Resolution: Fixed

Fixed with http://svn.apache.org/r1470331
                
> The extended responses are not decoded into their respective type
> -----------------------------------------------------------------
>
>                 Key: DIRAPI-130
>                 URL: https://issues.apache.org/jira/browse/DIRAPI-130
>             Project: Directory Client API
>          Issue Type: Bug
>    Affects Versions: 1.0.0-M16
>            Reporter: Emmanuel Lecharny
>             Fix For: 1.0.0-RC1
>
>
> When we receive an extendedResponse, we create a generic ExtendedResponseImpl, instead of a specific response associated with the request we sent. This is wrong, as it forbids the decoding of the ResponseValue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira