[
https://issues.apache.org/jira/browse/DIRSERVER-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny resolved DIRSERVER-1218.
------------------------------------------
Resolution: Fixed
Seems that the lookup operation is working well, whatever parameter you pass :
- '*'
- '+'
- [] (empty array)
or nothing.
The method just returns the expected result.
Some tests have been added for this issue (LookupIT in core-integ)
fixed in :
http://svn.apache.org/viewvc?rev=722254
> Investigate the altered lookup() (returns empty entries) does not cause issues
> ------------------------------------------------------------------------------
>
> Key: DIRSERVER-1218
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1218
> Project: Directory ApacheDS
> Issue Type: Task
> Reporter: Alex Karasulu
> Assignee: Emmanuel Lecharny
> Priority: Critical
> Fix For: 1.5.5
>
>
> Just recently the behavior of Lookup operations changed slightly where an
> explicit request for '*' is required to return all user attributes. If '*'
> or '+' is not specified lookup() operations are returning entries as if '1.1'
> is provided. We may have inadvertantly adapted to this shift to correctly
> deal with the issues it may case.
> Regardless the policy needs to be clearly defined and enforced especially if
> we're going to start using entries returned from lookup operations and
> stuffing them into the target entry fields of OperationContexts to prevent
> redundant lookups.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
