[weld-issues] [JBoss JIRA] Commented: (CDITCK-210) org.jboss.jsr299.tck.tests.implementation.enterprise.definition.Pitbull (Stateful session bean) 's @Remove method not part of EJB's business interface

org.jboss.jsr299.tck.tests.implementation.enterprise.definition.Pitbull (Stateful session bean) 's @Remove method not part of EJB's business interface ------------------------------------------------------------------------------------------------------------------------------------------------------ Key: CDITCK-210 URL: https://issues.jboss.org/browse/CDITCK-210 Project: CDI TCK Issue Type: Bug Security Level: Public(Everyone can see) Components: Tests Affects Versions: 1.0.4.Final Environment: Generic Java Platform Reporter: Bob Nettleton Assignee: Jozef Hartinger A Stateful session bean defined in the following test suite: org.jboss.jsr299.tck.tests.implementation.enterprise.definition includes a @Remove method that is not part of the Session Bean's Business interface. The bean in question is: org.jboss.jsr299.tck.tests.implementation.enterprise.definition.Pitbull According to the javadoc for the Remove annotation: http://download.oracle.com/javaee/6/api/javax/ejb/Remove.html This annotation must be placed on a method that is also a part of the Session Bean's business interface. This issue can cause problems with the portability of this test application and test suite, since different application servers may fail at deployment time with this type of EJB-related error. I request that either the Session Bean be modified to add this method to the business interface, or that the tests listed below be removed from the TCK: org.jboss.jsr299.tck.tests.implementation.enterprise.definition.EnterpriseBeanDefinitionTest.testStatelessMustBeDependentScoped [testng] org.jboss.jsr299.tck.tests.implementation.enterprise.definition.EnterpriseBeanViaXmlTest.testEjbDeclaredInXmlNotSimpleBean [testng] org.jboss.jsr299.tck.tests.implementation.enterprise.definition.EnterpriseBeanDefinitionTest.testSingletonWithDependentScopeOK [testng] org.jboss.jsr299.tck.tests.implementation.enterprise.definition.EnterpriseBeanDefinitionTest.testEnterpriseBeanClassLocalView [testng] org.jboss.jsr299.tck.tests.implementation.enterprise.definition.EnterpriseBeanDefinitionTest.testObjectIsInAPITypes [testng] org.jboss.jsr299.tck.tests.implementation.enterprise.definition.EnterpriseBeanDefinitionTest.testBeanWithStereotype [testng] org.jboss.jsr299.tck.tests.implementation.enterprise.definition.EnterpriseBeanDefinitionTest.testDefaultName [testng] org.jboss.jsr299.tck.tests.implementation.enterprise.definition.EnterpriseBeanDefinitionTest.testBeanWithNamedAnnotation [testng] org.jboss.jsr299.tck.tests.implementation.enterprise.definition.EnterpriseBeanDefinitionTest.testBeanWithQualifiers [testng] org.jboss.jsr299.tck.tests.implementation.enterprise.definition.EnterpriseBeanDefinitionTest.testBeanWithScopeAnnotation [testng] org.jboss.jsr299.tck.tests.implementation.enterprise.definition.EnterpriseBeanDefinitionTest.testSingletonWithApplicationScopeOK [testng] org.jboss.jsr299.tck.tests.implementation.enterprise.definition.EnterpriseBeanDefinitionTest.testBeanTypesAreLocalInterfacesWithoutWildcardTypesOrTypeVariablesWithSuperInterfaces [testng] org.jboss.jsr299.tck.tests.implementation.enterprise.definition.EnterpriseBeanDefinitionTest.testConstructorAnnotatedInjectCalled [testng] org.jboss.jsr299.tck.tests.implementation.enterprise.definition.EnterpriseBeanDefinitionTest.testRemoteInterfacesAreNotInAPITypes Another test suite: org.jboss.jsr299.tck.tests.context.dependent.ejb also has this problem in the following Stateful session EJB: org.jboss.jsr299.tck.tests.context.dependent.ejb.Fox In addition to the list above, the following tests also appear to be affected by this issue: org.jboss.jsr299.tck.tests.context.dependent.ejb.DependentContextEjbTest.testDestroyingEjbDestroysDependentSimples [testng] org.jboss.jsr299.tck.tests.context.dependent.ejb.DependentContextEjbTest.testDestroyingEjbDestroysDependents