This bug is fixed in both the 1.0 branch to be releases on 1.0.2 and the 1.5branch to be released for 1.5.0.
Alex On 2/27/07, Alex Karasulu <[EMAIL PROTECTED]> wrote:
This is for you: https://issues.apache.org/jira/browse/DIRSERVER-859 Alex On 2/26/07, Alex Karasulu <[EMAIL PROTECTED]> wrote: > > Looks like you sent this twice. Again file a JIRA issue and I'll start > debugging the problem. Please give us some sample data that shows this > error and if possible a test case to isolate the problem so we can fix it > rapidly. > > Here's something that might help: > > http://directory.apache.org/apacheds/1.0/reporting-bugs.html > > If you use the testcase archetype and then modify the test case to > contain the dataset in the server that reproduces this search bug then we > can get on it fast. > > Just add the tarball of your test project to the JIRA issue you create > for this as an attachment. > > Thanks, > Alex > > > On 2/26/07, marek-apacheds <[EMAIL PROTECTED]> wrote: > > > > Hi > > > > I have installed 1.0.1 version of apache DS. I successfully connected > > to it. When I use filter: > > - (cn=Marek) - ok > > - (!(cn=*)) - ok > > - (!(cn=Marek)) - Failed to resolve primary name for 2.5.4.3 in user > > index lookup [Root exception is javax.naming.NamingException: OID ' > > 2.5.4.3' was not found within the OID registry] > > It is written in documentation at > > http://directory.apache.org/apacheds/1.0/242-ldap-operations-searching.html that > > "not" operator is suported, but I see that it is partially supported. > > Am I doing anything wrong or is it a system bug? > > > > > > Regards > > Marek > > > > > >
