[ http://issues.apache.org/jira/browse/GERONIMO-948?page=all ]
David Jencks updated GERONIMO-948:
----------------------------------
Fix Version: Wish List
(was: 1.0-M5)
This is too hard and will require a lot of thought. Implementing
unloadRecursive, startRecursive, stopRecursive in ConfigurationManager is easy,
but figuring out what should happen if someone calls unloadRecursive on a
configuration that is in use by other configurations or is started or calling
unloadRecursive twice is going to take a lot of thought.
> Need reference counting on load/start of configurations
> -------------------------------------------------------
>
> Key: GERONIMO-948
> URL: http://issues.apache.org/jira/browse/GERONIMO-948
> Project: Geronimo
> Type: Bug
> Components: kernel
> Versions: 1.0-M5
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: Wish List
>
> When you load/start a configuration, it loads and starts its ancestors and
> keeps track of what it loaded and what it started, and undoes this when you
> stop/unload it. This will create big problems if you
> load A
> load B (with a common parent)
> unload A (unloading common parent of B)
> unload B
> Solution appears to be to count how many descendants use a config and only
> stop/unload if count reaches 0. Code to do this should probably be in the
> ConfigurationManager.
--
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
