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-512) non-reference gbean dependencies
Date Thu, 04 Aug 2005 02:52:35 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-512?page=all ]

Aaron Mulder updated GERONIMO-512:
----------------------------------

    Fix Version: 1.0
    Description: 
Currently there is no way to make gbeans start in a particular order unless they have a reference
to each other.  This is unsatisfactory as for instance one might open a server socket the
other wants to connect to.  Also, jndi refs are not reflected in the gbean dependency graph.

So far the best idea seems to be to add a list of dependencies (object names or their successors)
to GBeanData, and add these to the dependency manager on startup (and presumably remove them
on shutdown).

  was:
Currently there is no way to make gbeans start in a particular order unless they have a reference
to each other.  This is unsatisfactory as for instance one might open a server socket the
other wants to connect to.  Also, jndi refs are not reflected in the gbean dependency graph.

So far the best idea seems to be to add a list of dependencies (object names or their successors)
to GBeanData, and add these to the dependency manager on startup (and presumably remove them
on shutdown).

    Environment: 

> non-reference gbean dependencies
> --------------------------------
>
>          Key: GERONIMO-512
>          URL: http://issues.apache.org/jira/browse/GERONIMO-512
>      Project: Geronimo
>         Type: New Feature
>   Components: kernel
>     Versions: 1.0-M3
>     Reporter: David Jencks
>      Fix For: 1.0

>
> Currently there is no way to make gbeans start in a particular order unless they have
a reference to each other.  This is unsatisfactory as for instance one might open a server
socket the other wants to connect to.  Also, jndi refs are not reflected in the gbean dependency
graph.
> So far the best idea seems to be to add a list of dependencies (object names or their
successors) to GBeanData, and add these to the dependency manager on startup (and presumably
remove them on shutdown).

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