I don't want static class initialization for the containers from the MC. This will work fine when beans are running inside somebody else's container with the services from the wrapping container but will fail for JBoss's internal beans where dependencies need to be statisfied and ordered.
The ordering needs to be done by the MC - negating any deadlocks. Pure JBossAOP ClassNotFoundException x.Y NestedException: NameNotFoundException: java:/jaas/SecurityDomain With the MC it will wait for the jndi binding or you will get an error about incomplete dependencies DeploymentException: Unsatisfied dependency for 'Name' NestedException: SecurityDomain not deployed View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861652#3861652 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3861652 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
