Uploaded image for project: 'Directory Client API'
  1. Directory Client API
  2. DIRAPI-133

Correlate an extendedResponse with its associated request, when we don't have a responseName

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Invalid
    • Affects Version/s: 1.0.0-M16
    • Fix Version/s: 1.0.0-M18
    • Labels:
      None

      Description

      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.

        Activity

        Hide
        elecharny Emmanuel Lecharny added a comment -

        Closing the resolved issues.

        Show
        elecharny Emmanuel Lecharny added a comment - Closing the resolved issues.
        Hide
        elecharny Emmanuel Lecharny added a comment -

        This is already the case : the client creates an ExtendedRequest, which contains an instance of response, which is correlated to the request already.

        Show
        elecharny Emmanuel Lecharny added a comment - This is already the case : the client creates an ExtendedRequest, which contains an instance of response, which is correlated to the request already.

          People

          • Assignee:
            elecharny Emmanuel Lecharny
            Reporter:
            elecharny Emmanuel Lecharny
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development