geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <...@geronimo.apache.org>
Subject [jira] Updated: (GERONIMO-1351) Separate Derby network listener from system-databsae configuration
Date Tue, 13 Dec 2005 19:27:47 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-1351?page=all ]

Aaron Mulder updated GERONIMO-1351:
-----------------------------------

    Component: security
      Summary: Separate Derby network listener from system-databsae configuration  (was: Separate
Derby network listener from system-databsae ocnfiguration)

> Separate Derby network listener from system-databsae configuration
> ------------------------------------------------------------------
>
>          Key: GERONIMO-1351
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1351
>      Project: Geronimo
>         Type: Bug
>   Components: databases, security
>     Versions: 1.0-M5
>     Reporter: Aaron Mulder
>      Fix For: 1.1

>
> Currently the system-database configuraiton is required (for EJB timer, JMS, etc.). 
The configuration starts a Derby network listener.  There's no need for a network listener
to support these core features.  It seems like it would be nice to separate the network listener
so it could be disabled independently without crippling the server, and only enabled when
remote access to the embedded database was desirable.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message