&quot;adrian(a)jboss.org&quot; wrote : The next step is what the ENC deployer does about the | dependencies. | | e.g. If I want a DataSource, the DataSource should be deployed | before I start. | | The way this should work is that the object that wants an ENC | should be deployed through the Controller, either as a POJO | or JMX with the relevant dependency: | | | | <bean name="MyEJB"> | | <property name="enc"> | | <inject bean="MyEJB,ENCFactory" property="enc"/> | | </property> | | etc. | | | | The ENC deployer creates the ENCFactory using the metadata | from the scope it was provided with. That's nice for basic beans, but as I showed before, it is just not so simple for Java EE land where the ENC -> Global JNDI binding cannot be determine by the available metadata. To put it in other terms, the available metadata may not be enough to construct a Kernel identity or exact JNDI binding. The referenced component will need to be searched for based on the position of the component in the deployment and based on the little of metadata that was made available by the application developer. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972296#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...