-
Bug
-
Resolution: Done
-
Major
-
2.0.3.Final
-
None
-
None
I have the following session bean
@Stateless public class MockLoginActionBean extends LoginActionBean { } its superclass
public class LoginActionBean implements LoginAction { }
and an interface
public interface LoginAction { }
According to the spec., the bean types of an instance of a MockLoginActionBean should only be Object, MockLoginActionBean and LoginActionBean, however also LoginAction is contained in the set returned by javax.enterprise.inject.spi.BeanAttributes.getTypes(). This holds whether the superclass (LoginActionBean) is a session bean or not, even if the interface LoginAction is annotated @Remote or @Local.
- is related to
-
CDITCK-363 Fix session bean specialization tests
- Resolved
- relates to
-
CDI-388 Session bean specialization example is not valid
- Closed
-
CDITCK-350 Create a test for invalid session bean specialization
- Resolved
-
CDITCK-351 Improve tests for Bean types of a session bean
- Resolved