I need to have deployment unit aware injection / annotations, so stuff like:
@PersistenceUnit
| public void setEntityManagerFactory(EntityManagerFactory emf)
| {
| this.emf = emf;
| }
works within a MC bean while obeying the scoping rules.
@EJB annotations need the same thing. Now
AbstractEjbReferenceValueMetadata.getTargetJndiName throws scoping out the
window, which is wrong.
I think it boils down to knowing the cause of a MC bean install. While the
current resolvers work on deployment unit (as being the root cause) this might
now be truly the proper abstraction.
For the moment it would be great to actually know the deployment unit which is
causing a MC bean install.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210689#4210689
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210689
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
