anonymous wrote : he real solution is to create your own DependencyItem implementation | like I've been telling you to over a year now. And I've been telling you that EE injection requirements are not simple... Are you sure the DependencyItem stuff will work since EJB and PC ref's metadata may be incomplete or even ambiguous? Does a DependencyItem get queried EVERY TIME any arbitrary thing is deployed or when ANY arbitrary thing changes state within the MC? I also worry about a dependency item matching and picking up the wrong reference because an inner deployment scope hasn't been processed/deployed yet. I don't understand why I have to add the dependencies to the deployment to make this work. The subdeployments of an EAR are not going to be deployed piecemeal. Also, we're not going to make configuration more complicated for the user for the edge cases 90% of people don't care about. Meaning, we're not going to require a mapped-name with @EJB or @PersistenceContext refs. i.e. requiring them to specify a mapped-name. Where is there documentation on how dependency items work? The Javadoc isn't very helpful ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082220#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...