directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRSERVER-1603) Doing a lookup requiring an AT which is inherited by some of the entry's AT does not return anything
Date Tue, 18 Jan 2011 21:11:58 GMT

    [ https://issues.apache.org/jira/browse/DIRSERVER-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983376#action_12983376
] 

Emmanuel Lecharny commented on DIRSERVER-1603:
----------------------------------------------

I don't think it's a regression. It was an issue a long time ago for Searches, and has been
fixed. I don't think we fixed it for lookup (not 100% sure).

However, we were smart enough to create the common OperationContext to be used by search and
lookup, with all the needed method to handle this case, except that we never used it for lookups...
This is what I 'm currently doing.

Not really a big problem...

> Doing a lookup requiring an AT which is inherited by some of the entry's AT does not
return anything
> ----------------------------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-1603
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1603
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 1.5.7
>            Reporter: Emmanuel Lecharny
>            Priority: Critical
>             Fix For: 2.0-M1
>
>
> If we do a lookup, listing some attributes to get in the returned entry, and if we have
AT which inherit the given ATs, we don't get anything.
> For instance,        
> Entry entry = connection.lookup( "cn=test,ou=system", "name" );
> return an empty entry.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message