Mea culpa. Sorry I was just getting a little frustrated - the problem appears to have come from some example XMBean code from the 'Admin & Dev Guide' that I 'enhanced' in my own app.
A seemingly innuocuous NamingException was being thrown when trying to unbind a non existent JNDI name when the XMBean was first loaded. This apparently resulted in other non XMBean content failing to be loaded successfully down the track. The XMBean exposes its JNDI name as an attribute, and as part of the initialisation this attribute is set (also resulting in an attempt to deregister an exitsing JNDI name, and regsiter the new name). I guess that the moral of the story is to always investigate what may appear to be an unrelated harmless problem. Sorry for the static. Thanks and regards, Andrew View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3842623#3842623 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3842623 ------------------------------------------------------- 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
