directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (DIRNAMING-3) JNDI test framework
Date Sun, 29 Aug 2004 00:48:20 GMT
The following comment has been added to this issue:

     Author: Alex Karasulu
    Created: Sat, 28 Aug 2004 5:46 PM
Well I was thinking about an extention to the default TestCase that added the extra assertXXX()
methods you mentioned in your comment above.  I actually found myself writing a slew of JNDI
object comparison code to determine if objects that go through the round trip encode decode
cycle are still the same.  

Then I got smarter and started adding this logic to the equals() methods on Attrribute, Attrributes
implemetnations and in other places to deal with these values.  Take a look at these files
here for example:

Look way towards the ends of these files for the equals() methods:

And here take a look at this private method here for comparing two modification items:

private boolean equals( ModificationItem item0, ModificationItem item1 ) ===>

View this comment:

View the issue:

Here is an overview of the issue:
        Key: DIRNAMING-3
    Summary: JNDI test framework
       Type: Test

     Status: In Progress
   Priority: Major

    Project: Directory naming

   Assignee: Phil Steitz
   Reporter: Phil Steitz

    Created: Sat, 21 Feb 2004 11:28 AM
    Updated: Sat, 28 Aug 2004 5:46 PM

Create a test unit test framework for JNDI implementations and add test classes to cover all
implementation classes in o.a.naming.

Also create tests for thread/classloader-context bindings, permissions, and other features
supported in o.a.naming.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message