No it is not implemented yet. In fact, some like the EJB container do a form three phase startup.
You'll find there are three reasons for two phase startup. 1) Need to lookup/use something from a different service which won't be in a useful state until it has been started. 2) Need to do something beyond basic config, e.g. bind to jndi or a server socket. 3) Similar to (1) and (2): do some of registry processing, e.g. a jms queue does destinationManger.addQueue() during start. All these are planned to be replaced by microcontainer aspects 1) Dependency Injection 2) Externalization of configuration: | <bean name="whatever" .../> | <bean name="whatever.jndi" bean="JNDIBinding"> | <attribute name="target"><depends name="whatever"/></attribute> | <attribute name="jndiName">some/context/whatever</attribute> | </bean> | 3) This is an aspect of the reverse dependency processing: | <bean name="queue"> | ... | <reverse-dependency name="destinationManager" method="addQueue"/> | </bean> | which means when queue is fully available do destinationManager.addQueue(this); View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861148#3861148 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3861148 ------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
