[JBoss JIRA] Created: (CDITCK-166) Test should be on 1.0.1 exclude list: org.jboss.jsr299.tck.tests.context.application.ejb.ApplicationContextSharedTest.testApplicationScopeActiveDuringCallToEjbTimeoutMethod
by Kyle Grucci (JIRA)
Test should be on 1.0.1 exclude list: org.jboss.jsr299.tck.tests.context.application.ejb.ApplicationContextSharedTest.testApplicationScopeActiveDuringCallToEjbTimeoutMethod
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: CDITCK-166
URL: https://jira.jboss.org/browse/CDITCK-166
Project: CDI TCK
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Tests
Affects Versions: 1.0.1.Final
Environment: All
Reporter: Kyle Grucci
Priority: Minor
Fix For: 1.0.1.Final
The following test needs to be added to the 1.0.1 TCK exclude list...
org.jboss.jsr299.tck.tests.context.application.ejb.ApplicationContextSharedTest.testApplicationScopeActiveDuringCallToEjbTimeoutMethod
I just ran the 1.0.1 Final 299 TCK (with the latest exclude list that you have posted) with the following results...
827 Passed
1 Failed
The 1 failure is from this test...
org.jboss.jsr299.tck.tests.context.application.ejb.ApplicationContextSharedTest.testApplicationScopeActiveDuringCallToEjbTimeoutMethod
>From earlier emails, it appears that this test should be on the 1.0.1 exclude list per issue # CDITCK-157.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] Created: (CDITCK-121) Bug in BeanManagerTest
by Gurkan Erdogdu (JIRA)
Bug in BeanManagerTest
----------------------
Key: CDITCK-121
URL: https://jira.jboss.org/jira/browse/CDITCK-121
Project: CDI TCK
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Gurkan Erdogdu
public void testGetPassivationCapableBeanById()
{
Bean<?> bean = getCurrentManager().getBeans(Cow.class).iterator().next();
assert PassivationCapable.class.isAssignableFrom(bean.getClass());
......
Bean SPI class does not extends PassivationCapable interface. Therefore, PassivationCapable.class.isAssignableFrom(bean.getClass()); must not be true.
OWB beans do not implement PassivationCapable interface as a default. Therefore this is specific to Weld.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months