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/11/09 08:34:32 UTC
[jira] Created: (DIREVE-84) implement eve.net.passthru for SEDA frontend
implement eve.net.passthru for SEDA frontend
--------------------------------------------
Key: DIREVE-84
URL: http://nagoya.apache.org/jira/browse/DIREVE-84
Project: Directory Eve
Type: New Feature
Components: jndi-provider
Reporter: Alex Karasulu
Assigned to: Alex Karasulu
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 eve.net.disable.protocol. 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:
eve.net.passthru
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:
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] Updated: (DIREVE-84) implement eve.net.passthru for SEDA frontend
Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.
[ http://nagoya.apache.org/jira/browse/DIREVE-84?page=history ]
Alex Karasulu updated DIREVE-84:
--------------------------------
Fix Version: 0.8.0
> implement eve.net.passthru for SEDA frontend
> --------------------------------------------
>
> Key: DIREVE-84
> URL: http://nagoya.apache.org/jira/browse/DIREVE-84
> 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 eve.net.disable.protocol. 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:
> eve.net.passthru
> 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:
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-84) implement eve.net.passthru for SEDA frontend
Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.
[ http://nagoya.apache.org/jira/browse/DIREVE-84?page=history ]
Alex Karasulu closed DIREVE-84:
-------------------------------
Resolution: Fixed
Checked in changes to this on revision 111398 here:
http://svn.apache.org/viewcvs?view=rev&rev=111398
> implement eve.net.passthru for SEDA frontend
> --------------------------------------------
>
> Key: DIREVE-84
> URL: http://nagoya.apache.org/jira/browse/DIREVE-84
> 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 eve.net.disable.protocol. 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:
> eve.net.passthru
> 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:
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