directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DIRAPI-130) The extended responses are not decoded into their respective type
Date Thu, 20 Jun 2013 13:24:22 GMT

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

Emmanuel Lecharny updated DIRAPI-130:
-------------------------------------

    Fix Version/s:     (was: 1.0.0-RC1)
                   1.0.0-M18
    
> 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-M18
>
>
> 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

Mime
View raw message