Server may try to start modules in an order that won't work
-----------------------------------------------------------
Key: GERONIMO-3840
URL: https://issues.apache.org/jira/browse/GERONIMO-3840
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: core
Affects Versions: 2.1, 2.1.1, 2.2
Reporter: David Jencks
Assignee: David Jencks
Fix For: 2.2
The server is loading and then starting the modules in the order they are
listed in the config.xml, which is random. The specific case I've run into
where this doesn't work is when a builder has a customized default environment
set in config.xml. The property editor that can deal with this data type is
installed in a gbean in geronimo-gbean-deployer: this module must be started to
register the property editor.
If a module such as j2ee-deployer is loaded before geronimo-gbean-deployer is
started, the property editor will not be available. Loading a module only
loads, not starts, its ancestors.
The solution I've thought of is to sort the modules by dependency so
dependencies are loaded and started before the dependent module. This seems to
work fine.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
