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] [Resolved] (DIRAPI-150) A search done with a wrong baseDN does not return a NO_SUCH_ERROR
Date Tue, 23 Jul 2013 06:58:49 GMT

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

Emmanuel Lecharny resolved DIRAPI-150.
--------------------------------------

    Resolution: Not A Problem

Yes, this is on purpose. 

When doing a lookup() or a search(), if the base DN does not exist, you will simply get no
result.

Is this a problem for you ?
                
> A search done with a wrong baseDN does not return a NO_SUCH_ERROR
> -----------------------------------------------------------------
>
>                 Key: DIRAPI-150
>                 URL: https://issues.apache.org/jira/browse/DIRAPI-150
>             Project: Directory Client API
>          Issue Type: Bug
>    Affects Versions: 1.0.0-M18
>            Reporter: Emmanuel Lecharny
>            Priority: Blocker
>             Fix For: 1.0.0-RC1
>
>
> When we do a search with a non existing baseDN, we get back an empty cursor instead of
getting an LdapNoSuchObjectException.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message