[
https://issues.jboss.org/browse/CDI-667?page=com.atlassian.jira.plugin.sy...
]
Romain Manni-Bucau commented on CDI-667:
----------------------------------------
Think EJB 3.2 2.9 section already solves it:
{quote}An EJB packaged into a CDI bean archive and not annotated with
javax.enterprise.inject.Vetoed
annotation, is considered a CDI-enabled bean. The CDI container performs
dependency injection on all instances of CDI-enabled session and message-driven
beans{quote}
So whatever mode it is the EJB will integrate with CDI if CDI is on.
Session beans in trimmed bean archive
-------------------------------------
Key: CDI-667
URL:
https://issues.jboss.org/browse/CDI-667
Project: CDI Specification Issues
Issue Type: Clarification
Reporter: Tomas Remes
Fix For: 2.0 .Final
Currently it is not obvious how session beans should be treated in trimmed bean archive.
In other words are they considered as beans or not?
IMO we should state that there are discovered as beans, but it's questionable.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)