directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <>
Subject [jira] Closed: (DIREVE-84) implement for SEDA frontend
Date Thu, 09 Dec 2004 16:09:30 GMT
     [ ]
Alex Karasulu closed DIREVE-84:

    Resolution: Fixed

Checked in changes to this on revision 111398 here:

> implement for SEDA frontend
> --------------------------------------------
>          Key: DIREVE-84
>          URL:
>      Project: Directory Eve
>         Type: New Feature
>   Components: jndi-provider
>     Reporter: Alex Karasulu
>     Assignee: Alex Karasulu
>      Fix For: 0.8.0

> The Kerberos server and Eve both will naturally start up SEDA in their standalone configurations.
 When coupled together they should share the same instance of the framework.  This means one
or both may need to adopt the instance created by the other.  
> Eve already has a JNDI property for supressing SEDA initialization to make Eve operate
without the network frontend code.  The property is  For the time
being until container details are worked out we will add an environment property for passing
a SEDA Frontend referrence to the JNDI provider via the environment.  A key like the following
may be used:
> This would supress creation making the JNDI provider use that frontend instead.

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