Hi, The problem stems from some example XMBean code that I grafted from the 'Admin & Dev Guide' and managed to break.
The XMBean exposes its JNDI name as an attribute. The setter method for the attribute is responsible for unbinding an existing JNDI name, before binding the new JNDI name that has just been set. Unfortunately at start-up this property is not set, and as a result the unbind operation was failing with a NamingException. This didn't seem to affect the XMBean, however caused other content like WAR and EJB to fail to load. When loading the EAR first, and subsequently deploying the SAR content subsequently the problem is avoided because the WAR/EJB content has successfully been initialised. Thanks and regards, Andrew View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3842625#3842625 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3842625 ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
