DirContext.search() with null Name results in NPE
-------------------------------------------------
Key: DIREVE-295
URL: http://issues.apache.org/jira/browse/DIREVE-295
Project: Directory Server
Type: Improvement
Components: jndi-provider
Reporter: Enrique Rodriguez
Assigned to: Alex Karasulu
Priority: Minor
This is a minor issue I am marking as an improvement since the JNDI API doesn't
appear to say explicitly what the behavior is, so I'm entering this issue to
document it. The issue is that if you supply a null Name as the name to search
in DirContext.search() you get a NPE. If you supply a null String, however, it
is treated as the empty String, which indicates a search at the current
context's name. IMO, a null Name should be treated like the empty String.
So, a null Name fails with NPE:
Name name = null;
NamingEnumeration answer = ctx.search( name, matchAttrs, attrIDs );
java.lang.NullPointerException
at org.apache.ldap.common.name.LdapName.addAll(LdapName.java:527)
at
org.apache.ldap.server.jndi.ServerContext.buildTarget(ServerContext.java:843)
at
org.apache.ldap.server.jndi.ServerDirContext.search(ServerDirContext.java:488)
...
But, a null String will work fine:
String name = null;
NamingEnumeration answer = ctx.search( name, matchAttrs, attrIDs );
Which is the same as the empty String, which works fine, too;
String name = "";
NamingEnumeration answer = ctx.search( name, matchAttrs, attrIDs );
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
