Re: adding entries using jndi

ameyas wrote:


Why not just use native JNDI instead of netscape's JNDI service provider?

javax.naming.*;
javax.naming.directory.*;
javax.naming.ldap.*;


Well after looking at your code it seems that you don't know how LDAP
really works. A piece of data doesn't go directly into the directory. An
attribute is stored in the directory with the piece of data as its value.

Example: You may want to store phone numbers for all your users. This
is a standard attribute called telephoneNumber and it is already created
to store integer values. Assigning a particular user's telephoneNumber
attribute a telphone number value would store that user's phone number
so anyone searching for that user could read his/her phone number. You
don't just store the number itself. It has to belong to someone.

LDAP uses object classes to define the objects that can exist. These are
similar to classes in Java or C++. An instance of an object class is an
object (user, printer, server, etc.) just like an instance of a Java
class is an object. The LDAP object contains various attributes such as
first name, last name, email address, etc. This is similar to how a
object in Java may have member fields.


Well it depends on what the integer is supposed to represent. If it is
just some arbitrary integer you wouldn't have any reason to store that
anyway. There are many standard attributes already defined that can hold
integer values. I mentioned telephoneNumber above but there are others
such as a fax number or employeeID. However, when working with LDAP
with JNDI integers are just treated as strings so you won't ever have a
need to create Integers.


Yes you will if you want to connect to that specific location in the
directory and create/delete an object or modify an existing one.


a number by itself doesn't mean anything and is not designed to be put
into a directory on its own. You must create an object such as a user
object or computer object since you are working with ADS. And then
modify one of the predefined attributes. Since you don't seem to know
how LDAP works I suggest reading up on it first and also taking a look
at the ADS schema by using the Active Directory Schema MMC snap-in. I
presume this is available in ADAM. By browsing the directory schema you
can see what type of attributes a typical user can have. Also, if you
use ADSIedit you can see how attributes for a preexisting user are setup.


You can't do this until myRandomInt is created using
ctx.createSubcontext() but again, there is no reason to store just an
integer. For the code below, ChangeObject is a class I created with the
'name' field being the distinguished name of the object.

public String createEntry(ChangeObject object) {
    try {
        ctx.createSubcontext(object.name, object.attribSet);
        return null;
    } catch (NameAlreadyBoundException Ex) {
        return "Object already exists with that name.";
    } catch (InvalidAttributesException Ex) {
         return "Missing attributes.";
    } catch (NamingException Ex) {
        return Ex.getMessage();
    } catch (Exception Ex) {
        return Ex.toString();
    }
}

To modify an existing object do something like this:
public String modEntry(ChangeObject object) {
    LdapName nodeName = object.name;
    BasicAttributes attrs = object.attribSet;
    int operation = object.op;
    try {
        if (operation == 0)
            ctx.modifyAttributes(nodeName,
            InitialDirContext.ADD_ATTRIBUTE, attrs); else if (operation == 1)
            ctx.modifyAttributes(nodeName,
            InitialDirContext.REPLACE_ATTRIBUTE, attrs);
        else if (operation == 2)
            ctx.modifyAttributes(nodeName,
InitialDirContext.REMOVE_ATTRIBUTE, attrs);
        return null;
    } catch (NamingException Ex) {
            return Ex.getMessage();
    }
}


reply to the group if you need additional help