You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Alex Karasulu (JIRA)" <di...@incubator.apache.org> on 2004/10/31 08:07:32 UTC

[jira] Created: (DIREVE-70) complete SEDA protocol provider for LDAP

complete SEDA protocol provider for LDAP
----------------------------------------

         Key: DIREVE-70
         URL: http://issues.apache.org/jira/browse/DIREVE-70
     Project: Directory Eve
        Type: Task
  Components: protocol  
    Reporter: Alex Karasulu
 Assigned to: 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://issues.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


[jira] Commented: (DIREVE-70) complete SEDA protocol provider for LDAP

Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.
     [ http://nagoya.apache.org/jira/browse/DIREVE-70?page=comments#action_55930 ]
     
Alex Karasulu commented on DIREVE-70:
-------------------------------------

Looks like the Add handler was already there.  I confirmed correct operation - works like a champ.  I also added the Delete handler code to the stub that was there.  Confirmed that delete handler works properly. Checked in changes on revision 106731 here:

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



> 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


[jira] Commented: (DIREVE-70) complete SEDA protocol provider for LDAP

Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.
     [ http://nagoya.apache.org/jira/browse/DIREVE-70?page=comments#action_55931 ]
     
Alex Karasulu commented on DIREVE-70:
-------------------------------------

We got the following handlers left to implement:

--> CompareHamdler
--> ExtendedHandler
--> ModifyHandler
--> ModifyDnHandler
--> UnbindHandler

I'll begin working on the ModifyHandler and ModifyDnHandler for now.  The CompareHandler will require a special client to test/confirm correct operation and the ExtendedHandler needs to be properly designed.  We need to figure out how we will enable extended request handling and the registration of extended request hooks.  Right now there may be a few extended requests specific to Eve that we may want to enable like:

--> Sync
--> Shutdown
--> Enable DB Diagnostics
--> Enable New DB Partion
--> Disable New DB Partion

et. cetera...

The UnbindHandler needs more feedback from Trustin and Enrique for us to agree on the SEDA to provider communication mechanism we will use.  One we agree upon this the handler can be implemented in minutes.

> 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


[jira] Commented: (DIREVE-70) complete SEDA protocol provider for LDAP

Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.
     [ http://nagoya.apache.org/jira/browse/DIREVE-70?page=comments#action_55944 ]
     
Alex Karasulu commented on DIREVE-70:
-------------------------------------

Finished and tested the CompareHandler on revision 106783 here:

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



> 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


[jira] Commented: (DIREVE-70) complete SEDA protocol provider for LDAP

Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.
     [ 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


[jira] Commented: (DIREVE-70) complete SEDA protocol provider for LDAP

Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.
     [ http://nagoya.apache.org/jira/browse/DIREVE-70?page=comments#action_55943 ]
     
Alex Karasulu commented on DIREVE-70:
-------------------------------------

Completed ModifyRdn with revision 106776 here:

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



> 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


[jira] Commented: (DIREVE-70) complete SEDA protocol provider for LDAP

Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.
     [ http://nagoya.apache.org/jira/browse/DIREVE-70?page=comments#action_55945 ]
     
Alex Karasulu commented on DIREVE-70:
-------------------------------------

Completed the Unbind operation by having the LdapProtocolProvider constructor take the EventRouter and use that to publish a DisconnectEvent when the Unbind is requested.   Really need to cleanup the implicit session managment within the provider though. 

Check out the changes here in revision 106784:

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

If Trustin figures out a better way to do this then we can just roll back these changes.  Until then I think this is a relatively descent solution.



> 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


[jira] Closed: (DIREVE-70) complete SEDA protocol provider for LDAP

Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.
     [ http://nagoya.apache.org/jira/browse/DIREVE-70?page=history ]
     
Alex Karasulu closed DIREVE-70:
-------------------------------

    Resolution: Fixed

I don't think I will bother with the extended requests for now.  First because I don't know of any that we need which is a published LDAP extension request type and secondly the other extended requests are specific the Eve.  Also how the heck would you test this: there are no tools that I have seen to build and send extended requests.

> 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


[jira] Commented: (DIREVE-70) complete SEDA protocol provider for LDAP

Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.
     [ http://nagoya.apache.org/jira/browse/DIREVE-70?page=comments#action_55929 ]
     
Alex Karasulu commented on DIREVE-70:
-------------------------------------

Search and Bind are pretty much done at this point.  There definately are a few lingering bugs out there though.

> 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