Issue 4008 - [JLDAP] LDAPConnection class does not handle null LDAPSearchQueue and LDAPSearchConstraints in search method
Summary: [JLDAP] LDAPConnection class does not handle null LDAPSearchQueue and LDAPSea...
Status: RESOLVED SUSPENDED
Alias: None
Product: JLDAP
Classification: Unclassified
Component: JLDAP (show other issues)
Version: unspecified
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: OpenLDAP project
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-06 22:04 UTC by jglynn@bjc.org
Modified: 2021-08-03 17:48 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description jglynn@bjc.org 2005-09-06 22:04:54 UTC
Full_Name: John Glynn
Version: CVS HEAD
OS: java
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (159.251.88.4)


Using a null LDAPSearchQueue as a parameter in the search method throws a
NullPointerException.  This behavior does not match that of the wrapped novell
LDAPConnection. Additionally, there does not seem to be any way of constructing
a LDAPSearchQueue since there are no public constructors for those, so this
method really should handle nulls. Changing the wrapped call from
search(...,queue,...) to
search(...,(queue==null?null:queue.getWrappedObject()),...) works like Novell
intended.

Comment 1 Kurt Zeilenga 2005-09-08 19:02:34 UTC
moved from Incoming to Contrib
Comment 2 Kurt Zeilenga 2005-10-12 00:59:15 UTC
changed notes
Comment 3 Rastogi Arpit 2007-11-28 11:41:38 UTC
I tried to replicate the above problem using the following code snippet 
 
..........
...........
LDAPSearchQueue queue =lc.search(searchBase,searchScope,searchFilter,null,false,null,null);
..............
..............
 
But I am not able to find a NullPointerException as stated in the bug . It is working fine for me .
Please use the latest Jldap code and do let me know if I need to do something more to replicate the problem . 
Comment 4 npalani@openldap.org 2007-12-13 06:01:47 UTC
changed notes
changed state Open to Feedback
Comment 5 npalani@openldap.org 2007-12-13 06:02:03 UTC
changed notes
Comment 6 npalani@openldap.org 2007-12-13 06:02:07 UTC
changed notes
Comment 7 npalani@openldap.org 2007-12-13 06:03:06 UTC
John,

Could you please check the same issue with the latest source an come back? As
Arpit said above, we are not able to duplicate the issue at all.

Regards,
Palaniappan.
Comment 8 npalani@openldap.org 2007-12-13 06:03:15 UTC
changed notes
Comment 9 npalani@openldap.org 2008-01-25 10:32:08 UTC
Please , look at the bug . As it has been for a long time in the feedback state
.
Please check with the latest source code if the problem is replicated and if it
does not please move the bug to closed state . We will be moving it to suspend
state after a couple of weeks time . If you find it replicated please feel free
to reopen the bug .
Comment 10 npalani@openldap.org 2009-07-06 06:09:49 UTC
changed notes
changed state Feedback to Suspended
Comment 11 OpenLDAP project 2014-08-01 21:03:27 UTC
Moving this as suspended, as the reporter has not come back.

Regards,
Palaniappan N.