[cdi-dev] [JBoss JIRA] Commented: (CDI-158) Extension support for non CDI beans
[
https://issues.jboss.org/browse/CDI-158?page=com.atlassian.jira.plugin.sy...
]
David Lloyd commented on CDI-158:
---------------------------------
I agree, this would destroy performance. This looks nice from a top-down perspective but
the harsh reality is that if you want performance, you have to provide features based on
what the underlying software is actually capable of doing efficiently, and try to meet the
user requirements from that direction. And if you're clever enough, you can manage
it. But this isn't it.
Extension support for non CDI beans
-----------------------------------
Key: CDI-158
URL: https://issues.jboss.org/browse/CDI-158
Project: CDI Specification Issues
Issue Type: Tracker
Components: Java EE integration
Affects Versions: 1.0
Reporter: Aslak Knutsen
Fix For: 1.1 (Proposed)
CDI Extensions in EE6 can only rewrite/change/work upon CDI registered beans. This should
be extended to include _any_ EE component.
e.g.
* Change/Add @Resource InjectionPoint in a EJB
* Change/Add @Path on JAX-RS Resource handlers
* Change/Add @MassageDriven on a MDB
* Change/Add JPA Annotations
* Change/Add @TransactionAttributes on EJBs
* Change/Add @RunAs on EJBs
* Change/Add @WebService on EJBs
* Change/Add @WebServlet etc. on Servlets
* Change/Add @Timer on EJB
++++
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira