Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Date: Thu, 20 Jun 2013 13:24:21 +0000 (UTC)
From: "Emmanuel Lecharny (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Message-ID: <JIRA.12643535.1366363337831.148474.1371734661270@arcas>
In-Reply-To: <JIRA.12643535.1366363337831@arcas>
References: <JIRA.12643535.1366363337831@arcas>
Subject: [jira] [Updated] (DIRAPI-133) Correlate an extendedResponse with
 its associated request, when we don't have a responseName
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Emmanuel Lecharny updated DIRAPI-133:
-------------------------------------

    Fix Version/s:     (was: 1.0.0-RC1)
                   1.0.0-M18
    
> Correlate an extendedResponse with its associated request, when we don't have a responseName
> --------------------------------------------------------------------------------------------
>
>                 Key: DIRAPI-133
>                 URL: https://issues.apache.org/jira/browse/DIRAPI-133
>             Project: Directory Client API
>          Issue Type: Bug
>    Affects Versions: 1.0.0-M16
>            Reporter: Emmanuel Lecharny
>             Fix For: 1.0.0-M18
>
>
> It's possible for an extendedResponse to not have a responseName (the OID). It makes it impossible to associate the decoded message to a specific extendedResponse, unless we admit that this response is associated with the request that has been submitted.
> As we know the messageId, we may retrieve the request and know what is the type of response we have. This has to be implemented.

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