[
https://issues.apache.org/jira/browse/DIRSERVER-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14511995#comment-14511995
]
lucas theisen commented on DIRSERVER-1934:
------------------------------------------
[~akiran], yes, this still is an issue. I just committed the attached patch
(unit test) so that you can see for yourself. The test in question is
currently {{@Ignore}}'d so that it will not interfere with the build.
{code}
$ svn commit -m "DIRSERVER-1934: added in the patch unit test to demonstrate
the issue, currently ignored to not fail the build"
Adding core-integ/src/test/java/org/apache/directory/server/core/api
Adding
core-integ/src/test/java/org/apache/directory/server/core/api/LdapCoreSessionConnectionTest.java
Transmitting file data .
Committed revision 1675983.
{code}
> 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)
