Mailing-List: contact directory-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List"
 <directory-dev@incubator.apache.org>
Message-ID: <1918035911.1101576199583.JavaMail.apache@nagoya>
Date: Sat, 27 Nov 2004 09:23:19 -0800 (PST)
From: "Alex Karasulu (JIRA)" <directory-dev@incubator.apache.org>
To: directory-dev@incubator.apache.org
Subject: [jira] Commented: (DIREVE-70) complete SEDA protocol provider for
 LDAP
In-Reply-To: <2014250684.1099206452020.JavaMail.apache@nagoya>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

     [ http://nagoya.apache.org/jira/browse/DIREVE-70?page=comments#action_55932 ]
     
Alex Karasulu commented on DIREVE-70:
-------------------------------------

Completed and tested Modify handler in revision 106734 here: 

https://svn.apache.org/viewcvs.cgi?rev=106734&view=rev

Note:

--> Turns out attributes that are not valid attributes of the schema blow up as they should but the exceptions are cryptic and not the right ones according to the LDAP JNDI provider guide.
--> Also looks like the changes for a unrecognized attribute's addition are persisted.  Directory then freaks everytime it sees that attribute crippling the entry.  

Fixing these problems are part of the cross cutting concern for Schema checking which are covered by other issues.

> complete SEDA protocol provider for LDAP
> ----------------------------------------
>
>          Key: DIREVE-70
>          URL: http://nagoya.apache.org/jira/browse/DIREVE-70
>      Project: Directory Eve
>         Type: Task
>   Components: protocol
>     Reporter: Alex Karasulu
>     Assignee: Alex Karasulu

>
> We need to finish up the SEDA protocol provider for LDAP.  We already have most of the code in different places that we can assemble this from.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira