On Wed, 20 Feb 2002, David Jencks wrote: > I'm working on some other modifications to Container and I will apply this > patch (if no one objects). > > I think there is a big problem with the deployment order. Right now with > an ear that contains many ejb jars we deploy the jars individually in a > more or less random order. I believe we need to: > > 1. get all the classes in all of the .ear in classloaders > > 2. in a create() step, create each Container and bind it in jndi. Also make > the jsr-77 mbean. This step should do everything possible that doesn't > look at configuration outside the Container we are create()ing. > > 3. in a start() step, resolve the jndi local environments, links, etc, and > then make the container available to calls. This step hooks up all the > configuration that looks outside the current Container. > > Would this fix the ejb-link problem you refer to?
Yes. The class Application is a little missnamed in my opinion because there's a level above required. something that bundles these "Applications" into an "EnterpriseApplication" (what I would call Application) .. Holger _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
