4:04 p.m.
Mark Struberg created CDI-220:
---------------------------------
Summary: 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.1.EDR1, 1.0
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 Drakener 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
4:06 p.m.
[
https://issues.jboss.org/browse/CDI-220?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg updated CDI-220:
------------------------------
Description:
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.
was:
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 Drakener 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.
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
3:51 a.m.
[
https://issues.jboss.org/browse/CDI-220?page=com.atlassian.jira.plugin.sy...
]
Martin Kouba commented on CDI-220:
----------------------------------
Section 3.1.4. Specializing a managed bean states:
"If a bean class of a managed bean X is annotated @Specializes, then the bean class
of X must directly extend the bean class of another managed bean Y. Then X directly
specializes Y, as defined in Section 4.3, “Specialization”.
*If the bean class of X does not directly extend the bean class of another managed bean,
the container automatically detects the problem and treats it as a definition
error.*"
So your code (Trakehner = managed bean, Horse = session bean) should result in definition
error.
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
5:29 a.m.
[
https://issues.jboss.org/browse/CDI-220?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg commented on CDI-220:
-----------------------------------
Well Martin, I fear the CDI spec is not 100% clear as it says that session beans also must
be treated as managed beans... It would be more clear if it would state 'Managed CDI
bean' or anything like that.
Look at "3.1.1. Which Java classes are managed beans?"
A top-level Java class is a managed bean if it is defined to be a
managed bean by any other Java EE specification,
Which a session bean certainly is,
isn't?
hmm but it also states:
It is not annotated with an EJB component-defining annotation or
declared as an EJB bean class in ejb-jar.xml.
The confusion gets deeper because EJBs must also be held as Bean<T> in the
BeanManager as required by the spec.
JSR-316 (EE umbrella) btw seems to catched that as well and explicitly ranted about it ;)
"CDI-style managed beans"
We use this term to refer to classes that become managed beans per the rules
in the CDI specification (JSR-299), thus excluding managed beans declared using
the @ManagedBean annotation as well as EJB session beans, both of which would
be managed beans even in the absence of CDI.
*scratches his head*
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
6:31 a.m.
[
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
5125
days inactive
5126
days old
4 comments
2 participants
participants (2)
-
Mark Struberg (JIRA) -
Martin Kouba (JIRA)