You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Kurt T Stam (JIRA)" <ju...@ws.apache.org> on 2010/01/04 15:27:54 UTC

[jira] Closed: (JUDDI-317) CLONE -UDDI LDAP backend Implementation for Apache juddi

     [ https://issues.apache.org/jira/browse/JUDDI-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kurt T Stam closed JUDDI-317.
-----------------------------

    Resolution: Won't Fix
      Assignee: Kurt T Stam  (was: Steve Viens)

Unless we get push and support from the community I don't think we're going to implement this. Please reopen if things change.

> CLONE -UDDI LDAP backend Implementation for Apache juddi
> --------------------------------------------------------
>
>                 Key: JUDDI-317
>                 URL: https://issues.apache.org/jira/browse/JUDDI-317
>             Project: jUDDI
>          Issue Type: New Feature
>         Environment: JDK1.3.1 with any Servlet 2.3 complaint Application Server/Servlet Engine and an LDAPv3 server.
>            Reporter: fengwei
>            Assignee: Kurt T Stam
>
> This is a "Directory backend implementation" for Apache juddi. 
> It consists of a LDAP DataStore and LDAP Authenticator for Apache juddi, using which Apache juddi can be configured to setup a UDDIv2 server against any standard, LDAPv3 compliant directory backend. 
> The code is attached in the ZIP file. 
> Please go through the 'Apache juddi-LDAP README' file in the ZIP which provides more details on the implementation and deployment.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.