[
https://issues.apache.org/jira/browse/DIRSERVER-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14512349#comment-14512349
]
Emmanuel Lecharny commented on DIRSERVER-1934:
----------------------------------------------
Thanks a lot of the unit test, Lucas. It clearly demonstrates the issue.
I have checked the server's code, and what happens is that the request controls
are never injected into the {{BindOperationContext}}, thus no response controls
are sent back. Injectting the {{BindRequest}} controls into the
{{BindOperationContext}} magically (well, logically ;-) solve the issue.
I'll check the other operations, I suspect we have the exact same problem.
> 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)
