The way it's currently done, contexts that depend on something outside MC have no way of being notified that their external dependency is/was resolved. The context will move fwd the next time something is added to MC, but there is no API to simply ping the kernel. Perhaps a better approach with JNDI registry - if you have access to MC - is to install a bean into MC after the JNDI entry was added, where the bean would simply/only provide a supply with a JNDI name. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081881#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...