geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan (JIRA)" <>
Subject [jira] [Commented] (GERONIMO-6043) module init order doesn't always work due to gbean dependencies
Date Tue, 19 Jul 2011 05:39:58 GMT


Ivan commented on GERONIMO-6043:

Commit changes to trunk at r1148178. Currently, I moved ApplicationJndi as the last GBean
while init-order is configured in DD. As ApplicationJndi is a common GBean, which is dependent
by each EJB and web module GBean. Personally, this is somewhat a workaround solution, as once
the dependency relations are changed, we might face the order problem again. I have some better
ideas for this, but have not tried them
a. Sort the gbeans in the configuration by references and dependencies, and use start not
startRecusive method.
b. Move the codes in the doStart methods in the web module/ejb module/ejb ws GBean to another
method, which means those modules are not deployed to contains even if the gbeans start. We
need an extra action to do this. It might somewhat be used as lazy loading. 
Anyway, considering that we are near the 3.0 release, let's consider this in the next release
if possible

> module init order doesn't always work due to gbean dependencies
> ---------------------------------------------------------------
>                 Key: GERONIMO-6043
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: core
>    Affects Versions: 3.0
>            Reporter: David Jencks
>             Fix For: 3.0
> The new start modules in listed order flag in ee 6 doesn't always work because some gbean
dependencies conflict with it.  The biggest is the owb initialization.  We need to always
use the openejb owb integration to make this manageable.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message