geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Forrest Xia (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GERONIMO-6043) module init order doesn't always work due to gbean dependencies
Date Wed, 02 May 2012 05:41:03 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-6043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266359#comment-13266359
] 

Forrest Xia commented on GERONIMO-6043:
---------------------------------------

After 3.0-beta-1 release, seems we need to re-evaluate the issue of this jira reported, any
new comment?
                
> module init order doesn't always work due to gbean dependencies
> ---------------------------------------------------------------
>
>                 Key: GERONIMO-6043
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6043
>             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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message