Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Date: Wed, 10 Oct 2012 14:03:06 +0000 (UTC)
From: "Forrest Xia (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Message-ID: <1707198435.19780.1349877786550.JavaMail.jiratomcat@arcas>
In-Reply-To: <21606991.299.1309642461786.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (GERONIMO-6043) module init order doesn't always
 work due to gbean dependencies
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/GERONIMO-6043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Forrest Xia updated GERONIMO-6043:
----------------------------------

    Fix Version/s:     (was: 3.0.0)
                   3.0.1
    
> 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.0
>            Reporter: David Jencks
>             Fix For: 3.0.1
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira