[
https://issues.jboss.org/browse/CDI-158?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen commented on CDI-158:
-----------------------------------
The general point is, CDI has Extensions, but you can rewrite CDI stuff only. From a users
perspective and for a coherent platform standpoint, i don't care if this thing is a
EJB, a MDB, JAX-RS service or a CDI Bean. I should be able to operate on them all in the
same way.
This is a tracker item, don't read this as CDI Extensions should include all this and
everyone depend on CDI, but rather Think EE Extension.
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