[
https://issues.apache.org/jira/browse/DIRAPI-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny resolved DIRAPI-133.
--------------------------------------
Resolution: Invalid
This is already the case : the client creates an ExtendedRequest, which
contains an instance of response, which is correlated to the request already.
> 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-RC1
>
>
> 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
