We're going to quickly run smack into the problem where references to services like datasources are expressed in terms of JNDI names and the referencing component is being deployed before these referenced services. What I do now is VERY VERY hacky. I take the JNDI name of the datasource and construct an Kernel name from it. We talked before about requiring services that register in JNDI to also create a generic JndiBinding bean. Another thought I had, what about integrating/federating JNDI with the Kernel Registry? ANyways, this should be a topic for a different thread. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992104#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...