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:05:32 UTC

[jira] Created: (DIREVE-69) Add ability to fire up frontend when a JNDI property is set

Add ability to fire up frontend when a JNDI property is set
-----------------------------------------------------------

         Key: DIREVE-69
         URL: http://issues.apache.org/jira/browse/DIREVE-69
     Project: Directory Eve
        Type: Task
  Components: jndi-provider  
    Reporter: Alex Karasulu
 Assigned to: Alex Karasulu 


Need to make changes to the EveContextFactory to have Eve start up her front end networking layer where LDAP protocol requests are processed.  This issue depends on the SEDA protocol provider being implemented.

-- 
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] Closed: (DIREVE-69) Add ability to fire up frontend when a JNDI property is set

Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.

     [ http://nagoya.apache.org/jira/browse/DIREVE-69?page=history ]
     
Alex Karasulu closed DIREVE-69:
-------------------------------

    Resolution: Fixed

Already done even though protocol provider is only partially implemented at this point.

> Add ability to fire up frontend when a JNDI property is set
> -----------------------------------------------------------
>
>          Key: DIREVE-69
>          URL: http://nagoya.apache.org/jira/browse/DIREVE-69
>      Project: Directory Eve
>         Type: Task
>   Components: jndi-provider
>     Reporter: Alex Karasulu
>     Assignee: Alex Karasulu

>
> Need to make changes to the EveContextFactory to have Eve start up her front end networking layer where LDAP protocol requests are processed.  This issue depends on the SEDA protocol provider being implemented.

-- 
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