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 2015/04/25 10:57:38 UTC

[jira] [Resolved] (DIRSERVER-1934) LdapCoreSessionConnection does not include controls in response

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

Emmanuel Lecharny resolved DIRSERVER-1934.
------------------------------------------
    Resolution: Fixed

The controls weren't injected into the {{BindOperationContext}} instance. Fixed with http://svn.apache.org/r1676001

> LdapCoreSessionConnection does not include controls in response
> ---------------------------------------------------------------
>
>                 Key: DIRSERVER-1934
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1934
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 2.0.0-M16
>            Reporter: lucas theisen
>         Attachments: DIRSERVER-1934.patch
>
>
> This may not be a big issue as LdapCoreSessionConnection appears to only be useful for embedded ldap instances, but it does make for painful unit testing.  Many of my unit tests were failing due to missing controls in the response, and as soon as I switched to LdapNetworkConnection it all went away.  As a workaround, this will likely work though if your unit tests require LdapNetworkConnection, that means they could fail due to port collisions...  
> I could slap together a quick unit test if it would be helpful.
> As a workaround, use LdapNetworkConnection for now.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)