I have an mbean which is a child of mx4j.AbstractDynamicMBean which depends on a session bean. The deployment descriptor fragment below should cause it to not deploy until the EJB container deploys:
| <mbean code="com.portblue.mgmt.SweeperManager" | name="com.portblue.mgmt:service=SweeperManager"> | <depends>jboss.j2ee:module=portblue.jar,service=EjbModule</depends> | </mbean> | But the SweeperManager mbean's constructor is called before the ejb container is completely deployed, which is not my understanding of what should be happening. I have guessed that rather than the constructor, it is the start() lifecycle method that gets called when dependencies are ready. Is this the case, rather than the ctor? If it is the start() method, is there an easier way to hook into the JBoss JMX lifecycle methods than implementing the raw ServiceSupport interface? I notice there are abstract helper classes documented for ServiceMBeans, and that there is a similar helper for dynamic mbeans not documented anywhere, and which does not appear to do anything (org.jboss.mx.util.DynamicMBeanSupport). All of this is on JBoss 3.2.6. Any clues would be greatly appreciated. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3852839#3852839 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3852839 ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
