[
https://issues.jboss.org/browse/CDI-220?page=com.atlassian.jira.plugin.sy...
]
Martin Kouba commented on CDI-220:
----------------------------------
Yes. You're right. It's not 100% clear. I myself was confused many times when
reading the spec. Finally I got used to distinguish CDI beans in a way as *Chapter 3.
Programming model* does. Imho we should use *managed POJO beans* and *managed session
beans*.
behaviour of CDI bean @Specializes session bean is undefined
------------------------------------------------------------
Key: CDI-220
URL:
https://issues.jboss.org/browse/CDI-220
Project: CDI Specification Issues
Issue Type: Clarification
Components: Java EE integration
Affects Versions: 1.0, 1.1.EDR1
Reporter: Mark Struberg
Fix For: TBD
The current spec doesn't define what should happen if a CDI bean @Specializes a
session bean, e.g.
@Stateless
public class Horse {..}
@ApplicationScoped @Specializes
public class Trakehner extends Horse {..}
Section 3.2.4 explicitely forbids the other way around. I think we should also treat the
above case as error.
Otherwise we would end up getting different results whether we use @Inject or @EJB to
inject a Horse.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira