Hi

I faced a comparable error like Vikas (see below) with modification of
object classes (from a CLI client).
Can anybody point me to a place in the code where JUnit tests for JNDI
clients are hosted ?
Is it "apacheds/trunk/main/src/test/org/apache/ldap/server/jndi" (there
is one test case class present)?
I would like to create/add some test cases to verify behaviour for LDAP
clients (currently I concentrate on the "user experienece" ;-).
Including one for the situation Vicas described.

And a question: If I raise a defect in JIRA: What is the preferred way
to demonstrate it:
a) JNDI program/Test case (pure Java)
b) LDIF file with operation sequence (pure LDAP)

Greetings from Hamburg,
Stefan

---

All
Apache (apacheds-main-0.9.jar)
Java - JNDI to access ldap


ModificationItem[] mods = new ModificationItem[1];
Attribute mod = new BasicAttribute(uniqueMember_ATTR, userDN);
mods[0] =  new ModificationItem(DirContext.ADD_ATTRIBUTE, mod);
DirContext dc = null;
dc = lc.open();
dc.modifyAttributes(theDN, mods);

The above lines of code seems to not add additional values to the attribute.
The existing attribute values are getting replaced by this new value.

eg-
Group already has two users "john' and 'Matt'
To add 'Jack' to the group will cause  the other two to loose their
group assignments.

These work just fine with other ldap providers like openldap.
Any ideas comments?

thx

[ Post a follow-up to this message ]

Stefan Zoerner wrote:

> Hi
>
> I faced a comparable error like Vikas (see below) with modification of
> object classes (from a CLI client).
> Can anybody point me to a place in the code where JUnit tests for JNDI
> clients are hosted ?
> Is it "apacheds/trunk/main/src/test/org/apache/ldap/server/jndi"
> (there is one test case class present)?

Check out the core/src/test/org/apache/ldap/server/jndi also.  The main
just has the main executable in it along with code that glues various
services like the Kerberos MINA Service with LDAP.  The core is kept
free of other dependencies and is the heart for all the LDAP stuff after
protocol message decoding.

> I would like to create/add some test cases to verify behaviour for
> LDAP clients (currently I concentrate on the "user experienece" ;-).
> Including one for the situation Vicas described.
>
> And a question: If I raise a defect in JIRA: What is the preferred way
> to demonstrate it:
> a) JNDI program/Test case (pure Java)
> b) LDIF file with operation sequence (pure LDAP)
>
It's nice to have a simple JNDI TestCase then we can just add it to all
the test cases.  Plus it gives us code to reproduce the error.

Alex

[ Post a follow-up to this message ]