JSR 346: Contexts and Dependency Injection for Java EE 1.1 TCK Coverage

20091101

Contents

Chapter Summary
Section Summary
Coverage Detail
Unmatched Tests
Unversioned Tests
Test Group Summary

Coverage Distribution

 
 
 
 
 
 
 
 
 
 

Chapter Summary

Chapter Assertions Testable Total Tested Total Tests Tested
(problematic)
Tested
(working)
Coverage %
2 Concepts1331101101420110100,00%
3 Programming model234224223290022399,55%
4 Inheritance and specialization908484118084100,00%
5 Dependency injection, lookup, and EL276263250343025095,06%
6 Scopes and contexts224195190249019097,44%
7 Lifecycle of contextual instances6156506505089,29%
8 Decorators6865639606396,92%
9 Interceptor bindings57525267052100,00%
10 Events93837913007995,18%
11 Portable extensions374358322429032289,94%
12 Packaging and Deployment78575783057100,00%
Total16881547148020120148095,67%

Section Summary

SectionAssertionsTestableTotal TestedTested
(problematic)
Tested
(working)
Coverage %
2 Concepts76606100,00%
2.1 Functionality provided by the container to the bean00000
2.2 Bean types22202100,00%
2.2.1 Legal bean types121212012100,00%
2.2.2 Restricting the bean types of a bean111111011100,00%
2.2.3 Typecasting between bean types11101100,00%
2.3 Qualifiers00000
2.3.1 Built-in qualifier types33303100,00%
2.3.2 Defining new qualifier types41101100,00%
2.3.3 Declaring the qualifiers of a bean44404100,00%
2.3.4 Specifying qualifiers of an injected field22202100,00%
2.3.5 Specifying qualifiers of a method or constructor parameter55505100,00%
2.4 Scopes32202100,00%
2.4.1 Built-in scope types65505100,00%
2.4.2 Defining new scope types42202100,00%
2.4.3 Declaring the bean scope33303100,00%
2.4.4 Default scope55505100,00%
2.5 Bean EL names11101100,00%
2.5.1 Declaring the bean EL name44404100,00%
2.5.2 Default bean names77707100,00%
2.5.3 Beans with no name21101100,00%
2.6 Alternatives11101100,00%
2.6.1 Declaring an alternative76606100,00%
2.7 Stereotypes54404100,00%
2.7.1 Defining new stereotypes61101100,00%
2.7.1.1 Declaring the default scope for a stereotype22202100,00%
2.7.1.2 Specifying interceptor bindings for a stereotype44404100,00%
2.7.1.3 Declaring a @Named stereotype53303100,00%
2.7.1.4 Declaring an @Alternative stereotype11101100,00%
2.7.1.5 Stereotypes with additional stereotypes32202100,00%
2.7.2 Declaring the stereotypes for a bean55505100,00%
2.7.3 Built-in stereotypes10000
2.8 Problems detected automatically by the container74404100,00%
3 Programming model00000
3.1 Managed beans55505100,00%
3.1.1 Which Java classes are managed beans?101010010100,00%
3.1.2 Bean types of a managed bean11101100,00%
3.1.3 Declaring a managed bean76606100,00%
3.1.4 Specializing a managed bean77707100,00%
3.1.5 Default name for a managed bean11101100,00%
3.2 Session beans10870787,50%
3.2.1 EJB remove methods of session beans44404100,00%
3.2.2 Bean types of a session bean44404100,00%
3.2.3 Declaring a session bean66606100,00%
3.2.4 Specializing a session bean22202100,00%
3.2.5 Default name for a session bean11101100,00%
3.3 Producer methods131313013100,00%
3.3.1 Bean types of a producer method44404100,00%
3.3.2 Declaring a producer method131313013100,00%
3.3.3 Specializing a producer method33303100,00%
3.3.4 Default name for a producer method22202100,00%
3.4 Producer fields141313013100,00%
3.4.1 Bean types of a producer field44404100,00%
3.4.2 Declaring a producer field99909100,00%
3.4.3 Default name for a producer field11101100,00%
3.5 Disposer methods55505100,00%
3.5.1 Disposed parameter of a disposer method33303100,00%
3.5.2 Declaring a disposer method101010010100,00%
3.5.3 Disposer method resolution44404100,00%
3.6 Resources20000
3.6.1 Declaring a resource108808100,00%
3.6.2 Bean types of a resource55505100,00%
3.7 Additional built-in beans66606100,00%
3.8 Bean constructors11101100,00%
3.8.1 Declaring a bean constructor88808100,00%
3.9 Injected fields33303100,00%
3.9.1 Declaring an injected field22202100,00%
3.10 Initializer methods76606100,00%
3.10.1 Declaring an initializer method77707100,00%
3.11 The default qualifier at injection points11101100,00%
3.12 Vetoing types11101100,00%
3.13 The qualifier @Named at injection points22202100,00%
3.14 @New qualified beans363535035100,00%
4 Inheritance and specialization00000
4.1 Inheritance of type-level metadata403636036100,00%
4.2 Inheritance of member-level metadata363636036100,00%
4.3 Specialization54404100,00%
4.3.1 Direct and indirect specialization98808100,00%
5 Dependency injection, lookup, and EL21101100,00%
5.1 Modularity54404100,00%
5.1.1 Declaring selected alternatives for a bean deployment archive37363203288,89%
5.1.2 Enabled and disabled beans10000
5.1.3 Inconsistent specialization11101100,00%
5.1.4 Inter-module injection18171601694,12%
5.2 Typesafe resolution00000
5.2.1 Performing typesafe resolution121212012100,00%
5.2.2 Unsatisfied and ambiguous dependencies121212012100,00%
5.2.3 Legal injection point types33303100,00%
5.2.4 Assignability of raw and parameterized types99909100,00%
5.2.5 Primitive types and null values44404100,00%
5.2.6 Qualifier annotations with members31101100,00%
5.2.7 Multiple qualifiers44404100,00%
5.3 EL Name resolution22202100,00%
5.3.1 Ambiguous EL names33303100,00%
5.4 Client proxies53303100,00%
5.4.1 Unproxyable bean types77707100,00%
5.4.2 Client proxy invocation32202100,00%
5.5 Dependency injection15141201285,71%
5.5.1 Injection using the bean constructor44404100,00%
5.5.2 Injection of fields and initializer methods42423803890,48%
5.5.3 Destruction of dependent objects11101100,00%
5.5.4 Invocation of producer or disposer methods66606100,00%
5.5.5 Access to producer field values22202100,00%
5.5.6 Invocation of observer methods44404100,00%
5.5.7 Injection point metadata25252402496,00%
5.5.8 Bean metadata161616016100,00%
5.6 Programmatic lookup55505100,00%
5.6.1 The Instance interface17171601694,12%
5.6.2 The built-in Instance64404100,00%
5.6.3 Using AnnotationLiteral and TypeLiteral22202100,00%
6 Scopes and contexts00000
6.1 The Contextual interface42202100,00%
6.1.1 The CreationalContext interface73303100,00%
6.2 The Context interface151414014100,00%
6.3 Normal scopes and pseudo-scopes83303100,00%
6.4 Dependent pseudo-scope111111011100,00%
6.4.1 Dependent objects77707100,00%
6.4.2 Destruction of objects with scope @Dependent109909100,00%
6.4.3 Dependent pseudo-scope and Unified EL21101100,00%
6.5 Contextual instances and contextual references00000
6.5.1 The active context object for a scope22202100,00%
6.5.2 Contextual instance of a bean43303100,00%
6.5.3 Contextual reference for a bean55505100,00%
6.5.4 Contextual reference validity21101100,00%
6.5.5 Injectable references21101100,00%
6.5.6 Injectable reference validity210000,00%
6.6 Passivation and passivating scopes11101100,00%
6.6.1 Passivation capable beans14980888,89%
6.6.2 Passivation capable dependencies6640466,67%
6.6.3 Passivating scopes31101100,00%
6.6.4 Validation of passivation capable beans and dependencies252525025100,00%
6.7 Context management for built-in scopes00000
6.7.1 Request context lifecycle262626026100,00%
6.7.2 Session context lifecycle88808100,00%
6.7.3 Application context lifecycle181717017100,00%
6.7.4 Conversation context lifecycle28252402496,00%
6.7.5 The Conversation interface141414014100,00%
7 Lifecycle of contextual instances00000
7.1 Restriction upon bean instantiation00000
7.2 Container invocations and interception242222022100,00%
7.3 Lifecycle of contextual instances00000
7.3.1 Lifecycle of managed beans22202100,00%
7.3.2 Lifecycle of stateful session beans32202100,00%
7.3.3 Lifecycle of stateless session and singleton beans32202100,00%
7.3.4 Lifecycle of producer methods55505100,00%
7.3.5 Lifecycle of producer fields44404100,00%
7.3.6 Lifecycle of resources20191301368,42%
8 Decorators32202100,00%
8.1 Decorator beans7640466,67%
8.1.1 Declaring a decorator11101100,00%
8.1.2 Decorator delegate injection points101010010100,00%
8.1.3 Decorated types of a decorator77707100,00%
8.2 Decorator enablement and ordering121111011100,00%
8.3 Decorator resolution44404100,00%
8.3.1 Assignability of raw and parameterized types for delegate injection points99909100,00%
8.4 Decorator invocation151515015100,00%
9 Interceptor bindings00000
9.1 Interceptor binding types33303100,00%
9.1.1 Interceptor binding types with additional interceptor bindings32202100,00%
9.1.2 Interceptor bindings for stereotypes32202100,00%
9.2 Declaring the interceptor bindings of an interceptor54404100,00%
9.3 Binding an interceptor to a bean111111011100,00%
9.4 Interceptor enablement and ordering141313013100,00%
9.5 Interceptor resolution101010010100,00%
9.5.1 Interceptors with multiple bindings22202100,00%
9.5.2 Interceptor binding types with members65505100,00%
10 Events00000
10.1 Event types and qualifier types98808100,00%
10.2 Observer resolution64404100,00%
10.2.1 Assignability of type variables, raw and parameterized types66606100,00%
10.2.2 Event qualifier types with members21101100,00%
10.2.3 Multiple event qualifiers22202100,00%
10.3 Firing events44404100,00%
10.3.1 The Event interface99909100,00%
10.3.2 The built-in Event77707100,00%
10.4 Observer methods65505100,00%
10.4.1 Event parameter of an observer method44404100,00%
10.4.2 Declaring an observer method99909100,00%
10.4.3 Conditional observer methods33303100,00%
10.4.4 Transactional observer methods76606100,00%
10.5 Observer notification151111011100,00%
10.5.1 Observer method invocation context440000,00%
11 Portable extensions40000
11.1 The Bean interface87707100,00%
11.1.1 The Decorator interface44404100,00%
11.1.2 The Interceptor interface66606100,00%
11.1.3 The ObserverMethod interface76606100,00%
11.2 The Producer and InjectionTarget interfaces19161401487,50%
11.3 The BeanManager object6650583,33%
11.3.1 Obtaining a reference to the CDI container55505100,00%
11.3.2 Obtaining a contextual reference for a bean33303100,00%
11.3.3 Obtaining an injectable reference6650583,33%
11.3.4 Obtaining a CreationalContext22202100,00%
11.3.5 Obtaining a Bean by type77707100,00%
11.3.6 Obtaining a Bean by name22202100,00%
11.3.7 Obtaining a passivation capable bean by identifier11101100,00%
11.3.8 Resolving an ambiguous dependency5540480,00%
11.3.9 Validating an injection point22202100,00%
11.3.10 Firing an event66606100,00%
11.3.11 Observer method resolution55505100,00%
11.3.12 Decorator resolution55505100,00%
11.3.13 Interceptor resolution44404100,00%
11.3.14 Determining if an annotation is a qualifier type, scope type, stereotype or interceptor binding type77707100,00%
11.3.15 Determining the hash code and equivalence of qualifiers and interceptor bindings44404100,00%
11.3.16 Obtaining the active Context for a scope11101100,00%
11.3.17 Obtaining the ELResolver11101100,00%
11.3.18 Wrapping a Unified EL ExpressionFactory22202100,00%
11.3.19 Obtaining an AnnotatedType for a class33303100,00%
11.3.20 Obtaining an InjectionTarget for a class22202100,00%
11.3.21 Obtaining a Producer for a field or method44404100,00%
11.3.22 Obtaining an InjectionPoint33303100,00%
11.3.23 Obtaining a BeanAttributes33303100,00%
11.3.24 Obtaining a Bean22202100,00%
11.3.25 Obtaining the instance of an Extension22202100,00%
11.4 Alternative metadata sources45433003069,77%
11.5 Container lifecycle events86606100,00%
11.5.1 BeforeBeanDiscovery event8870787,50%
11.5.2 AfterBeanDiscovery event111010010100,00%
11.5.3 AfterDeploymentValidation event4430375,00%
11.5.4 BeforeShutdown event21101100,00%
11.5.5 ProcessModule event161616016100,00%
11.5.6 ProcessAnnotatedType event32322702784,38%
11.5.7 ProcessInjectionPoint event66606100,00%
11.5.8 ProcessInjectionTarget event36362702775,00%
11.5.9 ProcessProducer event14141201285,71%
11.5.10 ProcessBeanAttributes event141414014100,00%
11.5.11 ProcessBean event323131031100,00%
11.5.12 ProcessObserverMethod event55505100,00%
12 Packaging and Deployment00000
12.1 Bean deployment archives261212012100,00%
12.2 Application initialization lifecycle111010010100,00%
12.3 Application shutdown lifecycle33303100,00%
12.4 Bean discovery352929029100,00%
12.5 Integration with Unified EL33303100,00%

Coverage Detail

Colour Key
Assertion is covered
Assertion is not covered
Assertion test is unimplemented
Assertion is untestable

Section 2 - Concepts

a)

A bean comprises of a (nonempty) set of bean types.

Coverage

org.jboss.cdi.tck.tests.definition.bean
BeanDefinitionTest.testBeanTypesNonEmpty()github
b)

A bean comprises of a (nonempty) set of qualifiers.

Coverage

org.jboss.cdi.tck.tests.definition.bean
BeanDefinitionTest.testQualifiersNonEmpty()github
c)

A bean comprises of a scope.

Coverage

org.jboss.cdi.tck.tests.definition.bean
BeanDefinitionTest.testHasScopeType()github
e)

A bean comprises of an optional bean EL name.

Coverage

org.jboss.cdi.tck.tests.definition.name
NameDefinitionTest.testNonDefaultNamed()github
NameDefinitionTest.testNamedNotDeclaredByBean()github
f)This may only be tested indirectly

A bean comprises of a set of interceptor bindings.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.member
InterceptorBindingTypeWithMemberTest.testInterceptorBindingTypeWithMember()github
org.jboss.cdi.tck.tests.interceptors.definition.multipleBindings
MultipleInterceptorBindingsTest.testInterceptorAppliedToBeanWithAllBindings()github
g)

A bean comprises of a bean implementation.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.lifecycle
SimpleBeanLifecycleTest.testManagedBean()github
h)

A bean may or may not be an alternative.

Section 2.2 - Bean types

a)

A bean may have multiple bean types.

Coverage

org.jboss.cdi.tck.tests.definition.bean
BeanDefinitionTest.testBeanTypes()github
l)

All beans have the bean type java.lang.Object.

Coverage

org.jboss.cdi.tck.tests.definition.bean
BeanDefinitionTest.testBeanTypes()github
org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testApiTypeForClassReturn()github
org.jboss.cdi.tck.tests.implementation.enterprise.definition
EnterpriseBeanDefinitionTest.testObjectIsInAPITypes()github

Section 2.2.1 - Legal bean types

a)

A bean type may be an interface.

Coverage

org.jboss.cdi.tck.tests.definition.bean
BeanDefinitionTest.testBeanTypes()github
b)

A bean type may be a concrete class.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.lifecycle
SimpleBeanLifecycleTest.testManagedBean()github
c)

A bean type may be an abstract class.

Coverage

org.jboss.cdi.tck.tests.definition.bean
BeanDefinitionTest.testAbstractApiType()github
d)

A bean type may be declared final.

Coverage

org.jboss.cdi.tck.tests.definition.bean
BeanDefinitionTest.testFinalApiType()github
BeanDefinitionTest.testBeanTypes()github
e)

A bean type may have final methods.

Coverage

org.jboss.cdi.tck.tests.definition.bean
BeanDefinitionTest.testBeanTypes()github
f)

A bean type may be a parameterized type with actual type parameters.

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution.parameterized
AssignabilityOfRawAndParameterizedTypesTest.testAssignabilityToRawType()github
g)

A bean type may be a parameterized type with type variables.

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution.parameterized
AssignabilityOfRawAndParameterizedTypesTest.testAssignabilityToRawType()github
i)

A bean type may be an array type. Two array types are considered identical only if the element type is identical.

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution
ResolutionByTypeTest.testResolveByTypeWithArray()github
org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testApiTypeForArrayTypeReturn()github
org.jboss.cdi.tck.tests.implementation.producer.field.definition
ProducerFieldDefinitionTest.testApiTypeForArrayTypeReturn()github
j)

A bean type may be a primitive type. Primitive types are considered to be identical to their corresponding wrapper types in java.lang.

Coverage

org.jboss.cdi.tck.tests.definition.bean
BeanDefinitionTest.testIsNullable()github
k)

A bean type may be a raw type.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.lifecycle
SimpleBeanLifecycleTest.testManagedBean()github
la)

A type variable is not a legal bean type.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.broken.typeVariableReturnType
TypeVariableReturnTypeTest.testTypeVariableNotAllowed()github
lb)

A parameterized type that contains a wildcard type parameter is not a legal bean type.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.broken.parameterizedTypeWithWildcard
ParameterizedTypeWithWildcardTest.testParameterizedReturnTypeWithWildcard()github

Section 2.2.2 - Restricting the bean types of a bean

The bean types of a bean may be restricted by annotating the bean class or producer method or field with the annotation @javax.enterprise.inject.Typed. When a @Typed annotation is explicitly specified, only the types whose classes are explicitly listed using the value member, together with java.lang.Object are bean types of the bean.

a)

Check managed bean

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution
ResolutionByTypeTest.testBeanTypesOnManagedBean()github
b)

Check session bean

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution
EnterpriseResolutionByTypeTest.testBeanTypesOnSessionBean()github
c)

Check producer method

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution
ResolutionByTypeTest.testBeanTypesOnProducerMethod()github
d)

Check producer field

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution
ResolutionByTypeTest.testBeanTypesOnProducerField()github
e)

Check generic managed bean

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution
ResolutionByTypeTest.testGenericBeanTypesOnManagedBean()github
g)

Check generic producer method

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution
ResolutionByTypeTest.testGenericBeanTypesOnProducerMethod()github
h)

Check generic producer field

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution
ResolutionByTypeTest.testGenericBeanTypesOnProducerField()github

If a bean class or producer method or field specifies a @Typed annotation, and the value member specifies a class which does not correspond to a type in the unrestricted set of bean types of a bean, the container automatically detects the problem and treats it as a definition error.

j)

Check managed bean

Coverage

org.jboss.cdi.tck.tests.definition.bean.broken.restricted
RestrictedManagedBeanTest.testInvalidTypedValueOnManagedBean()github
k)

Check session bean

Coverage

org.jboss.cdi.tck.tests.definition.bean.broken.restricted
RestrictedSessionBeanTest.testInvalidTypedValueOnSessionBean()github
l)

Check producer method

Coverage

org.jboss.cdi.tck.tests.definition.bean.broken.restricted
RestrictedProducerFieldTest.testInvalidTypedValueOnProducerField()github
m)

Check producer field

Coverage

org.jboss.cdi.tck.tests.definition.bean.broken.restricted
RestrictedProducerMethodTest.testInvalidTypedValueOnProducerField()github

Section 2.2.3 - Typecasting between bean types

a)

A client of a bean may typecast its contextual reference to a bean to any bean type of the bean which is a Java interface. However, the client may not in general typecast its contextual reference to an arbitrary concrete bean type of the bean.

Coverage

org.jboss.cdi.tck.tests.definition.bean
BeanDefinitionTest.testBeanClientCanCastBeanInstanceToAnyBeanType()github

Section 2.3.1 - Built-in qualifier types

a0)@New qualified beans cannot be checked since @New beans aren't required to be available via programmatic lookup

Every bean has the built-in qualifier @Any, even if it does not explicitly declare this qualifier, except for the special @New qualified beans defined in Section 3.14, "@New qualified beans".

Coverage

org.jboss.cdi.tck.tests.lookup.injection.any
AnyInjectionTest.testAnyInjectionIfExactlyOneBeanForType()github
org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testDefaultBindingType()github
org.jboss.cdi.tck.tests.definition.qualifier
QualifierDefinitionTest.testDefaultQualifierDeclaredInJava()github
aa)

If a bean does not explicitly declare a qualifier other than @Named, the bean has exactly one additional qualifier, of type @Default. This is called the default qualifier.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testDefaultBindingType()github
org.jboss.cdi.tck.tests.definition.qualifier
QualifierDefinitionTest.testDefaultQualifierDeclaredInJava()github
org.jboss.cdi.tck.tests.implementation.producer.field.definition
ProducerFieldDefinitionTest.testDefaultBindingType()github
b)

The default qualifier is also assumed for any injection point that does not explicitly declare a qualifier.

Coverage

org.jboss.cdi.tck.tests.definition.qualifier
QualifierDefinitionTest.testDefaultQualifierForInjectionPoint()github

Section 2.3.2 - Defining new qualifier types

aa)

A qualifier type is a Java annotation defined as @Target({METHOD, FIELD, PARAMETER, TYPE}) and @Retention(RUNTIME).

ab)Non-runtime retention annotations are discarded by the compiler

A qualifier type is a Java annotation defined as @Target({METHOD, FIELD, PARAMETER, TYPE}) and @Retention(RUNTIME).

ba)

A qualifier type may be declared by specifying the @javax.inject.Qualifier meta-annotation.

Coverage

org.jboss.cdi.tck.tests.definition.qualifier
QualifierDefinitionTest.testQualifierDeclaresBindingAnnotation()github
d)This is true by default in the JLS

A qualifier type may define annotation members.

Section 2.3.3 - Declaring the qualifiers of a bean

The qualifiers of a bean are declared by annotating the bean class or producer method or field with the qualifier types.

a)

Test by annotating a bean class.

Coverage

org.jboss.cdi.tck.tests.definition.qualifier
QualifierDefinitionTest.testQualifiersDeclaredInJava()github
b)

Test by annotating a producer method.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testBindingType()github
c)

Test by annotating a producer field.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition
ProducerFieldDefinitionTest.testBindingType()github
d)

Any bean may declare multiple qualifier types.

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution
ResolutionByTypeTest.testAllQualifiersSpecifiedForResolutionMustAppearOnBean()github
org.jboss.cdi.tck.tests.definition.qualifier
QualifierDefinitionTest.testMultipleQualifiers()github

Section 2.3.4 - Specifying qualifiers of an injected field

a)

Qualifier types may be applied to injected fields (see Section 3.8, "Injected fields") to determine the bean that is injected, according to the rules of typesafe resolution defined in Section 5.3, "Typesafe resolution".

Coverage

org.jboss.cdi.tck.tests.implementation.simple.lifecycle
SimpleBeanLifecycleTest.testCreateInjectsFieldsDeclaredInJava()github
b)

A bean may only be injected to an injection point if it has all the qualifiers of the injection point.

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution
ResolutionByTypeTest.testAllQualifiersSpecifiedForResolutionMustAppearOnBean()github

Section 2.3.5 - Specifying qualifiers of a method or constructor parameter

Qualifier types may be applied to parameters of producer methods, initializer methods, disposer methods, observer methods or bean constructors (see Chapter 3, Bean implementation) to determine the bean instance that is passed when the method is called by the container.

a)

Test producer method.

Coverage

org.jboss.cdi.tck.tests.definition.qualifier
QualifierDefinitionTest.testFieldInjectedFromProducerMethod()github
org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testBindingTypesAppliedToProducerMethodParameters()github
b)

Test initializer method.

Coverage

org.jboss.cdi.tck.tests.implementation.initializer
InitializerMethodTest.testBindingTypeOnInitializerParameter()github
c)

Test disposer method.

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition
DisposalMethodDefinitionTest.testBindingTypesAppliedToDisposalMethodParameters()github
ca)

Test observer method.

Coverage

org.jboss.cdi.tck.tests.event
EventTest.testObserverMethodParameterInjectionPoints()github
d)

Test bean constructor.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.lifecycle
SimpleBeanLifecycleTest.testInjectionOfParametersIntoBeanConstructor()github

Section 2.4 - Scopes

a)

All beans have a scope.

Coverage

org.jboss.cdi.tck.tests.definition.bean
BeanDefinitionTest.testHasScopeType()github
b)This is a statement of intent

A scope type is represented by an annotation type.

c)

The set of scope types is extensible.

Coverage

org.jboss.cdi.tck.tests.definition.scope
ScopeDefinitionTest.testScopeTypesAreExtensible()github

Section 2.4.1 - Built-in scope types

There are five standard scope types defined by this specification, all defined in the package javax.enterprise.context.

aa)

The @RequestScoped, @ApplicationScoped and @SessionScoped annotations defined in Section 6.7, "Context management for built-in scopes" represent the standard scopes defined by the Java Servlets specification.

Coverage

org.jboss.cdi.tck.tests.context
ContextTest.testBuiltInContexts()github
ab)

The @RequestScoped, @ApplicationScoped and @SessionScoped annotations defined in Section 6.7, "Context management for built-in scopes" represent the standard scopes defined by the Java Servlets specification.

Coverage

org.jboss.cdi.tck.tests.context
ContextTest.testBuiltInContexts()github
ac)

The @RequestScoped, @ApplicationScoped and @SessionScoped annotations defined in Section 6.7, "Context management for built-in scopes" represent the standard scopes defined by the Java Servlets specification.

Coverage

org.jboss.cdi.tck.tests.context
ContextTest.testBuiltInContexts()github
ba)

The @ConversationScoped annotation represents the conversation scope defined in Section 6.7.4, "Conversation context lifecycle".

Coverage

org.jboss.cdi.tck.tests.context.conversation
LongRunningConversationPropagatedByFacesContextTest.testConversationPropagated()github
ca)

The @Dependent pseudo-scope is for dependent objects, as defined in Section 6.4, "Dependent pseudo-scope"

Coverage

org.jboss.cdi.tck.tests.context
ContextTest.testBuiltInContexts()github
e)

If an interceptor or decorator has any scope other than @Dependent, non-portable behavior results.

Section 2.4.2 - Defining new scope types

aa)

A scope type is a Java annotation defined as @Target({TYPE, METHOD, FIELD}) and @Retention(RUNTIME).

Coverage

org.jboss.cdi.tck.tests.definition.scope
ScopeDefinitionTest.testScopeTypeHasCorrectTarget()github
ab)Non-runtime retention annotations are discarded by the compiler

A scope type is a Java annotation defined as @Target({TYPE, METHOD, FIELD}) and @Retention(RUNTIME).

ac)

A scope type must not have any attributes. If a scope type has attributes non-portable behavior results.

ba)

All scope types must specify the @javax.inject.Scope or @javax.enterprise.context.NormalScope meta-annotation.

Coverage

org.jboss.cdi.tck.tests.definition.scope
ScopeDefinitionTest.testScopeTypeDeclaresScopeTypeAnnotation()github

Section 2.4.3 - Declaring the bean scope

a)

The scope of a bean is defined by annotating the bean class or producer method or field with a scope type.

Coverage

org.jboss.cdi.tck.tests.definition.scope
ScopeDefinitionTest.testScopeDeclaredInJava()github
ba)

A bean class or producer method or field may specify at most one scope type annotation. If a bean class or producer method or field specifies multiple scope type annotations, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.definition.scope.broken.tooManyScopes
TooManyScopesTest.testTooManyScopesSpecifiedInJava()github
c)

A scope type may be specified using a stereotype annotation, as defined in Section 2.7.2, "Declaring the stereotypes for a bean"

Coverage

org.jboss.cdi.tck.tests.definition.stereotype
StereotypeDefinitionTest.testStereotypeWithScopeType()github

Section 2.4.4 - Default scope

aa)

When no scope is explicitly declared by annotating the bean class or producer method or field the scope of a bean is defaulted.

Coverage

org.jboss.cdi.tck.tests.definition.scope
ScopeDefinitionTest.testDefaultScope()github
b)

If the bean does not declare any stereotype with a declared default scope, the default scope for the bean is @Dependent.

Coverage

org.jboss.cdi.tck.tests.definition.stereotype
StereotypeDefinitionTest.testStereotypeWithoutScopeType()github
c)

If all stereotypes declared by the bean that have some declared default scope have the same default scope, then that scope is the default scope for the bean.

Coverage

org.jboss.cdi.tck.tests.definition.scope
ScopeDefinitionTest.testMultipleCompatibleScopeStereotypes()github
org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testStereotypeSpecifiesScope()github
da)

If there are two different stereotypes declared by the bean that declare different default scopes, then there is no default scope and the bean must explicitly declare a scope. If it does not explicitly declare a scope, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.definition.scope
ScopeDefinitionTest.testMultipleIncompatibleScopeStereotypesWithScopeSpecified()github
org.jboss.cdi.tck.tests.definition.stereotype.broken.scopeConflict
IncompatibleStereotypesTest.testMultipleIncompatibleScopeStereotypes()github
e)

If a bean explicitly declares a scope, any default scopes declared by stereotypes are ignored.

Coverage

org.jboss.cdi.tck.tests.definition.stereotype
StereotypeDefinitionTest.testExplicitScopeOverridesMergedScopesFromMultipleStereotype()github
org.jboss.cdi.tck.tests.definition.scope
ScopeDefinitionTest.testScopeSpecifiedAndStereotyped()github

Section 2.5 - Bean EL names

a)

A valid bean EL name is a period-separated list of valid EL identifiers

Coverage

org.jboss.cdi.tck.tests.lookup.el
ResolutionByNameTest.testELResolverReturnsContextualInstance()github

Section 2.5.1 - Declaring the bean EL name

To specify the EL name of a bean, the qualifier @javax.inject.Named is applied to the bean class or producer method or field.

a)

Test with a bean class.

Coverage

org.jboss.cdi.tck.tests.definition.name
NameDefinitionTest.testNonDefaultNamed()github
b)

Test with a producer method.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testNamedMethod()github
c)

Test with a producer field.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition
ProducerFieldDefinitionTest.testNamedField()github
d)

If the @Named annotation does not specify the value member, the EL name is defaulted.

Coverage

org.jboss.cdi.tck.tests.definition.name
NameDefinitionTest.testDefaultNamed()github
org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testDefaultNamedMethod()github
org.jboss.cdi.tck.tests.implementation.producer.field.definition
ProducerFieldDefinitionTest.testDefaultNamedByStereotype()github

Section 2.5.2 - Default bean names

A default name must be assigned by the container when a bean class or producer method or field of a bean declares a @Named annotation and no bean name is explicitly specified by the value member.

a)

Test with a bean class.

Coverage

org.jboss.cdi.tck.tests.definition.name
NameDefinitionTest.testDefaultNamed()github
b)

Test with a producer method.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testDefaultNamedMethod()github
c)

Test with a producer field.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition
ProducerFieldDefinitionTest.testDefaultNamedByStereotype()github
e)

A default name must be assigned by the container when a bean declares a stereotype that declares an empty @Named annotation, and the bean does not explicitly specify an bean name.

Coverage

org.jboss.cdi.tck.tests.definition.stereotype.named
DefaultNamedTest.testStereotypeDeclaringNamed()github

If a bean class or producer method or field of a bean declares a @Named annotation and no bean name is explicitly specified the value of the value member is defaulted.

fa)

Test with a bean class.

Coverage

org.jboss.cdi.tck.tests.definition.name
NameDefinitionTest.testDefaultNamed()github
org.jboss.cdi.tck.tests.lookup.injectionpoint.named
NamedAtInjectionPointTest.testFieldNameUsedAsBeanName()github
fb)

Test with a producer method.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testDefaultNamedMethod()github
fc)

Test with a producer field.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition
ProducerFieldDefinitionTest.testDefaultNamed()github

Section 2.5.3 - Beans with no name

a)

If @Named is not declared by the bean, nor by its stereotypes, a bean has no name.

Coverage

org.jboss.cdi.tck.tests.definition.name
NameDefinitionTest.testNamedNotDeclaredByStereotype()github
NameDefinitionTest.testNamedNotDeclaredByBean()github
org.jboss.cdi.tck.tests.implementation.producer.field.definition
ProducerFieldDefinitionTest.testDefaultNamedByStereotype()github
b)

If an interceptor or decorator has a name, non-portable behavior results.

Section 2.6 - Alternatives

a)

An alternative is a bean that must be explicitly declared in the beans.xml file if it should be available for lookup, injection or EL resolution.

Coverage

org.jboss.cdi.tck.tests.alternative
AlternativeAvailabilityTest.testAlternativeAvailability()github
org.jboss.cdi.tck.tests.extensions.alternative.deployment
AlternativeInLibraryWithExtensionTest.testAlternative()github

Section 2.6.1 - Declaring an alternative

An alternative may be declared by annotating the bean class or producer method or field with the @Alternative annotation.

a)

Test with a bean class.

Coverage

org.jboss.cdi.tck.tests.alternative
AlternativeAvailabilityTest.testAlternativeAvailability()github
org.jboss.cdi.tck.tests.extensions.alternative.deployment
AlternativeInLibraryWithExtensionTest.testAlternative()github
ab)

Test with a producer method.

Coverage

org.jboss.cdi.tck.tests.alternative
AlternativeAvailabilityTest.testProducerAlternativesOnMethodAndField()github
ac)

Test with a producer field.

Coverage

org.jboss.cdi.tck.tests.alternative
AlternativeAvailabilityTest.testProducerAlternativesOnMethodAndField()github

An alternative may be declared by annotating a bean, producer method or producer field with a stereotype that declares an @Alternative annotation.

b)

Test with a bean.

Coverage

org.jboss.cdi.tck.tests.alternative
AlternativeAvailabilityTest.testAnyEnabledAlternativeStereotypeMakesAlternativeEnabled()github
c)

Test with a producer method.

Coverage

org.jboss.cdi.tck.tests.alternative
AlternativeAvailabilityTest.testStereotypeAlternativeOnProducerMethodAndField()github
d)

Test with a producer field.

Coverage

org.jboss.cdi.tck.tests.alternative
AlternativeAvailabilityTest.testStereotypeAlternativeOnProducerMethodAndField()github
e)

If an interceptor or decorator is an alternative, non-portable behavior results.

Section 2.7 - Stereotypes

a)

A stereotype may specify that all beans with the stereotype have defaulted bean EL names.

Coverage

org.jboss.cdi.tck.tests.definition.name
NameDefinitionTest.testStereotypeDefaultsName()github
org.jboss.cdi.tck.tests.definition.stereotype.named
DefaultNamedTest.testStereotypeDeclaringNamed()github
aa)

A stereotype may specify that all beans with the stereotype are alternatives.

Coverage

org.jboss.cdi.tck.tests.alternative
AlternativeAvailabilityTest.testAnyEnabledAlternativeStereotypeMakesAlternativeEnabled()github

A bean may declare zero, one or multiple stereotypes.

b)Not testable through API

A bean may declare zero stereotypes.

c)

Test with one stereotype.

Coverage

org.jboss.cdi.tck.tests.definition.stereotype
StereotypeDefinitionTest.testOneStereotypeAllowed()github
d)

Test with multiple stereotypes.

Coverage

org.jboss.cdi.tck.tests.definition.stereotype
StereotypeDefinitionTest.testMultipleStereotypesAllowed()github

Section 2.7.1 - Defining new stereotypes

A beans stereotype is a Java annotation defined as @Target({TYPE, METHOD, FIELD}), @Target(TYPE), @Target(METHOD), @Target(FIELD) or @Target({METHOD, FIELD}) and @Retention(RUNTIME).

aa)

Test @Target({TYPE, METHOD, FIELD}).

ab)

Test @Target(TYPE).

ac)

Test @Target(FIELD).

ad)

Test @Target({METHOD, FIELD}).

ae)Non-runtime retention annotations are discarded by the compiler

@Retention(RUNTIME) - untestable.

b)

A stereotype may be declared by specifying the @javax.enterprise.inject.Stereotype meta-annotation.

Coverage

org.jboss.cdi.tck.tests.definition.stereotype
StereotypeDefinitionTest.testOneStereotypeAllowed()github

Section 2.7.1.1 - Declaring the default scope for a stereotype

The default scope of a stereotype is defined by annotating the stereotype with a scope type. A stereotype may declare at most one scope. If a stereotype declares more than one scope, the container automatically detects the problem and treats it as a definition error.

aa)

Test with one scope.

Coverage

org.jboss.cdi.tck.tests.definition.stereotype
StereotypeDefinitionTest.testStereotypeWithScopeType()github
StereotypeDefinitionTest.testStereotypeWithoutScopeType()github
ab)

Test that a stereotype with multiple scopes throws an exception.

Coverage

org.jboss.cdi.tck.tests.definition.stereotype.broken.tooManyScopes
TooManyScopeTypesTest.testStereotypeWithTooManyScopeTypes()github

Section 2.7.1.2 - Specifying interceptor bindings for a stereotype

a0)

The interceptor bindings of a stereotype are defined by annotating the stereotype with the interceptor binding types.

Coverage

org.jboss.cdi.tck.tests.definition.stereotype.interceptor
StereotypeWithMultipleInterceptorBindingsTest.testMultipleInterceptorBindings()github
a)

A stereotype may declare zero interceptor bindings.

Coverage

org.jboss.cdi.tck.tests.definition.stereotype
StereotypeDefinitionTest.testOneStereotypeAllowed()github
b)

A stereotype may declare one interceptor bindings.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition
InterceptorDefinitionTest.testStereotypeInterceptorBindings()github
org.jboss.cdi.tck.tests.definition.stereotype.interceptor.enterprise
EnterpriseStereotypeInterceptorBindingTest.testStereotypeInterceptorBindings()github
c)

A stereotype may declare multiple interceptor bindings.

Coverage

org.jboss.cdi.tck.tests.definition.stereotype.interceptor
StereotypeWithMultipleInterceptorBindingsTest.testMultipleInterceptorBindings()github

Section 2.7.1.3 - Declaring a @Named stereotype

aa)

A stereotype may declare an empty @Named annotation, which specifies that every bean with the stereotype has a defaulted name when a name is not explicitly specified by the bean.

Coverage

org.jboss.cdi.tck.tests.definition.name
NameDefinitionTest.testStereotypeDefaultsName()github
org.jboss.cdi.tck.tests.definition.stereotype.named
DefaultNamedTest.testStereotypeDeclaringNamed()github
DefaultNamedTest.testStereotypeNamedOverridenByBean()github
org.jboss.cdi.tck.tests.implementation.producer.method.definition.name
ProducerMethodWithDefaultNameTest.testProducerMethodQualifiers()github
org.jboss.cdi.tck.tests.implementation.producer.field.definition
ProducerFieldDefinitionTest.testDefaultNamedByStereotype()github
ab)

A @Named qualifier declared by a stereotype is not added to the qualifiers of a bean with the stereotype.

Coverage

org.jboss.cdi.tck.tests.definition.stereotype.named
DefaultNamedTest.testStereotypeDeclaringNamed()github
org.jboss.cdi.tck.tests.implementation.producer.method.definition.name
ProducerMethodWithDefaultNameTest.testProducerMethodQualifiers()github
org.jboss.cdi.tck.tests.implementation.producer.field.definition
ProducerFieldDefinitionTest.testDefaultNamedByStereotype()github
ac)

If a stereotype declares a non-empty @Named annotation, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.definition.stereotype.broken.nonEmptyNamed
NonEmptyNamedTest.testStereotypeWithNonEmptyNamed()github
b)The behavior here is undefined.

A stereotype should not declare any qualifier annotation other than @Named. If a stereotype declares any other qualifier annotation, non-portable behavior results.

c)

A stereotype should not be annotated @Typed. If a stereotype is annotated @Typed, non-portable behavior results.

Section 2.7.1.4 - Declaring an @Alternative stereotype

a)

A stereotype may declare an @Alternative annotation, which specifies that every bean with the stereotype is an alternative.

Coverage

org.jboss.cdi.tck.tests.alternative
AlternativeAvailabilityTest.testAnyEnabledAlternativeStereotypeMakesAlternativeEnabled()github
org.jboss.cdi.tck.tests.definition.stereotype.alternative.enterprise
EnterpriseStereotypeAlternativeSpecializeTest.testStereotypeAlternative()github
EnterpriseStereotypeAlternativeTest.testStereotypeAlternative()github

Section 2.7.1.5 - Stereotypes with additional stereotypes

a)

A stereotype may declare other stereotypes.

Coverage

org.jboss.cdi.tck.tests.definition.stereotype.inheritance
StereotypeInheritenceTest.testInheritence()github
b)

Stereotype declarations are transitive - a stereotype declared by a second stereotype is inherited by all beans and other stereotypes that declare the second stereotype.

Coverage

org.jboss.cdi.tck.tests.definition.stereotype.inheritance
StereotypeInheritenceTest.testInheritence()github
c)No definition of what happens if you do this

Stereotypes declared @Target(TYPE) may not be applied to stereotypes declared @Target({TYPE, METHOD, FIELD}), @Target(METHOD), @Target(FIELD), @Target({METHOD, FIELD}).

Section 2.7.2 - Declaring the stereotypes for a bean

Stereotype annotations may be applied to a bean class or producer method or field.

a)

Test with a bean class.

Coverage

org.jboss.cdi.tck.tests.definition.scope
ScopeDefinitionTest.testScopeSpecifiedAndStereotyped()github
b)

Test with a producer method.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testStereotypeSpecifiesScope()github
c)

Test with a producer field.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition
ProducerFieldDefinitionTest.testStereotype()github
db)

The default scope declared by the stereotype may be overridden by the bean.

Coverage

org.jboss.cdi.tck.tests.definition.scope
ScopeDefinitionTest.testWebBeanScopeTypeOverridesStereotype()github
e)

Multiple stereotypes may be applied to the same bean.

Coverage

org.jboss.cdi.tck.tests.definition.stereotype
StereotypeDefinitionTest.testMultipleStereotypesAllowed()github
StereotypeDefinitionTest.testExplicitScopeOverridesMergedScopesFromMultipleStereotype()github

Section 2.7.3 - Built-in stereotypes

aa)Tested by API signature test

The built-in stereotype @javax.enterprise.inject.Model is intended for use with beans that define the model layer of an MVC web application architecture such as JSF.

Section 2.8 - Problems detected automatically by the container

a)Generalization

When the application violates a rule defined by this specification, the container automatically detects the problem. There are three kinds of problem - definition errors occur when a single bean definition violates the rules of this specification, deployment problems occur when there are problems resolving dependencies, or inconsistent specialization, in a particular deployment, and exceptions occur at runtime.

b)

Definition errors are developer errors. They may be detected by tooling at development time, and are also detected by the container at initialization time. If a definition error exists in a deployment, initialization will be aborted by the container.

Coverage

org.jboss.cdi.tck.tests.lookup.clientProxy.unproxyable.array
ArrayTest.testInjectionPointWithArrayType()github
org.jboss.cdi.tck.tests.definition.stereotype.broken.tooManyScopes
TooManyScopeTypesTest.testStereotypeWithTooManyScopeTypes()github
ba)

If a definition error exists, the container must throw a subclass of javax.enterprise.inject.spi.DefinitionException.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.definition.dependentWithPublicField
DependentWithPublicFieldTest.testNonDependentScopedBeanCanNotHavePublicField()github
org.jboss.cdi.tck.tests.definition.bean.broken.restricted
RestrictedManagedBeanTest.testInvalidTypedValueOnManagedBean()github
org.jboss.cdi.tck.tests.definition.scope.broken.tooManyScopes
TooManyScopesTest.testTooManyScopesSpecifiedInJava()github
c)

Deployment problems are detected by the container at initialization time. If a deployment problem exists in a deployment, initialization will be aborted by the container.

Coverage

org.jboss.cdi.tck.tests.lookup.dependency.resolution.broken.ambiguous
AmbiguousDependencyTest.testAmbiguousDependency()github
org.jboss.cdi.tck.tests.alternative.broken.incorrect.name
NoClassWithSpecifiedNameTest.test()github
ca)

If a deployment problem occurs, the container must throw a subclass of javax.enterprise.inject.spi.DeploymentException.

Coverage

org.jboss.cdi.tck.tests.lookup.dependency.resolution.broken.ambiguous
AmbiguousDependencyTest.testAmbiguousDependency()github
org.jboss.cdi.tck.tests.alternative.broken.incorrect.name
NoClassWithSpecifiedNameTest.test()github
d)

The container is permitted to define a non-portable mode, for use at development time, in which some definition errors and deployment problems do not cause application initialization to abort.

e)

Exceptions represent problems that may not be detected until they actually occur at runtime. All exceptions defined by this specification are unchecked exceptions. All exceptions defined by this specification may be safely caught and handled by the application.

Section 3.1 - Managed beans

a)

If the bean class of a managed bean is annotated with both the @Interceptor and @Decorator stereotypes, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.broken.interceptorCanNotBeDecorator
InterceptorCanNotBeDecoratorTest.testInterceptorCanNotAlsoBeDecorator()github

If a managed bean has a non-static public field, it must have scope @Dependent. If a managed bean with a non-static public field declares any scope other than @Dependent, the container automatically detects the problem and treats it as a definition error.

fa)

Check a dependent scoped bean with a public field.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.definition
SimpleBeanDefinitionTest.testDependentScopedBeanCanHaveNonStaticPublicField()github
fb)

Check a managed bean with a static public field which declares any scope other than @Dependent.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.definition.nonDependentWithPublicStaticField
NonDependentWithPublicStaticFieldTest.testNonDependentScopedBeanCanHavePublicStaticField()github
fc)

If a managed bean with a non-static public field declares any scope other than @Dependent, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.definition.dependentWithPublicField
DependentWithPublicFieldTest.testNonDependentScopedBeanCanNotHavePublicField()github
g)

If the managed bean class is a generic type, it must have scope @Dependent. If a managed bean with a parameterized bean class declares any scope other than @Dependent, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.definition.bean.genericbroken
GenericManagedBeanTest.testNonDependentGenericManagedBeanNotOk()github

Section 3.1.1 - Which Java classes are managed beans?

b)

A top-level Java class is not a managed bean if it is a non-static inner class.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.definition
SimpleBeanDefinitionTest.testNonStaticInnerClassDeclaredInJavaNotDiscovered()github
ba)Implied as the inverse of assertion 3.1.1.b

A top-level Java class that is a static inner class can be a managed bean.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.definition
SimpleBeanDefinitionTest.testStaticInnerClassDeclaredInJavaAllowed()github
ca)

A top-level Java class is not a managed bean if it is an abstract class, unless it is annotated @Decorator.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.definition
SimpleBeanDefinitionTest.testAbstractClassDeclaredInJavaNotDiscovered()github
cb)

A top-level Java class is not a managed bean if it is an interface, unless it is annotated @Decorator.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.definition
SimpleBeanDefinitionTest.testInterfaceNotDiscoveredAsSimpleBean()github
f)

A top-level Java class is not a managed bean if it is annotated with any of the EJB component-defining annotations

Coverage

org.jboss.cdi.tck.tests.implementation.simple.definition
EnterpriseBeanNotDiscoveredAsManagedBeanTest.testClassesImplementingEnterpriseBeanInterfaceNotDiscoveredAsSimpleBean()github
g)

A top-level Java class is not a managed bean if it implements javax.enterprise.inject.spi.Extension.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.definition
SimpleBeanDefinitionTest.testExtensionNotDiscoveredAsSimpleBean()github
h)

A top-level Java class is not a managed bean if it is annotated @Vetoed.

Coverage

org.jboss.cdi.tck.tests.vetoed.enterprise
EnterpriseVetoedTest.testClassLevelVeto()github
org.jboss.cdi.tck.tests.vetoed
VetoedTest.testClassLevelVeto()github
VetoedTest.testVetoedAnnotation()github
VetoedTest.testVetoedEnum()github
VetoedTest.testPackageLevelVeto()github
n)

A top-level Java class is not a managed bean if it is declared as an EJB bean class in ejb-jar.xml

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.definition
EnterpriseBeanViaXmlTest.testEjbDeclaredInXmlNotSimpleBean()github
p)

A top-level Java class is only a managed bean if it has an appropriate constructor - a constructor with no parameters.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.definition
SimpleBeanDefinitionTest.testSimpleBeanOnlyIfConstructorParameterless()github
q)

A top-level Java class is only a managed bean if it has an appropriate constructor - a constructor annotated @Inject.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.definition
SimpleBeanDefinitionTest.testSimpleBeanOnlyIfConstructorIsInitializer()github

Section 3.1.2 - Bean types of a managed bean

a)

The unrestricted set of bean types for a managed bean contains the bean class, every superclass and all interfaces it implements directly or indirectly.

Coverage

org.jboss.cdi.tck.tests.definition.bean
BeanDefinitionTest.testBeanTypes()github
org.jboss.cdi.tck.tests.definition.bean.types
ManagedBeanTypesTest.testGenericHierarchyBeanTypes()github

Section 3.1.3 - Declaring a managed bean

a)

A managed bean with a constructor that takes no parameters does not require any special annotations

Coverage

org.jboss.cdi.tck.tests.implementation.simple.definition
SimpleBeanDefinitionTest.testEmptyConstructorUsed()github
ab)

If the managed bean does not have a constructor that takes no parameters, it must have a constructor annotated @Inject. No additional special annotations are required.

A bean class may also specify a scope, name, stereotypes and/or qualifiers.

ba)

Test a bean with a scope.

Coverage

org.jboss.cdi.tck.tests.definition.bean
BeanDefinitionTest.testHasScopeType()github
bb)

Test a bean with a name.

Coverage

org.jboss.cdi.tck.tests.definition.name
NameDefinitionTest.testNonDefaultNamed()github
bd)

Test a bean with a stereotype.

Coverage

org.jboss.cdi.tck.tests.definition.bean
BeanDefinitionTest.testMultipleStereotypes()github
be)

Test a bean with a qualifier.

Coverage

org.jboss.cdi.tck.tests.definition.qualifier
QualifierDefinitionTest.testQualifiersDeclaredInJava()github
c)

A managed bean may extend another managed bean.

Coverage

org.jboss.cdi.tck.tests.definition.bean
BeanDefinitionTest.testBeanExtendsAnotherBean()github

Section 3.1.4 - Specializing a managed bean

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".

aa)

Test that a specializing bean has all its own qualifiers and the qualifiers of the specialized bean.

Coverage

org.jboss.cdi.tck.tests.inheritance.specialization.simple
SimpleBeanSpecializationTest.testSpecializingBeanHasQualifiersOfSpecializedAndSpecializingBean()github
ab)

Test that a specializing bean has the name of the specialized bean.

Coverage

org.jboss.cdi.tck.tests.inheritance.specialization.simple
SimpleBeanSpecializationTest.testSpecializingBeanHasNameOfSpecializedBean()github
ac)

Test a specialized bean extending a managed bean.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.lifecycle
SimpleBeanLifecycleTest.testSpecializedBeanExtendsManagedBean()github

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.

da)

Test a specializing bean extending a non simple bean.

Coverage

org.jboss.cdi.tck.tests.inheritance.specialization.simple.broken.noextend3
SpecializingClassExtendsNonSimpleBeanTest.testSpecializingClassExtendsNonSimpleBean()github
db)

Test a specializing bean extending nothing.

Coverage

org.jboss.cdi.tck.tests.inheritance.specialization.simple.broken.noextend2
SpecializingBeanExtendsNothingTest.testSpecializingClassDirectlyExtendsNothing()github
dc)

Test a specializing bean directly extending an enterprise bean class.

Coverage

org.jboss.cdi.tck.tests.inheritance.specialization.simple.broken.extendejb
SpecializingBeanExtendsEnterpriseBeanTest.testSpecializingClassDirectlyExtendsEnterpriseBean()github
dd)

Test a specializing bean implementing an interface and extending nothing.

Coverage

org.jboss.cdi.tck.tests.inheritance.specialization.simple.broken.noextend1
SpecializingBeanImplementsInterfaceOnly.testSpecializingClassImplementsInterfaceAndExtendsNothing()github

Section 3.1.5 - Default name for a managed bean

a)

The default name for a managed bean is the unqualified class name of the bean class, after converting the first character to lower case

Coverage

org.jboss.cdi.tck.tests.definition.name
NameDefinitionTest.testDefaultNamed()github

Section 3.2 - Session beans

aa)

A session bean is a bean that is implemented by a session bean with an EJB 3.x client view that is not annotated with @Vetoed.

Coverage

No tests exist for this assertion

ab)This is a reference to the EJB specification

The basic lifecycle and semantics of EJB session beans are defined by the EJB specification.

b)

A stateless session bean must belong to the @Dependent pseudo-scope

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.definition
EnterpriseBeanDefinitionTest.testStatelessMustBeDependentScoped()github
c)

A singleton bean must belong to either the @ApplicationScoped scope or to the @Dependent pseudo-scope

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.definition
EnterpriseBeanDefinitionTest.testSingletonWithDependentScopeOK()github
EnterpriseBeanDefinitionTest.testSingletonWithApplicationScopeOK()github
da)

If a session bean specifies an illegal scope, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.broken.singletonWithRequestScope
SingletonWithRequestScopeTest.testSingletonWithRequestScopeFails()github
org.jboss.cdi.tck.tests.implementation.enterprise.broken.statelessWithConversationScope
StatelessWithConversationScopeTest.testStatelessWithConversationScopeFails()github
org.jboss.cdi.tck.tests.implementation.enterprise.broken.singletonWithSessionScope
SingletonWithSessionScopeTest.testSingletonWithSessionScopeFails()github
org.jboss.cdi.tck.tests.implementation.enterprise.broken.statelessWithRequestScope
StatelessWithRequestScopeTest.testStatelessWithRequestScopeFails()github
org.jboss.cdi.tck.tests.implementation.enterprise.broken.statelessWithApplicationScope
StatelessWithApplicationScopeTest.testStatelessWithSessionScopeFails()github
org.jboss.cdi.tck.tests.implementation.enterprise.broken.statelessWithSessionScope
StatelessWithSessionScopeTest.testStatelessWithSessionScopeFails()github
org.jboss.cdi.tck.tests.implementation.enterprise.broken.singletonWithConversationScope
SingletonWithConversationScopeTest.testSingletonWithConversationScopeFails()github
e)No way of testing the real intent of this statement, so we check that a SFSB may be scoped

A stateful session bean may have any scope.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.definition
EnterpriseBeanDefinitionTest.testBeanWithScopeAnnotation()github
f)This is describing non-portable behavior

When a contextual instance of a session bean is obtained via the dependency injection service, the behavior of SessionContext.getInvokedBusinessInterface() is specific to the container implementation. Portable applications should not rely upon the value returned by this method.

g)

If the bean class of a session bean is annotated @Interceptor, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.broken.statelessInterceptor
InterceptorAnnotatedStatelessSessionBeanTest.testStatelessSessionBeanNotAllowedToBeInterceptor()github
h)

If the bean class of a session bean is annotated @Decorator, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.broken.statelessDecorator
DecoratorAnnotatedStatelessSessionBeanTest.testStatelessSessionBeanNotAllowedToBeDecorator()github
i)

If the session bean class is a generic type, it must have scope @Dependent. If a session bean with a parameterized bean class declares any scope other than @Dependent, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.broken.genericStateless
GenericStatelessSessionBeanTest.testRequestScopedGenericStatelessSessionBean()github

Section 3.2.1 - EJB remove methods of session beans

a)

If a session bean is a stateful session bean, and the scope is @Dependent, the application may call any EJB remove method of a contextual instance of the session bean.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.remove
EnterpriseBeanRemoveMethodTest.testApplicationMayCallAnyRemoveMethodOnDependentScopedSessionEnterpriseBeans()github
b)

If a session bean is a stateful session bean, and the scope is not @Dependent, the application may not directly call any EJB remove method of any instance of the session bean. If the application directly calls an EJB remove method of any contextual instance of a session bean that is a stateful session bean and declares any scope other than @Dependent, an UnsupportedOperationException is thrown

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.remove
EnterpriseBeanRemoveMethodTest.testApplicationCannotCallRemoveMethodOnNonDependentScopedSessionEnterpriseBean()github
da)

If the application directly calls an EJB remove method of a contextual instance of a session bean that is a stateful session bean and has scope @Dependent then no parameters are passed to the method by the container.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.remove
EnterpriseBeanRemoveMethodTest.testApplicationMayCallRemoveMethodOnDependentScopedSessionEnterpriseBeansButNoParametersArePassed()github
dba)

If the application directly calls an EJB remove method of a contextual instance of a session bean that is a stateful session bean and has scope @Dependent then the container ignores the instance instead of destroying it when Contextual.destroy() is called, as defined in Section 6.5, "Lifecycle of stateful session beans"

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.lifecycle
EnterpriseBeanLifecycleTest.testRemovedEjbIgnored()github

Section 3.2.2 - Bean types of a session bean

aa)

The unrestricted set of bean types for a session bean contains all local interfaces of the bean and their superinterfaces.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.definition
EnterpriseBeanDefinitionTest.testBeanTypesAreLocalInterfacesWithoutWildcardTypesOrTypeVariablesWithSuperInterfaces()github
org.jboss.cdi.tck.tests.definition.bean.types.enterprise
SessionBeanTypesTest.testGenericHierarchyBeanTypes()github
ba)

If the session bean has a bean class local view, the set of bean types contains the bean class and all superclasses.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.definition
EnterpriseBeanDefinitionTest.testEnterpriseBeanClassLocalView()github
EnterpriseBeanViaXmlTest.testEjbDeclaredInXmlNotSimpleBean()github
org.jboss.cdi.tck.tests.definition.bean.types.enterprise
SessionBeanTypesTest.testGenericHierarchyBeanTypes()github
c)

java.lang.Object is a bean type of every session bean

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.definition
EnterpriseBeanDefinitionTest.testObjectIsInAPITypes()github
org.jboss.cdi.tck.tests.definition.bean.types.enterprise
SessionBeanTypesTest.testGenericHierarchyBeanTypes()github
d)

Remote interfaces are not included in the set of bean types

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.definition
EnterpriseBeanDefinitionTest.testRemoteInterfacesAreNotInAPITypes()github

Section 3.2.3 - Declaring a session bean

aa)

A session bean does not require any special annotations apart from the component-defining annotation (or XML declaration) required by the EJB specification.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.definition
EnterpriseBeanDefinitionTest.testObjectIsInAPITypes()github

A bean class may also specify a scope, name, stereotypes and/or qualifiers.

ba)

Test a bean class with a scope.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.definition
EnterpriseBeanDefinitionTest.testBeanWithScopeAnnotation()github
bb)

Test a bean class with a name.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.definition
EnterpriseBeanDefinitionTest.testBeanWithNamedAnnotation()github
bd)

Test a bean class with a stereotype.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.definition
EnterpriseBeanDefinitionTest.testBeanWithStereotype()github
be)

Test a bean class with a qualifier.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.definition
EnterpriseBeanDefinitionTest.testBeanWithQualifiers()github
c)

A session bean class may extend another bean class.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.definition
EnterpriseBeanDefinitionTest.testBeanTypesAreLocalInterfacesWithoutWildcardTypesOrTypeVariablesWithSuperInterfaces()github

Section 3.2.4 - Specializing a session bean

aa)

If a bean class of a session bean X is annotated @Specializes, then the bean class of X must directly extend the bean class of another session bean Y. Then X directly specializes Y, as defined in Section 4.3 "Specialization".

Coverage

org.jboss.cdi.tck.tests.inheritance.specialization.enterprise
EnterpriseBeanSpecializationTest.testDirectSpecialization()github
da)

If the bean class of X does not directly extend the bean class of another session bean, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.inheritance.specialization.enterprise.broken.directlyExtendsSimpleBean
DirectlyExtendsSimpleBeanTest.testSpecializingClassDirectlyExtendsSimpleBean()github
org.jboss.cdi.tck.tests.inheritance.specialization.enterprise.broken.implementInterfaceAndExtendsNothing
ImplementsInterfaceAndExtendsNothingTest.testSpecializingClassImplementsInterfaceAndExtendsNothing()github
org.jboss.cdi.tck.tests.inheritance.specialization.enterprise.broken.directlyExtendsNothing
DirectlyExtendsNothingTest.testSpecializingClassDirectlyExtendsNothing()github

Section 3.2.5 - Default name for a session bean

a)

The default name for a session bean is the unqualified class name of the session bean class, after converting the first character to lower case.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.definition
EnterpriseBeanDefinitionTest.testDefaultName()github

Section 3.3 - Producer methods

aa)

A producer method must be a default-access, public, protected or private, non-abstract method of a managed bean class or session bean class.

Coverage

org.jboss.cdi.tck.tests.deployment.packaging.war.modules
WebArchiveModulesTest.testProducerAndEventDuringDisposal()github
org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testProducerOnNonBean()github
b)

A producer method may be static.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testStaticMethod()github
c)

A producer method may be non-static.

Coverage

org.jboss.cdi.tck.tests.deployment.packaging.war.modules
WebArchiveModulesTest.testProducerAndEventDuringDisposal()github
org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testDefaultBindingType()github
d)

If the bean is a session bean, the producer method must be either a business method of the EJB or a static method of the bean class

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.broken.enterprise.nonbusiness
ProducerMethodNotBusinessMethodTest.testProducerMethodOnSessionBeanMustBeBusinessMethod()github
e)

If a producer method sometimes returns a null value, then the producer method must have scope @Dependent.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testDependentProducerReturnsNullValue()github
f)

If a producer method returns a null value at runtime, and the producer method declares scope other than @Dependent, an IllegalProductException is thrown by the container. This restriction allows the container to use a client proxy, as defined in Section 5.4, "Client proxies".

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testNonDependentProducerReturnsNullValue()github
ga)

If the producer method return type is a parameterized type, it must specify an actual type parameter or type variable for each type parameter.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testParameterizedReturnType()github
ha)

If a producer method return type contains a wildcard type parameter the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.broken.parameterizedTypeWithWildcard
ParameterizedTypeWithWildcardTest.testParameterizedReturnTypeWithWildcard()github
iaa)

If the producer method return type is a parameterized type with a type variable, it must have scope @Dependent.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testTypeVariableReturnType()github
iab)

If a producer method with a parameterized return type with a type variable declares any scope other than @Dependent, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.broken.parameterizedTypeWithTypeParameter
ParameterizedReturnTypeWithTypeVariableTest.testNonDependentScopedProducerMethodWithParameterizedTypeWithTypeVariable()github
ib)

If a producer method return type is a type variable the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.broken.typeVariableReturnType
TypeVariableReturnTypeTest.testTypeVariableNotAllowed()github
j)

The application may call producer methods directly. However, if the application calls a producer method directly, no parameters will be passed to the producer method by the container; the returned object is not bound to any context; and its lifecycle is not managed by the container.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.lifecycle
ProducerMethodLifecycleTest.testWhenApplicationInvokesProducerMethodParametersAreNotInjected()github
k)

A bean may declare multiple producer methods.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testBindingType()github
ProducerMethodDefinitionTest.testScopeType()github

Section 3.3.1 - Bean types of a producer method

a)

If the return type of a producer method is an interface, the unrestricted set of bean types contains the return type, all interfaces it extends directly or indirectly and java.lang.Object

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testApiTypeForInterfaceReturn()github

If a return type of a producer method is primitive or is a Java array type, the unrestricted set of bean types contains exactly two types: the method return type and java.lang.Object.

ba)

Check primitive return type

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testApiTypeForPrimitiveReturn()github
bb)

Check array return type

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testApiTypeForArrayTypeReturn()github
c)

If the return type of a producer method is a class, the unrestricted set of bean types contains the return type, every superclass and all interfaces it implements directly or indirectly.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testApiTypeForClassReturn()github

Section 3.3.2 - Declaring a producer method

a)

A producer method may be declared by annotating a method with the @javax.enterprise.inject.Produces annotation

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testDefaultBindingType()github
ba)

A producer method may specify a scope.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testScopeType()github
ProducerMethodDefinitionTest.testStereotypeSpecifiesScope()github
bb)

A producer method may specify a name.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testNamedMethod()github
ProducerMethodDefinitionTest.testDefaultNamedMethod()github
bd)

A producer method may specify stereotypes.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testStereotypeSpecifiesScope()github
be)

A producer method may specify qualifiers.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testBindingType()github

If a producer method is annotated @Inject, has a parameter annotated @Disposes, or has a parameter annotated @Observes, the container automatically detects the problem and treats it as a definition error.

ca)

Test with a producer method annotated @Inject.

Coverage

org.jboss.cdi.tck.tests.implementation.initializer.broken.methodAnnotatedProduces
InitializerMethodAnnotatedProducesTest.testInitializerMethodAnnotatedProduces()github
da)

Test with a producer method annotated @Disposes.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.broken.parameterAnnotatedDisposes
ParameterAnnotatedDisposesTest.testProducerMethodWithParameterAnnotatedDisposes()github
ea)

Test with a producer method annotated @Observes.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.broken.parameterAnnotatedObserves
ParameterAnnotatedObservesTest.testProducerMethodWithParameterAnnotatedObserves()github
fa)

If a non-static method of a session bean class is annotated @Produces, and the method is not a business method of the session bean, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.broken.enterprise.nonbusiness
ProducerMethodNotBusinessMethodTest.testProducerMethodOnSessionBeanMustBeBusinessMethod()github
ga)

Interceptors and decorators may not declare producer methods. If an interceptor or decorator has a method annotated @Produces, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.broken.interceptor
ProducerMethodOnInterceptorTest.testProducerMethodNotAllowedOnInterceptor()github
gb)

Interceptors and decorators may not declare producer methods. If an interceptor or decorator has a method annotated @Produces, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.broken.decorator
ProducerMethodOnDecoratorTest.testProducerMethodNotAllowedOnDecorator()github
h)

A producer method may have any number of parameters.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testBindingTypesAppliedToProducerMethodParameters()github
i)

All producer method parameters are injection points.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testBindingTypesAppliedToProducerMethodParameters()github
org.jboss.cdi.tck.tests.implementation.disposal.method.definition.parameters
DisposedParameterPositionTest.testDisposedParameterPosition()github

Section 3.3.3 - Specializing a producer method

aa)

If a producer method X is annotated @Specializes, then it must be non-static and directly override another producer method Y. Then X directly specializes Y, as defined in Section 4.3 "Specialization".

Coverage

org.jboss.cdi.tck.tests.inheritance.specialization.producer.method.enterprise
EnterpriseProducerMethodSpecializationTest.testSpecializingProducerMethod()github
org.jboss.cdi.tck.tests.inheritance.specialization.producer.method
ProducerMethodSpecializationTest.testSpecializingProducerMethod()github
ba)

If a producer method is static, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.inheritance.specialization.producer.method.broken.specializesStaticMethod
SpecializesStaticMethodTest.testSpecializedStaticMethod()github
ca)

If a producer method does not directly override another producer method, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.inheritance.specialization.producer.method.broken.indirectOverride
IndirectOverrideTest.testSpecializedMethodIndirectlyOverridesAnotherProducerMethod()github

Section 3.3.4 - Default name for a producer method

The default name for a producer method is the method name, unless the method follows the JavaBeans property getter naming convention, in which case the default name is the JavaBeans property name

a)

Test default name is the method name.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition.name
ProducerMethodWithDefaultNameTest.testMethodName()github
b)

Test default name is the JavaBeans property name.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition.name
ProducerMethodWithDefaultNameTest.testJavaBeansPropertyName()github

Section 3.4 - Producer fields

aa)Just test that a producer field on these works

A producer field must be a default-access, public, protected or private, field of a managed bean class or session bean class

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.lifecycle
ProducerFieldLifecycleTest.testProducerFieldNotAnotherBean()github
ab)Just test that a producer field on these works

A producer field must be a default-access, public, protected or private, field of a managed bean class or session bean class

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition.enterprise
EnterpriseProducerFieldDefinitionTest.testStaticProducerField()github
b)

A producer field may be static.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.lifecycle
ProducerFieldLifecycleTest.testProducerStaticFieldBean()github
c)

A producer field may be non-static.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition
ProducerFieldDefinitionTest.testBeanDeclaresMultipleProducerFields()github
ca)

If the bean is a session bean, the producer field must be a static field of the bean class.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition.enterprise
EnterpriseProducerFieldDefinitionTest.testStaticProducerField()github
d)

If a producer field sometimes contains a null value when accessed, then the producer field must have scope @Dependent

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.lifecycle
ProducerFieldLifecycleTest.testProducerFieldReturnsNullIsDependent()github
e)

If a producer method contains a null value at runtime, and the producer field declares any other scope, an IllegalProductException is thrown by the container. This restriction allows the container to use a client proxy, as defined in Section 5.4, "Client proxies"

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.lifecycle
ProducerFieldLifecycleTest.testProducerFieldReturnsNullIsNotDependent()github
fa)

If the producer field type is a parameterized type, it must specify an actual type parameter or type variable for each type parameter

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition
ProducerFieldDefinitionTest.testParameterizedReturnType()github
fb)

If the producer field type is a parameterized type, it must specify an actual type parameter or type variable for each type parameter

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition
ProducerFieldDefinitionTest.testProducerFieldWithTypeVariable()github
ga)

If a producer field type contains a wildcard type parameter the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition.broken.parameterizedReturnTypeWithWildcard
ParameterizedReturnTypeWithWildcardTest.testParameterizedReturnTypeWithWildcard()github
gb)

If the producer field type is a parameterized type with a type variable, it must have scope @Dependent. If a producer field with a parameterized type with a type variable declares any scope other than @Dependent, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition.broken.typeVariable2
RequestScopedProducerFieldWithTypeVariableTest.testRequestScopedProducerFieldParameterizedWithTypeVariableNotAllowed()github
ha)

If a producer field type is a type variable the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition.broken.typeVariable
ProducerFieldWithTypeVariableTest.testProducerFieldWithTypeOfTypeVariableNotAllowed()github
i)This is a statement of intent

The application may access producer fields directly. However, if the application accesses a producer field directly, the returned object is not bound to any context; and its lifecycle is not managed by the container

j)

A bean may declare multiple producer fields

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition
ProducerFieldDefinitionTest.testBeanDeclaresMultipleProducerFields()github

Section 3.4.1 - Bean types of a producer field

a)

The bean types of a producer field depend upon the field type. If the field type is an interface, the unrestricted set of bean types contains the field type, all interfaces it extends directly or indirectly and java.lang.Object.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition
ProducerFieldDefinitionTest.testApiTypeForInterfaceReturn()github

The bean types of a producer field depend upon the field type. If a field type is primitive or is a Java array type, the unrestricted set of bean types contains exactly two types: the field type and java.lang.Object.

ba)

Check primitive type

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition
ProducerFieldDefinitionTest.testApiTypeForPrimitiveReturn()github
bb)

Check array type

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition
ProducerFieldDefinitionTest.testApiTypeForArrayTypeReturn()github
c)

The bean types of a producer field depend upon the field type. If the field type is a class, the unrestricted set of bean types contains the field type, every superclass and all interfaces it implements directly or indirectly

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition
ProducerFieldDefinitionTest.testApiTypeForClassReturn()github

Section 3.4.2 - Declaring a producer field

a)

A producer field may be declared by annotating a field with the @javax.enterprise.inject.Produces annotation.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition
ProducerFieldDefinitionTest.testBeanDeclaresMultipleProducerFields()github
b)

A producer field may specify a scope.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition
ProducerFieldDefinitionTest.testScopeType()github
c)

A producer field may specify a name.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition
ProducerFieldDefinitionTest.testNamedField()github
e)

A producer field may specify stereotypes.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition
ProducerFieldDefinitionTest.testStereotype()github
f)

A producer field may specify qualifiers.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition
ProducerFieldDefinitionTest.testBindingType()github
g)

If a producer field is annotated @Inject, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition.broken.inject
InjectAnnotatedProducerFieldTest.testInjectAnnotatedProducerFieldNotAllowed()github
h)

If a non-static field of a session bean class is annotated @Produces, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition.broken.enterprise.nonstatic
NonStaticFieldOfSessionBeanTest.testNonStaticFieldOfSessionBeanCannotBeProducerField()github
ia)

Interceptors and decorators may not declare producer fields. If an interceptor or decorator has a field annotated @Produces, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition.broken.interceptor
ProducerFieldOnInterceptorTest.testProducerFieldNotAllowedOnInterceptor()github
ib)

Interceptors and decorators may not declare producer fields. If an interceptor or decorator has a field annotated @Produces, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition.broken.decorator
ProducerFieldOnDecoratorTest.testProducerFieldNotAllowedOnDecorator()github

Section 3.4.3 - Default name for a producer field

a)

The default name for a producer field is the field name

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition
ProducerFieldDefinitionTest.testDefaultNamedByStereotype()github

Section 3.5 - Disposer methods

aa)

A disposer method must be a default-access, public, protected or private, non-abstract method of a managed bean class or session bean class.

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition
DisposalMethodDefinitionTest.testDisposalMethodOnNonBean()github
b)

A disposer method may be static.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testStaticDisposerMethod()github
org.jboss.cdi.tck.tests.implementation.disposal.method.definition
DisposalMethodDefinitionTest.testBindingTypesAppliedToDisposalMethodParameters()github
c)

A disposer method may be non-static.

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition
DisposalMethodDefinitionTest.testBindingTypesAppliedToDisposalMethodParameters()github
d)

If the bean is a session bean, the disposer method must be a business method of the EJB or a static method of the bean class.

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition.broken.methodOnSessionBean
DisposalMethodOnSessionBeanTest.testDisposalMethodNotBusinessOrStatic()github
e)

A bean may declare multiple disposer methods.

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition
DisposalMethodDefinitionTest.testBindingTypesAppliedToDisposalMethodParameters()github

Section 3.5.1 - Disposed parameter of a disposer method

a)

Each disposer method must have exactly one disposed parameter, of the same type as the corresponding producer method return type or producer field type.

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition.broken.multiParams
MultipleDisposeParametersDefinitionTest.testMultipleDisposeParameters()github
org.jboss.cdi.tck.tests.implementation.disposal.method.definition.parameters
DisposedParameterPositionTest.testDisposedParameterPosition()github
ba)

When searching for disposer methods for a producer method or producer field the container considers the type and qualifiers of the disposed parameter. f a producer method or producer field declared by the same bean class is assignable to the disposed parameter, according to the rules of typesafe resolution defined in Section 5.2, "Typesafe resolution", the container must call this method when destroying any instance returned by that producer method or producer field.

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition
DisposalMethodDefinitionTest.testBindingTypesAppliedToDisposalMethodParameters()github
DisposalMethodDefinitionTest.testDisposalMethodOnNonBean()github
da)

A disposer method may resolve to multiple producer methods or producer fields declared by the bean class, in which case the container must call it when destroying any instance returned by any of these producer methods or producer fields.

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition
DisposalMethodDefinitionTest.testDisposalMethodForMultipleProducerMethods()github

Section 3.5.2 - Declaring a disposer method

a)

A disposer method may be declared by annotating a parameter @javax.enterprise.inject.Disposes. That parameter is the disposed parameter

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition
DisposalMethodDefinitionTest.testBindingTypesAppliedToDisposalMethodParameters()github
b0)

Qualifiers may be declared by annotating the disposed parameter.

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition
DisposalMethodDefinitionTest.testBindingTypesAppliedToDisposalMethodParameters()github
ba)

If a method has more than one parameter annotated @Disposes, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition.broken.multiParams
MultipleDisposeParametersDefinitionTest.testMultipleDisposeParameters()github
ca)

If a disposer method is annotated @Produces, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition.broken.producesUnallowed
ProducesUnallowedDefinitionTest.testProducesUnallowed()github
da)

If a disposer method is annotated @Inject, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition.broken.initializerUnallowed
InitializerUnallowedDefinitionTest.testInitializerUnallowed()github
ea)

If a disposer method has a parameter annotated @Observes, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition.broken.observesUnallowed
ObserverParameterUnallowedDefinitionTest.testObserverParameterUnallowed()github
fa)

If a non-static method of a session bean class has a parameter annotated @Disposes, and the method is not a business method of the session bean, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition.broken.methodOnSessionBean
DisposalMethodOnSessionBeanTest.testDisposalMethodNotBusinessOrStatic()github
ga)

Interceptors and decorators may not declare disposer methods. If an interceptor or decorator has a method annotated @Disposes, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition.broken.interceptor
DisposerMethodOnInterceptorTest.testDisposerMethodNotAllowedOnInterceptor()github
gb)

Interceptors and decorators may not declare disposer methods. If an interceptor or decorator has a method annotated @Disposes, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition.broken.decorator
DisposerMethodOnDecoratorTest.testDisposerMethodNotAllowedOnDecorator()github
h)

In addition to the disposed parameter, a disposer method may declare additional parameters, which may also specify qualifiers. These additional parameters are injection points.

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition
DisposalMethodDefinitionTest.testDisposalMethodParametersGetInjected()github
org.jboss.cdi.tck.tests.implementation.disposal.method.definition.parameters
DisposedParameterPositionTest.testDisposedParameterPosition()github

Section 3.5.3 - Disposer method resolution

aa)

A disposer method is bound to a producer method if the producer method is declared by the same bean class as the disposer method, and the producer method is assignable to the disposed parameter, according to the rules of typesafe resolution defined in Section 5.2, "Typesafe resolution".

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition
DisposalMethodDefinitionTest.testBindingTypesAppliedToDisposalMethodParameters()github
ab)

A disposer method is bound to a producer field if the producer field is declared by the same bean class as the disposer method, and the producer field is assignable to the disposed parameter, according to the rules of typesafe resolution defined in Section 5.2, "Typesafe resolution".

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition
DisposalMethodDefinitionTest.testDisposalMethodCalledForProducerField()github
ba)

If there are multiple disposer methods for a single producer method or producer field, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition.broken.multipleDisposersForProducer
MultipleDisposerMethodsForProducerMethodTest.testMultipleDisposerMethodsForProducerMethodNotAllowed()github
ca)

If there is no producer method or producer field declared by the bean class that is assignable to the disposed parameter of a disposer method, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition.broken.unresolvedMethod
UnresolvedDisposalMethodDefinitionTest.testUnresolvedDisposalMethod()github

Section 3.6 - Resources

ka)Statement about non-portable behavior

The container is not required to support resources with scope other than @Dependent.

l)Doesn't mention the consequences of this

A resource may not declare a bean EL name

Section 3.6.1 - Declaring a resource

aa)Introductory text for the folloiwing assertions

A resource may be declared by specifying a Java EE component environment injection annotation as part of a producer field declaration.

bb)

For a Java EE resource, @Resource must be specified.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.resource.resource
InjectionOfResourceTest.testInjectionOfResource()github
org.jboss.cdi.tck.tests.implementation.simple.resource.env
EnvInjectionTest.testInjectionOfEnv()github
cc)

For a persistence context, @PersistenceContext must be specified.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.resource.persistenceContext
PersistenceContextInjectionTest.testInjectionOfPersistenceContext()github
dd)

For a persistence unit, @PersistenceUnit must be specified.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.resource.persistenceContext
PersistenceContextInjectionTest.testInjectionOfPersistenceUnit()github
ee)

For a remote EJB, @EJB must be specified.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.resource.ejb
EjbInjectionTest.testInjectionOfEjbs()github
ff)

For a web service, @WebServiceRef must be specified.

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual.ws
WebServiceResourceTest.testResourceBeanTypes()github
gg)This is defined in other specs

The injection annotation specifies the metadata needed to obtain the resources, entity manager, entity manager factory, remote EJB instance or web service reference from the component environment.

hh)

The bean type and qualifiers of the resource are determined by the producer field declaration.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.resource.persistenceContext
PersistenceContextInjectionTest.testBeanTypesAndBindingTypesOfPersistenceContext()github
i)

If the producer field declaration specifies an EL name, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.resource.broken.name
ResourceDefinitionWithNameTest.testDeployment()github
j)

If the matching object in the Java EE component environment is not of the same type as the producer field declaration, the container automatically detects the problem and treats it as a definition errors.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.resource.broken.type.ws
ResourceDefinitionWithDifferentTypeTest.testDeployment()github
org.jboss.cdi.tck.tests.implementation.simple.resource.broken.type.persistence
ResourceDefinitionWithDifferentTypeTest.testDeployment()github
org.jboss.cdi.tck.tests.implementation.simple.resource.broken.type.env
ResourceDefinitionWithDifferentTypeTest.testDeployment()github
org.jboss.cdi.tck.tests.implementation.simple.resource.broken.type
ResourceDefinitionWithDifferentTypeTest.testDeployment()github
org.jboss.cdi.tck.tests.implementation.simple.resource.broken.type.ejb
ResourceDefinitionWithDifferentTypeTest.testDeployment()github

Section 3.6.2 - Bean types of a resource

The unrestricted set of bean types of a resource is determined by the declared type of the producer field, as specified by Section 3.4.1, "Bean types of a producer field".

aa)

Check @Resource

Coverage

org.jboss.cdi.tck.tests.implementation.simple.resource.resource
InjectionOfResourceTest.testResourceBeanTypes()github
org.jboss.cdi.tck.tests.implementation.simple.resource.env
EnvInjectionTest.testResourceBeanTypes()github
ab)

Check @PersistenceContext

Coverage

org.jboss.cdi.tck.tests.implementation.simple.resource.persistenceContext
PersistenceContextInjectionTest.testBeanTypesAndBindingTypesOfPersistenceContext()github
ac)

Check @PersistenceUnit

Coverage

org.jboss.cdi.tck.tests.implementation.simple.resource.persistenceContext
PersistenceContextInjectionTest.testBeanTypesOfPersistenceUnit()github
ad)

Check @EJB

Coverage

org.jboss.cdi.tck.tests.implementation.simple.resource.ejb
EjbInjectionTest.testResourceBeanTypes()github
ae)

Check @WebServiceRef

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual.ws
WebServiceResourceTest.testResourceBeanTypes()github

Section 3.7 - Additional built-in beans

a)

A Java EE or embeddable EJB container must provide a bean with qualifier @Default and bean type javax.transaction.UserTransaction, allowing injection of a reference to the JTA UserTransaction.

Coverage

org.jboss.cdi.tck.tests.implementation.builtin
BuiltInBeansTest.testUserTransactionBean()github
b)

A Java EE or embeddable EJB container must provide a bean with qualifier @Default and bean type javax.security.Principal, allowing injection of a Principal representing the current caller identity.

Coverage

org.jboss.cdi.tck.tests.implementation.builtin
BuiltInBeansTest.testPrincipalBean()github
da)

A servlet container must provide a bean with qualifier @Default and bean type javax.servlet.http.HttpServletRequest, allowing injection of a reference to the HttpServletRequest. This bean is passivation capable dependency, as defined in Section 6.6.2, "Passivation capable dependencies".

Coverage

org.jboss.cdi.tck.tests.implementation.builtin.servlet
ServletContainerBuiltinBeanTest.testBuiltinBeansAvailableForInjection()github
ServletContainerBuiltinBeanTest.testBuiltinBeansFromClient()github
db)

A servlet container must provide a bean with qualifier @Default and bean type javax.servlet.http.HttpSession, allowing injection of a reference to the HttpSession. This bean is passivation capable dependency, as defined in Section 6.6.2, "Passivation capable dependencies".

Coverage

org.jboss.cdi.tck.tests.implementation.builtin.servlet
ServletContainerBuiltinBeanTest.testBuiltinBeansAvailableForInjection()github
ServletContainerBuiltinBeanTest.testBuiltinBeansFromClient()github
dc)

A servlet container must provide a bean with qualifier @Default and bean type javax.servlet.ServletContext, allowing injection of a reference to the ServletContext. This bean is passivation capable dependency, as defined in Section 6.6.2, "Passivation capable dependencies".

Coverage

org.jboss.cdi.tck.tests.implementation.builtin.servlet
ServletContainerBuiltinBeanTest.testBuiltinBeansAvailableForInjection()github
ServletContainerBuiltinBeanTest.testBuiltinBeansFromClient()github
e)

If a Java EE component class has an injection point of type UserTransaction and qualifier @Default, and may not validly make use of the JTA UserTransaction according to the Java EE platform specification, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.builtin.broken.transaction
UserTransactionInvalidInjectionTest.testUserTransactionInjection()github

Section 3.8 - Bean constructors

a)

When the container instantiates a bean, it calls the bean constructor. The bean constructor is a default-access, public, protected or private constructor of the bean class.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.definition
SimpleBeanDefinitionTest.testEmptyConstructorUsed()github

Section 3.8.1 - Declaring a bean constructor

The bean constructor may be identified by annotating the constructor @Inject

aa)

Test an @Inject constructor is used on a managed bean

Coverage

org.jboss.cdi.tck.tests.implementation.simple.definition
SimpleBeanDefinitionTest.testInitializerAnnotatedConstructor()github
org.jboss.cdi.tck.tests.implementation.simple.lifecycle
SimpleBeanLifecycleTest.testCreateInjectsFieldsDeclaredInJava()github
org.jboss.cdi.tck.tests.implementation.simple.definition
SimpleBeanDefinitionTest.testInitializerAnnotatedConstructorUsedOverEmptyConstuctor()github
ab)

Test an @Inject constructor is used on a session bean

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.definition
EnterpriseBeanDefinitionTest.testConstructorAnnotatedInjectCalled()github
ba)Can't check implicit constructor

If a bean class does not explicitly declare a constructor using @Inject, the constructor that accepts no parameters is the bean constructor.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.definition
SimpleBeanDefinitionTest.testEmptyConstructorUsed()github
ca)

If a bean class has more than one constructor annotated @Inject, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.definition.tooManyInitializerAnnotatedConstructors
TooManyInitializerAnnotatedConstructorsTest.testTooManyInitializerAnnotatedConstructor()github
da)

If a bean constructor has a parameter annotated @Disposes, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.definition.constructorHasDisposesParameter
ConstructorHasDisposesParameterTest.testConstructorHasDisposesParameter()github
ea)

If a bean constructor has a parameter annotated @Observes, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.definition.constructorHasObservesParameter
ConstructorHasObservesParameterTest.testConstructorHasObservesParameter()github
f)

A bean constructor may have any number of parameters.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.lifecycle
SimpleBeanLifecycleTest.testInjectionOfParametersIntoBeanConstructor()github
g)

All parameters of a bean constructor are injection points.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.lifecycle
SimpleBeanLifecycleTest.testQualifierTypeAnnotatedConstructor()github
SimpleBeanLifecycleTest.testInjectionOfParametersIntoBeanConstructor()github

Section 3.9 - Injected fields

An injected field is a non-static, non-final field of a bean class, a non-static, non-final field of an enum, or of any Java EE component class supporting injection.

a)

Test a bean class.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.lifecycle
SimpleBeanLifecycleTest.testCreateInjectsFieldsDeclaredInJava()github
b)

Test a Java EE component class.

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
InjectionIntoNonContextualComponentTest.testInjectionIntoServlet()github
InjectionIntoNonContextualComponentTest.testInjectionIntoFilter()github
InjectionIntoNonContextualComponentTest.testInjectionIntoServletListener()github
InjectionIntoNonContextualComponentTest.testInjectionIntoTagHandler()github
InjectionIntoNonContextualComponentTest.testInjectionIntoTagLibraryListener()github
InjectionIntoNonContextualComponentTest.testInjectionIntoJSFManagedBean()github
c)

Test an enum.

Coverage

org.jboss.cdi.tck.tests.lookup.injection.enums
EnumInjectionTest.testBasicEnum()github
EnumInjectionTest.testAdvancedEnum()github

Section 3.9.1 - Declaring an injected field

aa)

An injected field may be declared by annotating the field @javax.inject.Inject.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.lifecycle
SimpleBeanLifecycleTest.testCreateInjectsFieldsDeclaredInJava()github
org.jboss.cdi.tck.tests.lookup.injection.enums
EnumInjectionTest.testBasicEnum()github
b)

If an injected field is annotated @Produces, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.definition.broken.field
InjectedFieldAnnotatedWithProducesTest.testDeployment()github

Section 3.10 - Initializer methods

An initializer method is a default-access, public, protected or private, non-abstract, non-static, non-generic method of a bean class, a non-abstract, non-static method of an enum or of any Java EE component class supporting injection.

a)

Test a bean-class.

Coverage

org.jboss.cdi.tck.tests.implementation.initializer
InitializerMethodTest.testBindingTypeOnInitializerParameter()github
b)

Test a Java EE component class.

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
InjectionIntoNonContextualComponentTest.testServletInitializerMethodCalled()github
InjectionIntoNonContextualComponentTest.testFilterInitializerMethodCalled()github
InjectionIntoNonContextualComponentTest.testServletListenerInitializerMethodCalled()github
InjectionIntoNonContextualComponentTest.testTagLibraryListenerInitializerMethodCalled()github
c)

Test an enum.

Coverage

org.jboss.cdi.tck.tests.lookup.injection.enums
EnumInjectionTest.testBasicEnum()github
EnumInjectionTest.testAdvancedEnum()github
e)

If the bean is a session bean, the initializer method is not required to be a business method of the session bean.

Coverage

org.jboss.cdi.tck.tests.implementation.initializer
EjbInitializerMethodTest.testInitializerMethodNotABusinessMethod()github
f)

Method interceptors are never called when the container calls an initializer method

Coverage

org.jboss.cdi.tck.tests.interceptors.invocation
InterceptorInvocationTest.testInitializerMethodsNotIntercepted()github
g)

A bean class may declare multiple (or zero) initializer methods

Coverage

org.jboss.cdi.tck.tests.implementation.initializer
InitializerMethodTest.testMultipleInitializerMethodsAreCalled()github
h)This is a statement of intent

The application may call initializer methods directly, but then no parameters will be passed to the method by the container

Section 3.10.1 - Declaring an initializer method

a)

An initializer method may be declared by annotating the method @javax.inject.Inject

Coverage

org.jboss.cdi.tck.tests.implementation.initializer
InitializerMethodTest.testMultipleInitializerMethodsAreCalled()github
ab)

If a generic method of a bean is annotated @Inject, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.initializer.broken.generic
GenericInitializerMethodTest.testGenericInitializerMethodNotAllowed()github
ba)

If an initializer method is annotated @Produces, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.initializer.broken.methodAnnotatedProduces
InitializerMethodAnnotatedProducesTest.testInitializerMethodAnnotatedProduces()github
ca)

If an initializer method has a parameter annotated @Disposes, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.initializer.broken.parameterAnnotatedDisposes
ParameterAnnotatedDisposesTest.testInitializerMethodHasParameterAnnotatedDisposes()github
da)

If an initializer method has a parameter annotated @Observes, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.initializer.broken.parameterAnnotatedObserves
ParameterAnnotatedObservesTest.testInitializerMethodHasParameterAnnotatedObserves()github
e)

An initializer method may have any number of parameters.

Coverage

org.jboss.cdi.tck.tests.implementation.initializer
InitializerMethodTest.testMultipleInitializerMethodsAreCalled()github
f)

All initializer method parameters are injection points.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.lifecycle
EnterpriseBeanLifecycleTest.testInitializerMethodsCalledWithCurrentParameterValues()github
org.jboss.cdi.tck.tests.implementation.initializer
InitializerMethodTest.testBindingTypeOnInitializerParameter()github

Section 3.11 - The default qualifier at injection points

a)

If an injection point declares no qualifier, the injection point has exactly one qualifier, the default qualifier @Default.

Coverage

org.jboss.cdi.tck.tests.event
EventTest.testObserverMethodParameterInjectionPoints()github
org.jboss.cdi.tck.tests.implementation.disposal.method.definition
DisposalMethodDefinitionTest.testDisposalMethodParametersGetInjected()github
org.jboss.cdi.tck.tests.implementation.initializer
InitializerMethodTest.testMultipleInitializerMethodsAreCalled()github

Section 3.12 - Vetoing types

a)

Any type or package may be prevented from being considered by CDI by adding the @Vetoed annotation on the type or package.

Coverage

org.jboss.cdi.tck.tests.vetoed.enterprise
EnterpriseVetoedTest.testClassLevelVeto()github
EnterpriseVetoedTest.testAnnotatedTypeAddedByExtension()github
org.jboss.cdi.tck.tests.vetoed
VetoedTest.testClassLevelVeto()github
VetoedTest.testVetoedAnnotation()github
VetoedTest.testVetoedEnum()github
VetoedTest.testPackageLevelVeto()github
VetoedTest.testAnnotatedTypeAddedByExtension()github

Section 3.13 - The qualifier @Named at injection points

a)

If an injected field declares a @Named annotation that does not specify the value member, the name of the field is assumed.

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint.named
NamedAtInjectionPointTest.testFieldNameUsedAsBeanName()github
b)

If any other injection point declares a @Named annotation that does not specify the value member, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.lookup.byname.broken.injectionPointWithNamed
NamedNonFieldInjectionPointTest.testNamedProducerInjectionPointNotAllowed()github
org.jboss.cdi.tck.tests.lookup.byname.broken.injectionPointWithNamed2
NamedNonFieldInjectionPointTest.testNamedObserverMethodInjectionPointNotAllowed()github
org.jboss.cdi.tck.tests.lookup.byname.broken.injectionPointWithNamed3
NamedNonFieldInjectionPointTest.testNamedInitializerMethodInjectionPointNotAllowed()github

Section 3.14 - @New qualified beans

d)

For each managed bean, a second bean exists which has the same bean class.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.newSimpleBean
NewSimpleBeanTest.testForEachSimpleBeanANewBeanExists()github
e)

For each managed bean, a second bean exists which has the same bean types.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.newSimpleBean
NewSimpleBeanTest.testNewBeanHasTheSameBeanTypes()github
f)

For each managed bean, a second bean exists which has the same bean constructor.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.newSimpleBean
NewSimpleBeanTest.testNewBeanHasSameConstructor()github
g)

For each managed bean, a second bean exists which has the same initializer methods.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.newSimpleBean
NewSimpleBeanTest.testNewBeanHasSameInitializers()github
h)

For each managed bean, a second bean exists which has the same injected fields.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.newSimpleBean
NewSimpleBeanTest.testNewBeanHasSameInjectedFields()github
i)

For each managed bean, a second bean exists which has the same interceptor bindings.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.newSimpleBean
NewSimpleBeanTest.testNewBeanHasTheSameInterceptorBindings()github
j)

For each session bean, a second bean exists which has the same bean class.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.newBean
NewEnterpriseBeanTest.testForEachEnterpriseBeanANewBeanExists()github
k)

For each session bean, a second bean exists which has the same bean types.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.newBean
NewEnterpriseBeanTest.testForEachEnterpriseBeanANewBeanExists()github
l)

For each session bean, a second bean exists which has the same bean constructor.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.newBean
NewEnterpriseBeanICTest.testNewBeanHasSameConstructor()github
m)

For each session bean, a second bean exists which has the same initializer methods.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.newBean
NewEnterpriseBeanICTest.testNewBeanHasSameInitializers()github
n)

For each session bean, a second bean exists which has the same injected fields.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.newBean
NewEnterpriseBeanTest.testNewBeanHasSameInjectedFields()github
o)

For each session bean, a second bean exists which has the same interceptor bindings.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.newBean
NewEnterpriseBeanTest.testNewBeanHasTheSameInterceptorBindings()github
p)

This second bean has scope @Dependent.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.newBean
NewEnterpriseBeanTest.testNewBeanIsDependentScoped()github
r)

This second bean has exactly one qualifier: @javax.enterprise.inject.New(X.class) where x is the bean class.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.newBean
NewEnterpriseBeanTest.testNewBeanHasOnlyOneQualifier()github
s)

This second bean has no bean EL name.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.newBean
NewEnterpriseBeanTest.testNewBeanHasNoBeanELName()github
t)

This second bean has no stereotypes.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.newBean
NewEnterpriseBeanTest.testNewBeanHasNoStereotypes()github
org.jboss.cdi.tck.tests.implementation.simple.newSimpleBean
NewSimpleBeanTest.testNewBeanHasNoStereotypes()github
u)

This second bean has no observer methods.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.newBean
NewEnterpriseBeanTest.testNewBeanHasNoObservers()github
org.jboss.cdi.tck.tests.implementation.simple.newSimpleBean
NewSimpleBeanTest.testNewBeanHasNoObservers()github
v)

This second bean has no producer methods.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.newBean
NewEnterpriseBeanICTest.testNewBeanHasNoProducerMethods()github
org.jboss.cdi.tck.tests.implementation.simple.newSimpleBean
NewSimpleBeanTest.testNewBeanHasNoProducerMethods()github
w)

This second bean has no producer fields.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.newSimpleBean
NewSimpleBeanTest.testNewBeanHasNoProducerFields()github
x)

This second bean has no disposer methods.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.newBean
NewEnterpriseBeanICTest.testNewBeanHasNoDisposalMethods()github
org.jboss.cdi.tck.tests.implementation.simple.newSimpleBean
NewSimpleBeanTest.testNewBeanHasNoDisposerMethods()github
xb)

This second bean is not an alternative.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.newSimpleBean
NewSimpleBeanTest.testNewBeanIsNotAlternative()github
xc)

This second bean is enabled, in the sense of Section 5.1.2, "Enabled and disabled beans", if and only if some other enabled bean has an injection point with the qualifier @New(X.class) where X is the bean class.

Coverage

org.jboss.cdi.tck.tests.lookup.dynamic
DynamicLookupTest.testNewBeanNotEnabledWithouInjectionPoint()github
xd)

This bean is called the @New qualified bean for the class X.

Note that this second bean exists, and may be enabled and available for injection even if the first bean is disabled, as defined by Section 5.1.2, “Enabled and disabled beans” or if the bean class is deployed outside of a bean deployment archive, as defined in Section 12.1, “Bean deployment archives”, and is therefore not discovered during the bean discovery process defined in Chapter 12, Packaging and deployment. The container discovers @New qualified beans by inspecting injection points of other enabled beans.

ya)

Check that @New on a field injection point outside the BDA, but in the classpath causes a bean with qualifier @New and the given type to be created

Coverage

org.jboss.cdi.tck.tests.implementation.simple.newSimpleBean
NewSimpleBeanTest.testNewBeanCreatedForFieldInjectionPoint()github
yb)

Check that @New on a field injection point (which is a session bean class) outside the BDA, but in the classpath causes a session bean with qualifier @New and the given type to be created

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.newBean
NewEnterpriseBeanTest.testNewBeanCreatedForFieldInjectionPoint()github
yc)

Check that @New on a initializer method injection point outside the BDA, but in the classpath causes a bean with qualifier @New and the given type to be created

Coverage

org.jboss.cdi.tck.tests.implementation.simple.newSimpleBean
NewSimpleBeanTest.testNewBeanCreatedForInitializerInjectionPoint()github
yd)

Check that @New on a initializer method injection point (which is a session bean class) outside the BDA, but in the classpath causes a session bean with qualifier @New and the given type to be created

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.newBean
NewEnterpriseBeanTest.testNewBeanCreatedForInitializerInjectionPoint()github
ye)

Check that @New on a constructor injection point outside the BDA, but in the classpath causes a bean with qualifier @New and the given type to be created

Coverage

org.jboss.cdi.tck.tests.implementation.simple.newSimpleBean
NewSimpleBeanTest.testNewBeanCreatedForConstructorInjectioAnPoint()github
yf)

Check that @New on a constructor injection point (which is a session bean class) outside the BDA, but in the classpath causes a session bean with qualifier @New and the given type to be created

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.newBean
NewEnterpriseBeanTest.testNewBeanCreatedForConstructorInjectionPoint()github
yg)

Check that @New on a producer method injection point outside the BDA, but in the classpath causes a bean with qualifier @New and the given type to be created

Coverage

org.jboss.cdi.tck.tests.implementation.simple.newSimpleBean
NewSimpleBeanTest.testNewBeanCreatedForProducerMethod()github
yh)

Check that @New on a producer method injection point (which is a session bean class) outside the BDA, but in the classpath causes a session bean with qualifier @New and the given type to be created

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.newBean
NewEnterpriseBeanTest.testNewBeanCreatedForProducerMethod()github
yi)

Check that @New on a observer method injection point outside the BDA, but in the classpath causes a bean with qualifier @New and the given type to be created

Coverage

org.jboss.cdi.tck.tests.implementation.simple.newSimpleBean
NewSimpleBeanTest.testNewBeanCreatedForObserverMethod()github
yj)

Check that @New on a observer method injection point (which is a session bean class) outside the BDA, but in the classpath causes a session bean with qualifier @New and the given type to be created

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.newBean
NewEnterpriseBeanTest.testNewBeanCreatedForObserverMethod()github
yk)

Check that @New on a disposer method injection point outside the BDA, but in the classpath causes a bean with qualifier @New and the given type to be created

Coverage

org.jboss.cdi.tck.tests.implementation.simple.newSimpleBean
NewSimpleBeanTest.testNewBeanCreatedForDisposerMethod()github
yl)

Check that @New on a disposer method injection point (which is a session bean class) outside the BDA, but in the classpath causes a session bean with qualifier @New and the given type to be created

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.newBean
NewEnterpriseBeanTest.testNewBeanCreatedForDisposerMethod()github
z)

When the qualifier @New is specified at an injection point and no value member is explicitly specified, the container defaults the value to the declared type of the injection point.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.newSimpleBean
NewSimpleBeanTest.testNewBeanWithNoMemberValue()github

Section 4.1 - Inheritance of type-level metadata

Suppose a class X is extended directly or indirectly by the bean class of a managed bean or session bean Y. If X is annotated with a qualifier type, stereotype or interceptor binding type Z then Y inherits the annotation if and only if Z declares the @Inherited meta-annotation and neither Y nor any intermediate class that is a subclass of X and a superclass of Y declares an annotation of type Z.

aa)

Test qualifier type for directly extended managed bean annotated @Inherited is inherited.

Coverage

org.jboss.cdi.tck.tests.definition.qualifier
QualifierDefinitionTest.testQualifierDeclaredInheritedIsInherited()github
QualifierDefinitionTest.testQualifierDeclaredInheritedIsBlockedByIntermediateClass()github
org.jboss.cdi.tck.tests.alternative.resolution.qualifier
QualifierInheritedTest.testResolution()github
aaa)

Test qualifier type for directly extended managed bean not annotated @Inherited is not inherited.

Coverage

org.jboss.cdi.tck.tests.definition.qualifier
QualifierDefinitionTest.testQualifierNotDeclaredInheritedIsNotInherited()github
org.jboss.cdi.tck.tests.alternative.resolution.qualifier
QualifierNotInheritedTest.testResolution()github
ab)

Test stereotype for directly extended managed bean annotated @Inherited is inherited.

Coverage

org.jboss.cdi.tck.tests.definition.stereotype
StereotypeDefinitionTest.testStereotypeDeclaredInheritedIsInherited()github
org.jboss.cdi.tck.tests.definition.scope
ScopeDefinitionTest.testWebBeanScopeTypeOverridesStereotype()github
aba)

Test stereotype for directly extended managed bean not annotated @Inherited is not inherited.

Coverage

org.jboss.cdi.tck.tests.definition.stereotype
StereotypeDefinitionTest.testStereotypeNotDeclaredInheritedIsNotInherited()github
ad)

Test interceptor binding type for directly extended managed bean annotated @Inherited is inherited.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.inheritance
InterceptorBindingInheritanceTest.testInterceptorBindingDirectlyInheritedFromManagedBean()github
ada)

Test interceptor binding type for directly extended managed bean not annotated @Inherited is not inherited.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.inheritance
InterceptorBindingInheritanceTest.testInterceptorBindingDirectlyInheritedFromManagedBean()github
ag)

Test qualifier type for indirectly extended managed bean annotated @Inherited is inherited.

Coverage

org.jboss.cdi.tck.tests.definition.qualifier
QualifierDefinitionTest.testQualifierDeclaredInheritedIsIndirectlyInherited()github
aga)

Test qualifier type for indirectly extended managed bean not annotated @Inherited is not inherited.

Coverage

org.jboss.cdi.tck.tests.definition.qualifier
QualifierDefinitionTest.testQualifierNotDeclaredInheritedIsNotIndirectlyInherited()github
ah)

Test stereotype for indirectly extended managed bean annotated @Inherited is inherited.

Coverage

org.jboss.cdi.tck.tests.definition.stereotype
StereotypeDefinitionTest.testStereotypeDeclaredInheritedIsIndirectlyInherited()github
aha)

Test stereotype for indirectly extended managed bean not annotated @Inherited is not inherited.

Coverage

org.jboss.cdi.tck.tests.definition.stereotype
StereotypeDefinitionTest.testStereotypeNotDeclaredInheritedIsNotIndirectlyInherited()github
aj)

Test interceptor binding type for indirectly extended managed bean annotated @Inherited is inherited.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.inheritance
InterceptorBindingInheritanceTest.testInterceptorBindingIndirectlyInheritedFromManagedBean()github
aja)

Test interceptor binding type for indirectly extended managed bean not annotated @Inherited is not inherited.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.inheritance
InterceptorBindingInheritanceTest.testInterceptorBindingIndirectlyInheritedFromManagedBean()github
al)

Test qualifier type for directly extended session bean annotated @Inherited is inherited.

Coverage

org.jboss.cdi.tck.tests.definition.qualifier.enterprise
EnterpriseQualifierDefinitionTest.testQualifierDeclaredInheritedIsInherited()github
ala)

Test qualifier type for directly extended session bean not annotated @Inherited is not inherited.

Coverage

org.jboss.cdi.tck.tests.definition.qualifier.enterprise
EnterpriseQualifierDefinitionTest.testQualifierNotDeclaredInheritedIsNotInherited()github
am)

Test stereotype for directly extended session bean annotated @Inherited is inherited.

Coverage

org.jboss.cdi.tck.tests.definition.stereotype.enterprise
EnterpriseStereotypeDefinitionTest.testStereotypeDeclaredInheritedIsInherited()github
ama)

Test stereotype for directly extended session bean not annotated @Inherited is not inherited.

Coverage

org.jboss.cdi.tck.tests.definition.stereotype.enterprise
EnterpriseStereotypeDefinitionTest.testStereotypeNotDeclaredInheritedIsNotInherited()github
an)

Test interceptor binding type for directly extended session bean annotated @Inherited is inherited.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.inheritance
InterceptorBindingInheritanceTest.testInterceptorBindingDirectlyInheritedFromSessionBean()github
ana)

Test interceptor binding type for directly extended session bean not annotated @Inherited is not inherited.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.inheritance
InterceptorBindingInheritanceTest.testInterceptorBindingDirectlyInheritedFromSessionBean()github
ap)

Test qualifier type for indirectly extended session bean annotated @Inherited is inherited.

Coverage

org.jboss.cdi.tck.tests.definition.qualifier.enterprise
EnterpriseQualifierDefinitionTest.testQualifierDeclaredInheritedIsIndirectlyInherited()github
apa)

Test qualifier type for indirectly extended session bean not annotated @Inherited is not inherited.

Coverage

org.jboss.cdi.tck.tests.definition.qualifier.enterprise
EnterpriseQualifierDefinitionTest.testQualifierNotDeclaredInheritedIsNotIndirectlyInherited()github
aq)

Test stereotype for indirectly extended session bean annotated @Inherited is inherited.

Coverage

org.jboss.cdi.tck.tests.definition.stereotype.enterprise
EnterpriseStereotypeDefinitionTest.testStereotypeDeclaredInheritedIsIndirectlyInherited()github
aqa)

Test stereotype for indirectly extended session bean not annotated @Inherited is not inherited.

Coverage

org.jboss.cdi.tck.tests.definition.stereotype.enterprise
EnterpriseStereotypeDefinitionTest.testStereotypeNotDeclaredInheritedIsNotIndirectlyInherited()github
ar)

Test interceptor binding type for indirectly extended session bean annotated @Inherited is inherited.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.inheritance
InterceptorBindingInheritanceTest.testInterceptorBindingIndirectlyInheritedFromSessionBean()github
ara)

Test interceptor binding type for indirectly extended session bean not annotated @Inherited is not inherited.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.inheritance
InterceptorBindingInheritanceTest.testInterceptorBindingIndirectlyInheritedFromSessionBean()github

Suppose a class X is extended directly or indirectly by the bean class of a managed bean or session bean Y. If X is annotated with a scope type Z then Y inherits the annotation if and only if Z declares the @Inherited meta-annotation and neither Y nor any intermediate class that is a subclass of X and a superclass of Y declares a scope type.

ba)

Test scope type for directly extended managed bean annotated @Inherited is inherited.

Coverage

org.jboss.cdi.tck.tests.definition.scope
ScopeDefinitionTest.testScopeTypeDeclaredInheritedIsInherited()github
ScopeDefinitionTest.testScopeTypeDeclaredInheritedIsBlockedByIntermediateScopeTypeMarkedInherited()github
ScopeDefinitionTest.testScopeTypeDeclaredInheritedIsBlockedByIntermediateScopeTypeNotMarkedInherited()github
baa)

Test scope type for directly extended managed bean not annotated @Inherited is not inherited.

Coverage

org.jboss.cdi.tck.tests.definition.scope
ScopeDefinitionTest.testScopeTypeNotDeclaredInheritedIsNotInherited()github
bc)

Test scope type for indirectly extended managed bean annotated @Inherited is inherited.

Coverage

org.jboss.cdi.tck.tests.definition.scope
ScopeDefinitionTest.testScopeTypeDeclaredInheritedIsIndirectlyInherited()github
bca)

Test scope type for indirectly extended managed bean not annotated @Inherited is not inherited.

Coverage

org.jboss.cdi.tck.tests.definition.scope
ScopeDefinitionTest.testScopeTypeNotDeclaredInheritedIsNotIndirectlyInherited()github
be)

Test scope type for directly extended session bean annotated @Inherited is inherited.

Coverage

org.jboss.cdi.tck.tests.definition.scope.enterprise
EnterpriseScopeDefinitionTest.testScopeTypeDeclaredInheritedIsInherited()github
bea)

Test scope type for directly extended session bean not annotated @Inherited is not inherited.

Coverage

org.jboss.cdi.tck.tests.definition.scope.enterprise
EnterpriseScopeDefinitionTest.testScopeTypeNotDeclaredInheritedIsNotInherited()github
bh)

Test scope type for indirectly extended session bean annotated @Inherited is inherited.

Coverage

org.jboss.cdi.tck.tests.definition.scope.enterprise
EnterpriseScopeDefinitionTest.testScopeTypeDeclaredInheritedIsIndirectlyInherited()github
bha)

Test scope type for indirectly extended session bean not annotated @Inherited is not inherited.

Coverage

org.jboss.cdi.tck.tests.definition.scope.enterprise
EnterpriseScopeDefinitionTest.testScopeTypeNotDeclaredInheritedIsNotIndirectlyInherited()github
hhh)

For class X which is extended directly by the bean class of a managed bean Y, a scope type explicitly declared by X and inherited by Y from X takes precedence over default scopes of stereotypes declared or inherited by Y.

Coverage

org.jboss.cdi.tck.tests.definition.stereotype
StereotypeDefinitionTest.testStereotypeScopeIsOverriddenByInheritedScope()github
hhi)

For class X which is extended indirectly by the bean class of a managed bean Y, a scope type explicitly declared by X and inherited by Y from X takes precedence over default scopes of stereotypes declared or inherited by Y.

Coverage

org.jboss.cdi.tck.tests.definition.stereotype
StereotypeDefinitionTest.testStereotypeScopeIsOverriddenByIndirectlyInheritedScope()github
hhj)

For class X which is extended directly by the bean class of a session bean Y, a scope type explicitly declared by X and inherited by Y from X takes precedence over default scopes of stereotypes declared or inherited by Y.

Coverage

org.jboss.cdi.tck.tests.definition.stereotype.enterprise
EnterpriseStereotypeDefinitionTest.testStereotypeScopeIsOverriddenByInheritedScope()github
hhk)

For class X which is extended indirectly by the bean class of a session bean Y, a scope type explicitly declared by X and inherited by Y from X takes precedence over default scopes of stereotypes declared or inherited by Y.

Coverage

org.jboss.cdi.tck.tests.definition.stereotype.enterprise
EnterpriseStereotypeDefinitionTest.testStereotypeScopeIsOverriddenByIndirectlyInheritedScope()github
i)sigtest

For annotations defined by the bean specification, all built-in scope types are declared @Inherited

j)sigtest

For annotations defined by the bean specification, all built-in stereotypes are declared @Inherited

k)sigtest

For annotations defined by the bean specification, no built-in qualifier type is declared @Inherited

m)sigtest

The @Named annotation is not declared @Inherited and bean EL names are not inherited unless specialization is used

Section 4.2 - Inheritance of member-level metadata

Suppose a class X is extended directly or indirectly by the bean class of a managed bean or session bean Y. If X declares an injected field x then Y inherits x.

aa)

Check managed bean X directly extends managed bean Y

Coverage

org.jboss.cdi.tck.tests.lookup.injection
InjectionTest.testInjectionFieldsAndInitializerMethods()github
ac)

Check managed bean X indirectly extends managed bean Y

Coverage

org.jboss.cdi.tck.tests.lookup.injection
InjectionTest.testFieldDeclaredInIndirectSuperclassInjected()github
ab)

Check session bean X directly extends session bean Y

Coverage

org.jboss.cdi.tck.tests.lookup.injection.enterprise
SessionBeanInjectionTest.testFieldDeclaredInSuperclassInjected()github
ad)

Check session bean X indirectly extends session bean Y

Coverage

org.jboss.cdi.tck.tests.lookup.injection.enterprise
SessionBeanInjectionTest.testFieldDeclaredInSuperclassIndirectlyInjected()github

Suppose a class X is extended directly or indirectly by the bean class of a managed bean or session bean Y. If X declares an initializer, non-static observer, @PostConstruct or @PreDestroy method x() then Y inherits x() if and only if neither Y nor any intermediate class that is a subclass of X and a superclass of Y overrides the method x().

baa)

Check managed bean X directly extends managed bean Y with @PostConstruct

Coverage

org.jboss.cdi.tck.tests.implementation.simple.lifecycle
SimpleBeanLifecycleTest.testSubClassInheritsPostConstructOnSuperclass()github
SimpleBeanLifecycleTest.testSubClassDoesNotInheritPostConstructOnSuperclassBlockedByIntermediateClass()github
bab)

Check session bean X directly extends session bean Y with @PostConstruct

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.lifecycle
EnterpriseBeanLifecycleTest.testDirectSubClassInheritsPostConstructOnSuperclass()github
bac)

Check managed bean X indirectly extends managed bean Y with @PostConstruct

Coverage

org.jboss.cdi.tck.tests.implementation.simple.lifecycle
SimpleBeanLifecycleTest.testIndirectSubClassInheritsPostConstructOnSuperclass()github
bad)

Check session bean X indirectly extends session bean Y with @PostConstruct

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.lifecycle
EnterpriseBeanLifecycleTest.testIndirectSubClassInheritsPostConstructOnSuperclass()github
bba)

Check managed bean X directly extends managed bean Y with @PostDestroy

Coverage

org.jboss.cdi.tck.tests.implementation.simple.lifecycle
SimpleBeanLifecycleTest.testSubClassInheritsPreDestroyOnSuperclass()github
SimpleBeanLifecycleTest.testSubClassDoesNotInheritPreDestroyConstructOnSuperclassBlockedByIntermediateClass()github
bbb)

Check session bean X directly extends session bean Y with @PostDestroy

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.lifecycle
EnterpriseBeanLifecycleTest.testSubClassInheritsPreDestroyOnSuperclass()github
bbc)

Check managed bean X indirectly extends managed bean Y with @PostDestroy

Coverage

org.jboss.cdi.tck.tests.implementation.simple.lifecycle
SimpleBeanLifecycleTest.testIndirectSubClassInheritsPreDestroyOnSuperclass()github
bbd)

Check session bean X indirectly extends session bean Y with @PostDestroy

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.lifecycle
EnterpriseBeanLifecycleTest.testIndirectSubClassInheritsPreDestroyOnSuperclass()github
dc)

Check managed bean X directly extends managed bean Y with a non-static observer method

Coverage

org.jboss.cdi.tck.tests.event
EventTest.testNonStaticObserverMethodInherited()github
org.jboss.cdi.tck.tests.event.observer.inheritance
ObserverInheritanceTest.testNonStaticObserverMethodInherited()github
df)

Check session bean X directly extends session bean Y with a non-static observer method

Coverage

org.jboss.cdi.tck.tests.event.observer.inheritance.enterprise
EnterpriseObserverInheritanceTest.testNonStaticObserverMethodInherited()github
di)

Check managed bean X indirectly extends managed bean Y with a non-static observer method

Coverage

org.jboss.cdi.tck.tests.event.observer.inheritance
ObserverInheritanceTest.testNonStaticObserverMethodInherited()github
org.jboss.cdi.tck.tests.event
EventTest.testNonStaticObserverMethodIndirectlyInherited()github
dl)

Check session bean X indirectly extends session bean Y with a non-static observer method

Coverage

org.jboss.cdi.tck.tests.event.observer.inheritance.enterprise
EnterpriseObserverInheritanceTest.testNonStaticObserverMethodIndirectlyInherited()github
dm)

Check managed bean X directly extends managed bean Y with a initializer method

Coverage

org.jboss.cdi.tck.tests.inheritance.initializer
InitializerMethodInheritanceTest.testManagedBeanDirectlyInheritsInitializer()github
dn)

Check session bean X directly extends session bean Y with a initializer method

Coverage

org.jboss.cdi.tck.tests.inheritance.initializer
InitializerMethodInheritanceTest.testSessionBeanDirectlyInheritsInitializer()github
do)

Check managed bean X indirectly extends managed bean Y with a initializer method

Coverage

org.jboss.cdi.tck.tests.inheritance.initializer
InitializerMethodInheritanceTest.testManagedBeanIndirectlyInheritsInitializer()github
dp)

Check session bean X indirectly extends session bean Y with a initializer method

Coverage

org.jboss.cdi.tck.tests.inheritance.initializer
InitializerMethodInheritanceTest.testSessionBeanIndirectlyInheritsInitializer()github

Suppose a class X is extended directly or indirectly by the bean class of a managed bean or session bean Y. If X declares a non-static method x() annotated with an interceptor binding type Z then Y inherits the binding if and only if neither Y nor any intermediate class that is a subclass of X and a superclass of Y overrides the method x().

ka)

Check managed bean X directly extends managed bean Y

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.inheritance
InterceptorBindingInheritanceTest.testMethodInterceptorBindingDirectlyInheritedFromManagedBean()github
InterceptorBindingInheritanceTest.testMethodInterceptorBindingDirectlyNotInherited()github
kb)

Check session bean X directly extends session bean Y

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.inheritance
InterceptorBindingInheritanceTest.testMethodInterceptorBindingDirectlyInheritedFromSessionBean()github
kc)

Check managed bean X indirectly extends managed bean Y

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.inheritance
InterceptorBindingInheritanceTest.testMethodInterceptorBindingIndirectlyInheritedFromManagedBean()github
InterceptorBindingInheritanceTest.testMethodInterceptorBindingIndirectlyNotInherited()github
kd)

Check session bean X indirectly extends session bean Y

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.inheritance
InterceptorBindingInheritanceTest.testMethodInterceptorBindingIndirectlyInheritedFromSessionBean()github

Suppose a class X is extended directly or indirectly by the bean class of a managed bean or session bean Y .If X declares a non-static producer or disposer method x() then Y does not inherit this method.

da)

Check managed bean X directly extends managed bean Y with a non-static producer method

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testNonStaticProducerMethodNotInheritedBySpecializingSubclass()github
ProducerMethodDefinitionTest.testNonStaticProducerMethodNotInherited()github
db)

Check managed bean X directly extends managed bean Y with a non-static disposer method

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition.inheritance
DisposerMethodInheritanceTest.testManagedBeanDisposerMethodNotInherited()github
dd)

Check session bean X directly extends session bean Y with a non-static producer method

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition.enterprise
EnterpriseProducerMethodDefinitionTest.testNonStaticProducerMethodNotInheritedBySpecializingSubclass()github
EnterpriseProducerMethodDefinitionTest.testNonStaticProducerMethodNotInherited()github
de)

Check session bean X directly extends session bean Y with a non-static disposer method

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition.inheritance
DisposerMethodInheritanceTest.testSessionBeanDisposerMethodNotInherited()github
dg)

Check managed bean X indirectly extends managed bean Y with a non-static producer method

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testNonStaticProducerMethodNotInherited()github
dh)

Check managed bean X indirectly extends managed bean Y with a non-static disposer method

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition.inheritance
DisposerMethodInheritanceTest.testManagedBeanDisposerMethodNotInherited()github
dj)

Check session bean X indirectly extends session bean Y with a non-static producer method

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition.enterprise
EnterpriseProducerMethodDefinitionTest.testNonStaticProducerMethodNotIndirectlyInherited()github
dk)

Check session bean X indirectly extends session bean Y with a non-static disposer method

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition.inheritance
DisposerMethodInheritanceTest.testSessionBeanDisposerMethodNotInherited()github

Suppose a class X is extended directly or indirectly by the bean class of a managed bean or session bean Y. If X declares a non-static producer field x then Y does not inherit this field.

ea)We don't test session beans, as they can't have non-static producer fields

Check managed bean X directly extends managed bean Y

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition
ProducerFieldDefinitionTest.testNonStaticProducerFieldNotInherited()github
ec)We don't test session beans, as they can't have non-static producer fields

Check managed bean X indirectly extends managed bean Y

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.definition
ProducerFieldDefinitionTest.testNonStaticProducerFieldNotIndirectlyInherited()github

If X is a generic type, and an injection point or observer method declared by X is inherited by Y, and the declared type of the injection point, producer method, producer field, disposed para- meter or event parameter contains type variables declared by X, the type of the injection point, producer method, producer field, disposed parameter or event parameter inherited in Y is the declared type, after substitution of actual type arguments declared by Y or any intermediate class that is a subclass of X and a superclass of Y.

f)

Check injection point

Coverage

org.jboss.cdi.tck.tests.inheritance.generics
MemberLevelInheritanceTest.testInjectionPointDefinition()github
MemberLevelInheritanceTest.testInjectionPoint()github
g)

check observer method

Coverage

org.jboss.cdi.tck.tests.inheritance.generics
MemberLevelInheritanceTest.testObserverResolution()github
MemberLevelInheritanceTest.testObserver()github

Section 4.3 - Specialization

a)

If two beans both support a certain bean type, and share at least one qualifier, then they are both eligible for injection to any injection point with that declared type and qualifier.

When an enabled bean specializes a second bean, we can be certain that the second bean is never instantiated or called by the container. Even if the second bean defines a producer or observer method, the method will never be called.

ca)

The second bean is never instantiated.

Coverage

org.jboss.cdi.tck.tests.inheritance.specialization.enterprise
EnterpriseBeanSpecializationTest.testSpecializedBeanNotInstantiated()github
org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes.specialization
SpecializationTest.testProcessBeanAttributesFiredProperlyForSpecializedBean()github
VetoTest.testSpecializedBeanAvailableAfterSpecializingBeanVetoed()github
cb)

Producer method on specialized bean is not called.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.lifecycle
ProducerMethodLifecycleTest.testProducerMethodFromSpecializedBeanUsed()github
org.jboss.cdi.tck.tests.inheritance.specialization.simple
SimpleBeanSpecializationTest.testProducerMethodOnSpecializedBeanNotCalled()github
org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testNonStaticProducerMethodNotInheritedBySpecializingSubclass()github
cc)

Observer method on specialized bean is not called.

Coverage

org.jboss.cdi.tck.tests.event
EventTest.testObserverCalledOnSpecializedBeanOnly()github
cd)

Producer field on specialized bean is not used.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.lifecycle
ProducerFieldLifecycleTest.testProducerFieldFromSpecializingBeanUsed()github

Section 4.3.1 - Direct and indirect specialization

ia)

A bean X is said to specialize another bean Y if X directly specializes Y.

Coverage

org.jboss.cdi.tck.tests.lookup.modules.specialization
SpecializationModularity01Test.testSpecialization()github
org.jboss.cdi.tck.tests.inheritance.specialization.simple
SimpleBeanSpecializationTest.testIndirectSpecialization()github
SimpleBeanSpecializationTest.testSpecializingBeanInjection()github
org.jboss.cdi.tck.tests.inheritance.specialization.producer.method.enterprise
EnterpriseProducerMethodSpecializationTest.testSpecializingProducerMethod()github
EnterpriseProducerMethodSpecializationTest.testSpecializingBeanInjection()github
org.jboss.cdi.tck.tests.inheritance.specialization.producer.method
ProducerMethodSpecializationTest.testSpecializingProducerMethod()github
ProducerMethodSpecializationTest.testSpecializingBeanInjection()github
org.jboss.cdi.tck.tests.inheritance.specialization.enterprise
EnterpriseBeanSpecializationTest.testDirectSpecialization()github
org.jboss.cdi.tck.tests.lookup.modules.specialization
SpecializationModularity02Test.testSpecialization()github
SpecializationModularity04Test.testSpecialization()github
ib)

A bean X is said to specialize another bean Y if a bean Z exists, such that X directly specializes Z and Z specializes Y.

Coverage

org.jboss.cdi.tck.tests.inheritance.specialization.simple
SimpleBeanSpecializationTest.testIndirectSpecialization()github
j)

A bean X that specializes bean Y will include all qualifiers of Y, together with all qualifiers declared explicitly by X.

Coverage

org.jboss.cdi.tck.tests.inheritance.specialization.simple
SimpleBeanSpecializationTest.testSpecializingBeanHasQualifiersOfSpecializedAndSpecializingBean()github
org.jboss.cdi.tck.tests.inheritance.specialization.producer.method
ProducerMethodSpecializationTest.testSpecializingProducerMethod()github
org.jboss.cdi.tck.tests.inheritance.specialization.enterprise
EnterpriseBeanSpecializationTest.testSpecializingBeanHasBindingsOfSpecializedAndSpecializingBean()github
k)

A bean X that specializes bean Y will have the same name as Y if Y has a name.

Coverage

org.jboss.cdi.tck.tests.inheritance.specialization.simple
SimpleBeanSpecializationTest.testSpecializingBeanHasNameOfSpecializedBean()github
org.jboss.cdi.tck.tests.inheritance.specialization.producer.method
ProducerMethodSpecializationTest.testSpecializingProducerMethod()github
org.jboss.cdi.tck.tests.inheritance.specialization.enterprise
EnterpriseBeanSpecializationTest.testSpecializingBeanHasNameOfSpecializedBean()github
l)

X must have all the bean types of Y. If X does not have some bean type of Y, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.inheritance.specialization.simple.broken.types
SpecializingBeanWithoutBeanTypeOfSpecializedBeanTest.testDeployment()github
org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes.specialization.broken
TypeConflictDetectionTest.testDeployment()github

If Y has a bean name and X declares a bean name explicitly the container automatically detects the problem and treats it as a definition error.

la)

Test that a specializing producer method with a name throws a definition exception.

Coverage

org.jboss.cdi.tck.tests.inheritance.specialization.producer.method.broken.specializingAndSpecializedBeanHaveName
SpecializingAndSpecializedBeanHaveNameTest.testSpecializingAndSpecializedBeanHasName()github
lb)

Test that a specializing managed bean with a name throws a definition exception.

Coverage

org.jboss.cdi.tck.tests.inheritance.specialization.simple.broken.names
SpecializingAndSpecializedBeanHasNameTest.testSpecializingAndSpecializedBeanHasName()github
lc)

Test that a specializing enterprise bean with a name throws a definition exception.

Coverage

org.jboss.cdi.tck.tests.inheritance.specialization.enterprise.broken.sameName
SameNameTest.testSpecializingAndSpecializedBeanHasName()github
n)Defines non-portable behavior

If an interceptor or decorator is annotated @Specializes, non-portable behavior results.

Section 5 - Dependency injection, lookup, and EL

b)The RI has unit tests for this atm

The container is required to support circularities in the bean dependency graph where at least one bean participating in every circular chain of dependencies has a normal scope, as defined in Section 6.3, "Normal scopes and pseudo-scopes".

Coverage

org.jboss.cdi.tck.tests.lookup.circular
CircularDependencyTest.testCircularInjectionOnTwoNormalBeans()github
CircularDependencyTest.testCircularInjectionOnOneNormalAndOneDependentBean()github
CircularDependencyTest.testNormalProducerMethodDeclaredOnNormalBeanWhichInjectsProducedBean()github
CircularDependencyTest.testNormalProducerMethodDeclaredOnDependentBeanWhichInjectsProducedBean()github
CircularDependencyTest.testDependentProducerMethodDeclaredOnNormalBeanWhichInjectsProducedBean()github
CircularDependencyTest.testNormalCircularConstructors()github
CircularDependencyTest.testNormalAndDependentCircularConstructors()github
CircularDependencyTest.testSelfConsumingConstructorsOnNormalBean()github
org.jboss.cdi.tck.tests.lookup.injection.enterprise.chain
SessionBeanInjectionChainTest.testChainOfSessionBeans()github
c)

The container is not required to support circular chains of dependencies where every bean participating in the chain has a pseudo-scope.

Section 5.1 - Modularity

Beans packaged in a certain Java EE module or library are available for injection, lookup and EL resolution to classes and JSP/JSF pages packaged in some other Java EE module or library if and only if the first module or library is required to be accessible to the other module or library by the Java EE platform specification.

aa)

Test with injection.

Coverage

org.jboss.cdi.tck.tests.lookup.modules
EnabledSessionBeanInjectionAvailabilityTest.testInjection()github
org.jboss.cdi.tck.tests.lookup.modules.specialization
SpecializationModularity01Test.testSpecialization()github
SpecializationModularity08Test.testSpecialization()github
org.jboss.cdi.tck.tests.lookup.modules
EnabledManagedBeanInjectionAvailabilityTest.testInjection()github
org.jboss.cdi.tck.tests.lookup.modules.specialization
SpecializationModularity06Test.testSpecialization()github
SpecializationModularity03Test.testSpecialization()github
SpecializationModularity05Test.testSpecialization()github
SpecializationModularity02Test.testSpecialization()github
SpecializationModularity04Test.testSpecialization()github
ab)

Test with lookup.

Coverage

org.jboss.cdi.tck.tests.lookup.modules
InterModuleLookupTest.testEnabledManagedBeanAvailableForInjection()github
ac)

Test with EL resolution.

Coverage

org.jboss.cdi.tck.tests.lookup.modules
InterModuleELResolutionTest.testEnabledManagedBeanAvailableForELResolution()github
d)If a module/library is not BDA then no injection is possible at all

An alternative is never available for injection, lookup or EL resolution in a Java EE module or library that is not a bean deployment archive (a module or library with no beans.xml file.

e)

Nor is an alternative available for injection, lookup or EL resolution in every bean deployment archive. An alternative must be explicitly selected in every bean deployment archive in which the alternative should be available for injection, lookup and EL resolution.

Coverage

org.jboss.cdi.tck.tests.alternative
AlternativeAvailabilityTest.testAlternativeAvailability()github

Section 5.1.1 - Declaring selected alternatives for a bean deployment archive

aa)This is a statement of intent

Alternatives may be selected for an application, or selected only for a particular bean archive.

The following assertion is not made explicitly by the spec, however it is implied ab)

By default, a bean archive has no selected alternatives.

Coverage

org.jboss.cdi.tck.tests.alternative
AlternativeAvailabilityTest.testAlternativeAvailability()github

An alternative may be selected for an application using the <alternatives> element of the beans.xml file of the bean archive that declares the alternative. The <alternatives> element contains a list of bean classes and stereotypes, along with a priority attribute.

ba)

An alternative is selected for the entire application if the alternative is a managed bean or session bean and the bean class of the bean is listed, along with a priority attribute.

Coverage

org.jboss.cdi.tck.tests.alternative.selection
SelectedAlternative01Test.testAlternativeManagedBeanSelected()github
bb)

An alternative is selected for the entire application if the alternative is a managed bean or session bean and the bean class of the bean is listed, along with a priority attribute.

Coverage

No tests exist for this assertion

bc)

An alternative is selected for the entire application if the alternative is a producer method, field or resource, and the bean class that declares the method or field is listed, along with a priority attribute.

Coverage

org.jboss.cdi.tck.tests.alternative.selection
SelectedAlternative01Test.testAlternativeProducerSelected()github
bd)

An alternative is selected for the entire application if the alternative is a producer method, field or resource, and the bean class that declares the method or field is listed, along with a priority attribute.

Coverage

org.jboss.cdi.tck.tests.alternative.selection
SelectedAlternative01Test.testAlternativeProducerSelected()github
be)

An alternative is selected for the entire application if the alternative is a producer method, field or resource, and the bean class that declares the method or field is listed, along with a priority attribute.

Coverage

org.jboss.cdi.tck.tests.alternative.selection.resource
ResourceAlternative02Test.testAlternativeResourceDeselected()github
ResourceAlternative01Test.testAlternativeResourceSelected()github
bf)

An alternative is selected for the entire application if any @Alternative stereotype of the alternative is listed, along with a priority attribute.

Coverage

org.jboss.cdi.tck.tests.alternative.selection
SelectedAlternative01Test.testAlternativeStereotypeSelected()github

An alternative may be selected for a bean archive using the <alternatives> element of the beans.xml file of the bean archive. The <alternatives> element contains a list of bean classes and stereotypes, along with a priority attribute.

ca)

An alternative is selected for the bean archive if the alternative is a managed bean or session bean and the bean class of the bean is listed.

Coverage

org.jboss.cdi.tck.tests.alternative.resolution.qualifier
QualifierNotInheritedTest.testResolution()github
QualifierNotDeclaredTest.testResolution()github
org.jboss.cdi.tck.tests.alternative
AlternativeAvailabilityTest.testAlternativeAvailability()github
org.jboss.cdi.tck.tests.alternative.resolution.qualifier
QualifierInheritedTest.testResolution()github
cb)

An alternative is selected for the bean archive if the alternative is a managed bean or session bean and the bean class of the bean is listed.

Coverage

org.jboss.cdi.tck.tests.alternative.enterprise
SessionBeanAlternativeTest.testEnabledPolicyAvailable()github
cc)

An alternative is selected for the bean archive if the alternative is a producer method, field or resource, and the bean class that declares the method or field is listed.

Coverage

org.jboss.cdi.tck.tests.alternative
AlternativeAvailabilityTest.testProducersOnAlternativeClass()github
cd)

An alternative is selected for the bean archive if the alternative is a producer method, field or resource, and the bean class that declares the method or field is listed.

Coverage

org.jboss.cdi.tck.tests.alternative
AlternativeAvailabilityTest.testProducersOnAlternativeClass()github
ce)

An alternative is selected for the bean archive if the alternative is a producer method, field or resource, and the bean class that declares the method or field is listed.

Coverage

org.jboss.cdi.tck.tests.alternative.enterprise.resource
ResourceAlternativeAvailabilityTest.testResourceAvailability()github
cf)

An alternative is selected for the bean archive if any @Alternative stereotype of the alternative is listed.

Coverage

org.jboss.cdi.tck.tests.alternative
AlternativeAvailabilityTest.testAnyEnabledAlternativeStereotypeMakesAlternativeEnabled()github
The following assertion is not made explicitly by the spec, however it is implied cg)

An alternative selected only for a specific bean archive is not selected for an application.

Coverage

org.jboss.cdi.tck.tests.deployment.packaging.war.modules
WebArchiveModulesTest.testAlternatives()github

An alternative selected for an application may be deselected for a bean archive using the <alternatives> element of the beans.xml file of the bean archive. The <alternatives> element contains a list of bean classes and stereotypes, along with a disabled flag.

da)

An alternative is not selected for the bean archive if the alternative is a managed bean or session bean and the bean class of the bean is listed, along with a disabled flag.

Coverage

org.jboss.cdi.tck.tests.alternative.selection
SelectedAlternative04Test.testAlternativeManagedBeanDeselected()github
db)

An alternative is not selected for the bean archive if the alternative is a managed bean or session bean and the bean class of the bean is listed, along with a disabled flag.

Coverage

No tests exist for this assertion

dc)

An alternative is not selected for the bean archive if the alternative is a producer method, field or resource, and the bean class that declares the method or field is listed, along with a disabled flag.

Coverage

org.jboss.cdi.tck.tests.alternative.selection
SelectedAlternative04Test.testAlternativeProducerDeselected()github
dd)

An alternative is not selected for the bean archive if the alternative is a producer method, field or resource, and the bean class that declares the method or field is listed, along with a disabled flag.

Coverage

org.jboss.cdi.tck.tests.alternative.selection
SelectedAlternative04Test.testAlternativeProducerDeselected()github
de)

An alternative is not selected for the bean archive if the alternative is a producer method, field or resource, and the bean class that declares the method or field is listed, along with a disabled flag.

Coverage

org.jboss.cdi.tck.tests.alternative.selection.resource
ResourceAlternative02Test.testAlternativeResourceDeselected()github
df)

An alternative is not selected for the bean archive if any @Alternative stereotype of the alternative is listed, along with a disabled flag.

Coverage

org.jboss.cdi.tck.tests.alternative.selection
SelectedAlternative04Test.testAlternativeStereotypeDeselected()github

An alternative may be given a default priority, but not selected for an application using the <alternatives> element of the beans.xml file of the bean archive. The <alternatives> element contains a list of bean classes and stereotypes, along with a disabled flag and a priority attribute.

ea)

An alternative is is not selected for an application if the alternative is a managed bean or session bean and the bean class of the bean is listed, along with a disabled flag and a priority attribute.

Coverage

org.jboss.cdi.tck.tests.alternative.selection
SelectedAlternative05Test.testManagedBeanWithDefaultPrioritySelected()github
eb)

An alternative is is not selected for an application if the alternative is a managed bean or session bean and the bean class of the bean is listed, along with a disabled flag and a priority attribute.

Coverage

No tests exist for this assertion

ec)

An alternative is is not selected for an application if the alternative is a producer method, field or resource, and the bean class that declares the method or field is listed, along with a disabled flag and a priority attribute.

Coverage

org.jboss.cdi.tck.tests.alternative.selection
SelectedAlternative05Test.testAlternativeProducerSelected()github
ed)

An alternative is is not selected for an application if the alternative is a producer method, field or resource, and the bean class that declares the method or field is listed, along with a disabled flag and a priority attribute.

Coverage

org.jboss.cdi.tck.tests.alternative.selection
SelectedAlternative05Test.testAlternativeProducerSelected()github
ee)

An alternative is is not selected for an application if the alternative is a producer method, field or resource, and the bean class that declares the method or field is listed, along with a disabled flag and a priority attribute.

Coverage

org.jboss.cdi.tck.tests.alternative.selection.resource
ResourceAlternative03Test.testAlternativeResourceDeselected()github
ef)

An alternative is is not selected for an application if any @Alternative stereotype of the alternative is listed, along with a disabled flag and a priority attribute.

Coverage

org.jboss.cdi.tck.tests.alternative.selection
SelectedAlternative05Test.testAlternativeStereotypeSelected()github

An alternative with a default priority may be selected for a bean archive using the <alternatives> element of the beans.xml file of the bean archive. The <alternatives> element contains a list of bean classes and stereotypes, along with an enabled flag.

fa)

An alternative is selected for the bean archive if the alternative is a managed bean or session bean and the bean class of the bean is listed, along with an enabled flag.

Coverage

org.jboss.cdi.tck.tests.alternative.selection
SelectedAlternative05Test.testManagedBeanWithDefaultPrioritySelected()github
fb)

An alternative is selected for the bean archive if the alternative is a managed bean or session bean and the bean class of the bean is listed, along with an enabled flag.

Coverage

No tests exist for this assertion

fc)

An alternative is selected for the bean archive if the alternative is a producer method, field or resource, and the bean class that declares the method or field is listed, along with an enabled flag.

Coverage

org.jboss.cdi.tck.tests.alternative.selection
SelectedAlternative05Test.testAlternativeProducerSelected()github
fd)

An alternative is selected for the bean archive if the alternative is a producer method, field or resource, and the bean class that declares the method or field is listed, along with an enabled flag.

Coverage

org.jboss.cdi.tck.tests.alternative.selection
SelectedAlternative05Test.testAlternativeProducerSelected()github
fe)

An alternative is selected for the bean archive if the alternative is a producer method, field or resource, and the bean class that declares the method or field is listed, along with an enabled flag.

Coverage

org.jboss.cdi.tck.tests.alternative.selection.resource
ResourceAlternative03Test.testAlternativeResourceDeselected()github
ff)

An alternative is selected for the bean archive if any @Alternative stereotype of the alternative is listed, along with an enabled flag.

Coverage

org.jboss.cdi.tck.tests.alternative.selection
SelectedAlternative05Test.testAlternativeStereotypeSelected()github
h)

Each child <class> element must specify the name of a bean class of an alternative bean. If there is no class with the specified name, or if the class with the specified name is not an alternative bean class, the container automatically detects the problem and treats it as a deployment problem.

Coverage

org.jboss.cdi.tck.tests.alternative.broken.not.alternative
ClassIsNotAlternativeTest.test()github
org.jboss.cdi.tck.tests.alternative.broken.incorrect.name
NoClassWithSpecifiedNameTest.test()github
i)

Each child <stereotype> element must specify the name of a @Alternative stereotype annotation. If there is no annotation with the specified name, or the annotation is not a @Alternative stereotype, the container automatically detects the problem and treats it as a deployment problem.

Coverage

org.jboss.cdi.tck.tests.alternative.broken.incorrect.name.stereotype
NoAnnotationWithSpecifiedNameTest.test()github
org.jboss.cdi.tck.tests.alternative.broken.not.alternative.stereotype
ClassIsNotAlternativeTest.test()github
j)

If the same type is listed twice under the <alternatives> element, the container automatically detects the problem and treats it as a deployment problem.

Coverage

org.jboss.cdi.tck.tests.alternative.broken.same.type.twice
SameTypeListedTwiceTest.test()github
k)

For a custom implementation of the Bean interface defined in Section 11.1, "The Bean interface", the container calls isAlternative() to determine whether the bean is an alternative, and getBeanClass() and getStereotypes() to determine whether an alternative is selected in a certain bean deployment archive.

Coverage

org.jboss.cdi.tck.tests.definition.bean.custom
CustomBeanImplementationTest.testGetStereotypesCalled()github
CustomBeanImplementationTest.testIsPolicyCalled()github
CustomBeanImplementationTest.testGetBeanClassCalled()github

Section 5.1.2 - Enabled and disabled beans

a)Tested in 5.1.4

A bean is said to be enabled if it is deployed in a bean deployment archive, and it is not a producer method or field of a disabled bean, and it is not specialized by any other enabled bean, as defined in Section 4.3, "Specialization", and either it is not an alternative, or it is a selected alternative of at least one bean deployment archive. Otherwise, the bean is said to be disabled.

Section 5.1.3 - Inconsistent specialization

a)

Suppose an enabled bean X specializes a second bean Y. If there is another enabled bean that specializes Y we say that inconsistent specialization exists. The container automatically detects inconsistent specialization and treats it as a deployment problem.

Coverage

org.jboss.cdi.tck.tests.inheritance.specialization.simple.broken.inconsistent
InconsistentSpecializationTest.testInconsistentSpecialization()github
org.jboss.cdi.tck.tests.inheritance.specialization.producer.method.broken.twoBeansSpecializeTheSameBean
TwoBeansSpecializeTheSameBeanTest.testTwoBeansSpecializeTheSameBean()github
org.jboss.cdi.tck.tests.inheritance.specialization.enterprise.broken.twoBeansSpecializeTheSameBean
TwoBeansSpecializeTheSameBeanTest.testTwoBeansSpecializeTheSameBean()github
org.jboss.cdi.tck.tests.lookup.modules.specialization
SpecializationModularity07Test.testSpecialization()github

Section 5.1.4 - Inter-module injection

A bean is available for injection in a certain module if the bean is not an interceptor or decorator, the bean is enabled, the bean is either not an alternative, or the module is a bean archive and the bean is a selected alternative of the bean archive, and the bean class is required to be accessible to classes in the module, according to the class accessibility requirements of the module architecture.

a)

Check a decorator can not be injected

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution.decorator
DecoratorNotInjectedTest.testDecoratorNotResolved()github
b)

Check an interceptor can not be injected

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution.interceptor
InterceptorNotResolvedInterModuleTest.testInterceptorNotAvailableForInjection()github
InterceptorNotResolvedTest.testInterceptorNotAvailableForInjection()github
c)

Check an enabled managed bean can be injected

Coverage

org.jboss.cdi.tck.tests.lookup.modules
EnabledManagedBeanInjectionAvailabilityTest.testInjection()github
d)

Check an enabled session bean can be injected

Coverage

org.jboss.cdi.tck.tests.lookup.modules
EnabledSessionBeanInjectionAvailabilityTest.testInjection()github
e)

Check an enabled producer field can be injected

Coverage

org.jboss.cdi.tck.tests.lookup.modules
EnabledProducerFieldInjectionAvailabilityTest.testInjection()github
f)

Check an enabled producer method can be injected

Coverage

org.jboss.cdi.tck.tests.lookup.modules
EnabledProducerMethodInjectionAvailabilityTest.testInjection()github
g)

Check producer method of a disabled bean is not injectable

Coverage

org.jboss.cdi.tck.tests.lookup.modules.broken
DisabledProducerMethodInjectionNotAvailableTest.testInjection()github
h)

Check producer field of a disabled bean is not injectable

Coverage

org.jboss.cdi.tck.tests.lookup.modules.broken
DisabledProducerFieldInjectionNotAvailableTest.testInjection()github
i)

Check a disabled managed bean is not injectable

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution.broken.disabled
DisabledBeanNotAvailableForInjectionTest.testDeployment()github
j)

Check a disabled session bean is not injectable

Coverage

org.jboss.cdi.tck.tests.lookup.modules.broken
DisabledSessionBeanInjectionNotAvailableTest.testInjection()github
k)

Check a specialized session bean is not injectable

Coverage

org.jboss.cdi.tck.tests.lookup.modules
SpecializedBeanInjectionNotAvailableTest.testSessionBeanInjection()github
l)

Check a specialized managed bean is not injectable

Coverage

org.jboss.cdi.tck.tests.lookup.modules
SpecializedBeanInjectionNotAvailableTest.testManagedBeanInjection()github
org.jboss.cdi.tck.tests.lookup.modules.specialization
SpecializationModularity08Test.testSpecialization()github
SpecializationModularity06Test.testSpecialization()github
SpecializationModularity03Test.testSpecialization()github
SpecializationModularity05Test.testSpecialization()github
m)Specialized producer method is not legal.

Check a specialized producer field is not injectable

n)

Check a specialized producer method is not injectable

Coverage

org.jboss.cdi.tck.tests.lookup.modules
SpecializedProducerMethodInjectionNotAvailableTest.testManagedBeanInjection()github
o)

Check a selected alternative is injected for a managed bean

Coverage

org.jboss.cdi.tck.tests.lookup.modules
SelectedAlternativeManagedBeanInjectionAvailabilityTest.testInjection()github
p)

Check a selected alternative is injected for a session bean

Coverage

org.jboss.cdi.tck.tests.lookup.modules
SelectedAlternativeSessionBeanInjectionAvailabilityTest.testInjection()github

For a custom implementation of the Bean interface defined in Section 11.1, "The Bean interface, the container calls getBeanClass() to determine the bean class of the bean and InjectionPoint.getMember() and then Member.getDeclaringClass() to determine the class that declares an injection point.

q)

Check Bean.getBeanClass() is used to determine the bean class

Coverage

org.jboss.cdi.tck.tests.definition.bean.custom
CustomBeanImplementationTest.testGetBeanClassCalled()github
r)

Check InjectionPoint.getMember().getDeclaringClass() is used to determine the class declaring the injection point

Coverage

No tests exist for this assertion

Section 5.2.1 - Performing typesafe resolution

A bean is assignable to a given injection point if the bean has a bean type that matches the required type. For this purpose, primitive types are considered to match their corresponding wrapper types in java.lang and array types are considered to match only if their element types are identical. Parameterized and raw types are considered to match if they are identical or if the bean type is assignable to the required type, as defined in Section 5.2.3, "Assignability of raw and parameterized types".

i)

Test with a primitive type.

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution
ResolutionByTypeTest.testResolveByTypeWithPrimitives()github
j)

Test with an array type.

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution
ResolutionByTypeTest.testResolveByTypeWithArray()github
ka)

Test with a parameterized type.

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution
ResolutionByTypeTest.testResolveByTypeWithTypeParameter()github
kb)

Test with a raw type.

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution.parameterized
AssignabilityOfRawAndParameterizedTypesTest.testAssignabilityToRawType()github
kc)

Test with a @Named bean.

Coverage

org.jboss.cdi.tck.tests.lookup.injection
InjectionTest.testInjectionOfNamedBean()github

A bean is assignable to a given injection point if the bean has all the required qualifiers. If no required qualifiers were explicitly specified, the container assumes the required qualifier @Default. A bean has the required qualifier if it has a qualifier with (a) the same type and (b) the same annotation member value for each member which is not annotated @javax.enterprise.util.NonBinding.

la)

Test with beans with required qualifiers.

Coverage

org.jboss.cdi.tck.tests.alternative.resolution.qualifier
QualifierInheritedTest.testResolution()github
org.jboss.cdi.tck.tests.lookup.typesafe.resolution
ResolutionByTypeTest.testAllQualifiersSpecifiedForResolutionMustAppearOnBean()github
lb)

Test with beans without required qualifiers.

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution
ResolutionByTypeTest.testDefaultBindingTypeAssumed()github
org.jboss.cdi.tck.tests.alternative.resolution.qualifier
QualifierNotInheritedTest.testResolution()github
QualifierNotDeclaredTest.testResolution()github
lc)

Test with matching beans with matching qualifier with same type.

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution
ResolutionByTypeTest.testAllQualifiersSpecifiedForResolutionMustAppearOnBean()github
ld)

Test with matching beans with matching qualifier with same annotation member value for each member which is not annotated @javax.enterprise.util.NonBinding.

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution
ResolutionByTypeTest.testResolveByTypeWithNonBindingMembers()github
n)

A bean is eligible for injection to a certain injection point if it is available for injection in the module that contains the class that declares the injection point, and it is assignable to the injection point.

Coverage

org.jboss.cdi.tck.tests.deployment.packaging.war.modules
WebArchiveModulesTest.testInjectionChainVisibilityAndInterceptorEnablement()github
org.jboss.cdi.tck.tests.deployment.packaging.visibility
JarToJarAlphaVisibilityTest.testDeployment()github
JarToJarReverseAlphaVisibilityTest.testDeployment()github

For a custom implementation of the Bean interface defined in Section 11.1, "The Bean interface", the container calls getTypes() and getQualifiers() to determine the bean types and qualifiers.

na)

Test getTypes() determines bean types.

Coverage

org.jboss.cdi.tck.tests.definition.bean.custom
CustomBeanImplementationTest.testGetTypesCalled()github
nb)

Test getQualifiers() determines qualifiers.

Coverage

org.jboss.cdi.tck.tests.definition.bean.custom
CustomBeanImplementationTest.testGetBindingsCalled()github

Section 5.2.2 - Unsatisfied and ambiguous dependencies

When an ambiguous dependency exists, the container attempts to resolve the ambiguity. The container eliminates all eligible beans that are not alternatives, except for producer methods and fields of beans that are alternatives. If there is exactly one bean remaining, the container will select this bean, and the ambiguous dependency is called resolvable. If all the beans left are alternatives with a priority, then the container will select the alternative with the highest priority, and the ambiguous dependency is called resolvable.

ca)

Test that the container eliminates all eligible beans that are not alternatives, except for producer methods and fields of beans that are alternatives.

Coverage

org.jboss.cdi.tck.tests.alternative.selection.resource
ResourceAlternative05Test.testAlternativeResourceSelected()github
org.jboss.cdi.tck.tests.alternative.selection
SelectedAlternative02Test.testDependencyResolvable()github
org.jboss.cdi.tck.tests.alternative.selection.resource
ResourceAlternative04Test.testAlternativeResourceSelected()github
org.jboss.cdi.tck.tests.alternative.selection
SelectedAlternative03Test.testDependencyResolvable()github
cb)

Test that the container eliminates all eligible beans that are not alternatives, except for producer methods and fields of beans that are alternatives.

Coverage

org.jboss.cdi.tck.tests.lookup.dependency.resolution
AmbiguousDependencyResolutionTest.testProducerMethodOnAlternativeIsNotEliminated()github
AmbiguousDependencyResolutionTest.testProducerFieldOnAlternativeIsNotEliminated()github
cc)

Test that the container will select the alternative with the highest priority.

Coverage

org.jboss.cdi.tck.tests.alternative.selection.resource
ResourceAlternative05Test.testAlternativeResourceSelected()github
org.jboss.cdi.tck.tests.alternative.selection
SelectedAlternative02Test.testDependencyResolvable()github
org.jboss.cdi.tck.tests.alternative.selection.resource
ResourceAlternative04Test.testAlternativeResourceSelected()github
org.jboss.cdi.tck.tests.alternative.selection
SelectedAlternative03Test.testDependencyResolvable()github

The container must validate all injection points of all enabled beans, all enums, all observer methods, all disposer methods and all other Java EE component classes supporting injection when the application is initialized to ensure that there are no unsatisfied or ambiguous dependencies. If an unsatisfied or ambiguous dependency exists, the container automatically detects the problem and treats it as a deployment problem.

aa)

Test unsatisfied dependency for enabled bean.

Coverage

org.jboss.cdi.tck.tests.lookup.dependency.resolution.broken.unsatisfied
UnsatisfiedDependencyTest.testUnsatisfiedDependency()github
org.jboss.cdi.tck.tests.lookup.injection.enums.broken
EnumValidationTest.testDeployment()github
ab)

Test unsatisfied dependency for observer method.

Coverage

org.jboss.cdi.tck.tests.event.observer.broken.validation.unsatisfied
ObserverMethodParameterInjectionValidationTest.test()github
ac)

Test unsatisfied dependency for disposer method.

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition.broken.validation.unsatisfied
DisposerMethodParameterInjectionValidationTest.test()github
ad)

Test unsatisfied dependency for Java EE component.

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual.broken.unsatisfied
UnsatisfiedInjectionIntoNonContextualComponentTest.testInjectionIntoServlet()github
ae)

Test ambiguous dependency for enabled bean.

Coverage

org.jboss.cdi.tck.tests.lookup.dependency.resolution.broken.ambiguous
AmbiguousDependencyTest.testAmbiguousDependency()github
af)

Test ambiguous dependency for observer method.

Coverage

org.jboss.cdi.tck.tests.event.observer.broken.validation.ambiguous
ObserverMethodParameterInjectionValidationTest.test()github
ag)

Test ambiguous dependency for disposer method.

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition.broken.validation.ambiguous
DisposerMethodParameterInjectionValidationTest.test()github
ah)

Test ambiguous dependency for Java EE component.

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual.broken.ambiguous
AmbiguousInjectionIntoNonContextualComponentTest.testInjectionIntoServlet()github
b)

For a custom implementation of the Bean interface defined in Section 11.1, "The Bean interface", the container calls getInjectionPoints() to determine the set of injection points.

Coverage

org.jboss.cdi.tck.tests.definition.bean.custom
CustomBeanImplementationTest.testGetInjectionPointsCalled()github

Section 5.2.3 - Legal injection point types

a)

Any legal bean type, as defined in Section 2.2.1, "Legal bean types" may be the required type of an injection point.

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint.requiredtype
LegalRequiredTypeTest.testLegalRequiredType()github
b)

The required type of an injection point may contain a wildcard type parameter. However, a type variable is not a legal injection point type.

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution.parameterized
AssignabilityOfRawAndParameterizedTypesTest.testAssignabilityOfParameterizedTypeWithActualTypesToParameterizedTypeWithWildcardsAtInjectionPoint()github
c)

If an injection point type is a type variable, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution.broken.type.variable
TypeVariableInjectionPointTest.testTypeVariableInjectionPoint()github

Section 5.2.4 - Assignability of raw and parameterized types

a)

A parameterized bean type is considered assignable to a raw required type if the raw types are identical and all type parameters of the bean type are either unbounded type variables or java.lang.Object.

Coverage

org.jboss.cdi.tck.tests.lookup.injection.parameterized
ParameterizedTypesInjectionToRawTypeTest.testInjection()github
org.jboss.cdi.tck.tests.lookup.injection.parameterized.broken.raw
ParameterizedTypesInjectionRawAmbiguousTest.testInjection()github
org.jboss.cdi.tck.tests.lookup.typesafe.resolution.parameterized
AssignabilityOfRawAndParameterizedTypesTest.testAssignabilityToRawType()github
org.jboss.cdi.tck.tests.lookup.injection.parameterized
ParameterizedTypesInjectionToParameterizedWithActualTypeTest.testInjection()github

A parameterized bean type is considered assignable to a parameterized required type if they have identical raw type and for each parameter: the required type parameter and the bean type parameter are actual types with identical raw type, and, if the type is parameterized, the bean type parameter is assignable to the required type parameter according to these rules, or the required type parameter is a wildcard, the bean type parameter is an actual type and the actual type is assignable to the upper bound, if any, of the wildcard and assignable from the lower bound, if any, of the wildcard, or the required type parameter is a wildcard, the bean type parameter is a type variable and the upper bound of the type variable is assignable to or assignable from the upper bound, if any, of the wildcard and assignable from the lower bound, if any, of the wildcard, or the required type parameter is an actual type, the bean type parameter is a type variable and the actual type is as- signable to the upper bound, if any, of the type variable, or the required type parameter and the bean type parameter are both type variables and the upper bound of the required type parameter is assignable to the upper bound, if any, of the bean type parameter.

ba)

Check the required type parameter and the bean type parameter are actual types with identical raw type

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution.parameterized
AssignabilityOfRawAndParameterizedTypesTest.testAssignabilityOfParameterizedTypeWithActualTypesToParameterizedTypeWithActualTypes()github
org.jboss.cdi.tck.tests.lookup.injection.parameterized
ParameterizedTypesInjectionToParameterizedWithActualTypeTest.testInjection()github
bb)

Check the required type parameter and the bean type parameter are actual types with identical raw type for nested type parameters

Coverage

org.jboss.cdi.tck.tests.lookup.injection.parameterized
ParameterizedTypesInjectionToParameterizedWithActualTypeTest.testInjection()github
c)

Check the required type parameter is a wildcard, the bean type parameter is an actual type and the actual type is assignable to the upper bound of the wildcard and assignable from the lower bound of the wildcard

Coverage

org.jboss.cdi.tck.tests.lookup.injection.parameterized
ParameterizedTypesInjectionToParameterizedWithWildcardTest.testInjection()github
org.jboss.cdi.tck.tests.lookup.typesafe.resolution.parameterized
AssignabilityOfRawAndParameterizedTypesTest.testAssignabilityOfParameterizedTypeWithActualTypesToParameterizedTypeWithWildcards()github
da)

Check the required type parameter is a wildcard, the bean type parameter is a type variable and the upper bound of the type variable is assignable to the upper bound of the wildcard and assignable from the lower bound of the wildcard

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution.parameterized
AssignabilityOfRawAndParameterizedTypesTest.testAssignabilityOfParameterizedTypeWithTypeVariablesToParameterizedTypeWithWildcards()github
org.jboss.cdi.tck.tests.lookup.injection.parameterized
ParameterizedTypesInjectionToParameterizedWithWildcardTest.testInjection()github
db)

Check the required type parameter is a wildcard, the bean type parameter is a type variable and the upper bound of the type variable is assignable from the upper bound of the wildcard and assignable from the lower bound of the wildcard

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution.parameterized
AssignabilityOfRawAndParameterizedTypesTest.testAssignabilityOfParameterizedTypeWithTypeVariablesToParameterizedTypeWithWildcards2()github
org.jboss.cdi.tck.tests.lookup.injection.parameterized
ParameterizedTypesInjectionToParameterizedWithWildcardTest.testInjection()github
e)

Check the required type parameter is an actual type, the bean type parameter is a type variable and the actual type is assignable to the upper bound of the type variable

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution.parameterized
AssignabilityOfRawAndParameterizedTypesTest.testAssignabilityOfParameterizedTypeWithTypeVariablesToParameterizedTypeWithActualTypes()github
org.jboss.cdi.tck.tests.lookup.injection.parameterized
ParameterizedTypesInjectionToParameterizedWithActualTypeTest.testInjection()github
f)

Check the required type parameter and the bean type parameter are both type variables and the upper bound of the required type parameter is assignable to the upper bound of the bean type parameter.

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution.parameterized
AssignabilityOfRawAndParameterizedTypesTest.testAssignabilityOfParameterizedTypeWithTypeVariablesToParameterizedTypeTypeVariable()github
org.jboss.cdi.tck.tests.lookup.injection.parameterized
ParameterizedTypesInjectionToParameterizedWithTypeVariableUpperBoundTest.testInjection()github
ParameterizedTypesInjectionToParameterizedWithTypeVariableTest.testInjection()github
The following assertion is not made explicitly by the spec, however it is implied g)

A raw bean type is not assignable to a parameterized required type.

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution.parameterized.broken
RawBeanTypeParameterizedRequiredTypeTest.test()github

Section 5.2.5 - Primitive types and null values

If necessary, the container performs boxing or unboxing when it injects a value to a field or parameter of primitive or wrapper type.

aa)

Test boxing.

Coverage

org.jboss.cdi.tck.tests.lookup.injection
InjectionTest.testInjectionPerformsBoxingIfNecessary()github
org.jboss.cdi.tck.tests.lookup.typesafe.resolution
ResolutionByTypeTest.testResolveByTypeWithPrimitives()github
ab)

Test unboxing.

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution
ResolutionByTypeTest.testResolveByTypeWithPrimitives()github
b)

If an injection point of primitive type resolves to a producer method or producer field that returns a null value at runtime, the container must inject the primitive type's default value as defined by the Java Language Specification.

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution.primitive
PrimitiveInjectionPointTest.testPrimitiveInjectionPointResolvedToNonPrimitiveProducerMethod()github
c)

For a custom implementation of the Bean interface defined in Section 11.1, "The Bean interface", the container calls isNullable() to determine whether the bean may have null values.

Coverage

org.jboss.cdi.tck.tests.definition.bean.custom
CustomBeanImplementationTest.testIsNullableCalled()github
org.jboss.cdi.tck.tests.definition.bean
BeanDefinitionTest.testIsNullable()github

Section 5.2.6 - Qualifier annotations with members

a)A statement of intent

Qualifier types may have annotation members.

b)

An annotation member may be excluded from consideration using the @NonBinding annotation.

Coverage

org.jboss.cdi.tck.tests.lookup.binding.members.array
BindingAnnotationWithMemberTest.testArrayMemberWithNonBinding()github
org.jboss.cdi.tck.tests.lookup.binding.members.annotation
BindingAnnotationWithMemberTest.testAnnotationMemberWithNonBinding()github
org.jboss.cdi.tck.tests.lookup.typesafe.resolution
ResolutionByTypeTest.testResolveByTypeWithNonBindingMembers()github
c)

Array-valued or annotation-valued members of a qualifier type should be annotated @NonBinding in a portable application. If an array-valued or annotation-valued member of a qualifier is not annotated @NonBinding, non-portable behavior results.

Section 5.2.7 - Multiple qualifiers

a)

A bean class may declare multiple qualifiers.

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution
ResolutionByTypeTest.testAllQualifiersSpecifiedForResolutionMustAppearOnBean()github
b)

A producer method may declare multiple qualifiers.

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution
ResolutionByTypeTest.testResolveByTypeWithPrimitives()github
c)

A producer field may declare multiple qualifiers.

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution
ResolutionByTypeTest.testResolveByTypeWithPrimitives()github
d)

A bean must declare all of the qualifiers that are specified at the injection point to be considered a candidate for injection.

Coverage

org.jboss.cdi.tck.tests.lookup.typesafe.resolution
ResolutionByTypeTest.testAllQualifiersSpecifiedForResolutionMustAppearOnBean()github

Section 5.3 - EL Name resolution

d)

An EL name resolves to a bean if the bean has the given EL name, and the bean is available for injection in the war containing the JSP or JSF page with the EL expression.

Coverage

org.jboss.cdi.tck.tests.lookup.el.integration
IntegrationWithUnifiedELTest.testELResolverRegisteredWithJsf()github
IntegrationWithUnifiedELTest.testELResolverRegisteredWithServletContainer()github
e)

For a custom implementation of the Bean interface defined in Section 11.1, "The Bean interface", the container calls getName() to determine the bean EL name.

Coverage

org.jboss.cdi.tck.tests.definition.bean.custom
CustomBeanImplementationTest.testGetNameCalled()github

Section 5.3.1 - Ambiguous EL names

ca)

An ambiguous EL name exists in an EL expression when an EL name resolves to multiple beans. When an ambiguous EL name exists, the container attempts to resolve the ambiguity. If any of the beans are alternatives, the container eliminates all beans that are not alternatives. If there is exactly one bean remaining, the container will select this bean, and the ambiguous EL name is called resolvable.

Coverage

org.jboss.cdi.tck.tests.lookup.byname
ResolutionByNameTest.testAmbiguousELNamesResolved()github

All unresolvable ambiguous EL names are detected by the container when the application is initialized. Suppose two beans are both accessible to classes in a certain war, and either the two beans have the same EL name and the name is not resolvable, or the EL name of one bean is of the form x.y, where y is a valid bean EL name, and x is the EL name of the other bean, the container automatically detects the problem and treats it as a deployment problem.

da)

Test with two beans with the same EL name.

Coverage

org.jboss.cdi.tck.tests.lookup.byname.duplicateNameResolution
DuplicateNameResolutionTest.testDuplicateNamedBeans()github
db)

Test with with an EL name in the form x.y.

Coverage

org.jboss.cdi.tck.tests.lookup.byname.duplicatePrefixResolution
DuplicateNamePrefixResolutionTest.testDuplicateBeanNamePrefix()github

Section 5.4 - Client proxies

b)

A contextual reference to a bean with a normal scope, as defined in Section 6.3, “Normal scopes and pseudo-scopes”, is not a direct reference to a contextual instance of the bean (the object returned by Contextual.create()). Instead, the contextual reference is a client proxy object.

Coverage

org.jboss.cdi.tck.tests.lookup.clientProxy
ClientProxyTest.testClientProxyUsedForNormalScope()github
a)

Client proxies are never required for a bean whose scope is a pseudo-scope such as @Dependent.

The following assertion is not made explicitly by the spec, however it is implied c)For the statement

Client proxies are serializable

Coverage

org.jboss.cdi.tck.tests.lookup.clientProxy
ClientProxyTest.testSimpleBeanClientProxyIsSerializable()github
d)

The container must guarantee that when any valid injected reference to a bean of normal scope is invoked, the invocation is always processed by the current instance of the injected bean.

Coverage

org.jboss.cdi.tck.tests.lookup.clientProxy.incontainer
ClientProxyTest.testInvocationIsProcessedOnCurrentInstance()github
e)

Client proxies may be shared between multiple injection points.

Section 5.4.1 - Unproxyable bean types

Certain legal bean types cannot be proxied by the container. If an injection point whose declared type cannot be proxied by the container resolves to a bean with a normal scope, the container automatically detects the problem and treats it as a deployment problem.

aa)

Test a class which doesn't have a non-private constructor with no parameters.

Coverage

org.jboss.cdi.tck.tests.lookup.clientProxy.unproxyable.privateConstructor
PrivateConstructorTest.testClassWithPrivateConstructor()github
baa)

Test a class which is declared final.

Coverage

org.jboss.cdi.tck.tests.lookup.clientProxy.unproxyable.finalClass
FinalClassTest.testInjectionPointWithUnproxyableTypeWhichResolvesToNormalScopedBean()github
org.jboss.cdi.tck.tests.deployment.lifecycle.broken.normalScope
AddingNormalScopeTest.testAddingScopeType()github
bba)

Test a class that has non-static, final method with public visibility.

Coverage

org.jboss.cdi.tck.tests.lookup.clientProxy.unproxyable.finalMethod
NonPrivateNonStaticMethodTest.testClassWithPublicFinalMethodCannotBeProxied()github
bca)This is not allowed in CDI 1.0.

Test with a class that has static final method with public visibility.

Coverage

org.jboss.cdi.tck.tests.lookup.clientProxy.unproxyable.finalMethod
StaticFinalMethodTest.testClassWithStaticFinalMethodCanBeProxied()github
bda)This is not allowed in CDI 1.0.

Test a class that has final method with private visibility.

Coverage

org.jboss.cdi.tck.tests.lookup.clientProxy.unproxyable.finalMethod
PrivateFinalMethodTest.testClassWithPrivateFinalMethodCanBeProxied()github
ca)

Test primitive type

Coverage

org.jboss.cdi.tck.tests.lookup.clientProxy.unproxyable.primitive
UnproxyableTest.testInjectionPointWithUnproxyableTypeWhichResolvesToNormalScopedBean()github
da)

Test array type.

Coverage

org.jboss.cdi.tck.tests.lookup.clientProxy.unproxyable.array
ArrayTest.testInjectionPointWithArrayType()github

Section 5.4.2 - Client proxy invocation

aa)

Every time a method of the bean is invoked upon a client proxy, the client proxy must obtain a contextual instance of the bean, as defined in Section 6.5.2, "Contextual instance of a bean", and invoke the method upon this instance.

Coverage

org.jboss.cdi.tck.tests.lookup.clientProxy
ClientProxyTest.testClientProxyInvocation()github
ab)

If the scope is not active, as specified in Section 6.5.1, "The active context object for a scope", the client proxy rethrows ContextNotActiveException or IllegalStateException.

Coverage

org.jboss.cdi.tck.tests.lookup.clientProxy
ClientProxyTest.testInactiveScope()github
b)

The behavior of all methods declared by java.lang.Object, except for toString(), is undefined for a client proxy.

Section 5.5 - Dependency injection

a)

The container is required to perform dependency injection whenever it creates a contextual instance of a session bean.

Coverage

org.jboss.cdi.tck.tests.lookup.injection.enterprise
SessionBeanInjectionTest.testInjectionOnContextualSessionBean()github
b)

The container is required to perform dependency injection whenever it creates a contextual instance of a managed bean.

Coverage

org.jboss.cdi.tck.tests.lookup.injection
InjectionTest.testInjectionOfNamedBean()github
c)

The container is required to perform dependency injection whenever it instantiates non-contextual instances of session beans (for example, session beans obtained by the application from JNDI or injected using @EJB).

Coverage

org.jboss.cdi.tck.tests.lookup.injection.enterprise
SessionBeanInjectionTest.testInjectionOnNonContextualSessionBean()github
d)

The container is required to perform dependency injection whenever it instantiates non-contextual instances of managed beans.

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
InjectionIntoNonContextualComponentTest.testInjectionIntoJSFManagedBean()github
da)

The container is required to perform dependency injection whenever it instantiates non-contextual instances of enums.

Coverage

org.jboss.cdi.tck.tests.lookup.injection.enums
EnumInjectionTest.testBasicEnum()github

The container is required to perform dependency injection whenever it instantiates instances of any other Java EE component class supporting injection.

ea)

Test injection into a servlet listener

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
InjectionIntoNonContextualComponentTest.testInjectionIntoServletListener()github
eb)

Test injection into a tag handler

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
InjectionIntoNonContextualComponentTest.testInjectionIntoTagHandler()github
ec)

Test injection into a tag library listener

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
InjectionIntoNonContextualComponentTest.testInjectionIntoTagLibraryListener()github
ed)

Test injection into an EJB Interceptor

Coverage

org.jboss.cdi.tck.tests.lookup.injection.enterprise
SessionBeanInjectionTest.testInjectionOnEJBInterceptor()github
ee)

Test injection into a WS endpoint

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual.ws
WebServiceResourceTest.testInjectionIntoWebServiceEndpoint()github
ef)

Test injection into a servlet

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
InjectionIntoNonContextualComponentTest.testInjectionIntoServlet()github
eg)

Test injection into a filter

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
InjectionIntoNonContextualComponentTest.testInjectionIntoFilter()github
f)

A Java EE 5 container is not required to support injection for non-contextual objects.

g)

The container interacts with instances of beans, enums and other Java EE component classes supporting injection by calling methods and getting and setting the field values.

Coverage

No tests exist for this assertion

h)

The object injected by the container may not be a direct reference to a contextual instance of the bean. Instead, it is an injectable reference, as defined by Section 6.5.5, "Injectable references".

Coverage

No tests exist for this assertion

Section 5.5.1 - Injection using the bean constructor

When the container instantiates a managed bean or session bean with a constructor annotated @Inject, the container calls this constructor, passing an injectable reference to each parameter. If there is no constructor annotated @Inject, the container calls the constructor with no parameters.

aa)

Test managed bean with a constructor annotated @Inject.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.definition
SimpleBeanDefinitionTest.testInitializerAnnotatedConstructorUsedOverEmptyConstuctor()github
ab)

Test session bean with a constructor annotated @Inject.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.definition
EnterpriseBeanDefinitionTest.testConstructorAnnotatedInjectCalled()github
ba)

Test constructor with no parameters is used for a managed bean

Coverage

org.jboss.cdi.tck.tests.implementation.simple.definition
SimpleBeanDefinitionTest.testEmptyConstructorUsed()github
bb)

Test constructor with no parameters is used for a session bean

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.definition
EnterpriseBeanDefinitionTest.testConstructorWithNoParamsUsed()github

Section 5.5.2 - Injection of fields and initializer methods

When the container creates a new instance of a managed bean, session bean, enum or of any other Java EE component class supporting injection, the container must: Initialize the values of all injected fields. The container sets the value of each injected field to an injectable reference. Call all initializer methods, passing an injectable reference to each parameter.

aa)

Test session bean fields injected

Coverage

org.jboss.cdi.tck.tests.lookup.injection.enterprise
SessionBeanInjectionTest.testInjectionOnContextualSessionBean()github
ab)

Test session bean initializer methods called

Coverage

org.jboss.cdi.tck.tests.lookup.injection.enterprise
SessionBeanInjectionTest.testInjectionOnContextualSessionBean()github
ac)

Test managed bean fields injected

Coverage

org.jboss.cdi.tck.tests.lookup.injection
InjectionTest.testInjectionOfNamedBean()github
ad)

Test managed bean initializer methods called

Coverage

org.jboss.cdi.tck.tests.implementation.initializer
InitializerMethodTest.testMultipleInitializerMethodsAreCalled()github
ada)

Test enum fields injected

Coverage

org.jboss.cdi.tck.tests.lookup.injection.enums
EnumInjectionTest.testBasicEnum()github
EnumInjectionTest.testAdvancedEnum()github
adb)

Test enum initializer methods called

Coverage

org.jboss.cdi.tck.tests.lookup.injection.enums
EnumInjectionTest.testBasicEnum()github
EnumInjectionTest.testAdvancedEnum()github
ae)

Test Servlet fields injected

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
InjectionIntoNonContextualComponentTest.testInjectionIntoServlet()github
af)

Test Servlet initializer methods called

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
InjectionIntoNonContextualComponentTest.testServletInitializerMethodCalled()github
ag)

Test Servlet Filter fields injected

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
InjectionIntoNonContextualComponentTest.testInjectionIntoFilter()github
ah)

Test Servlet Filter initializer methods called

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
InjectionIntoNonContextualComponentTest.testFilterInitializerMethodCalled()github
ai)

Test Servlet Listener fields injected

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
InjectionIntoNonContextualComponentTest.testInjectionIntoServletListener()github
aj)

Test Servlet Listener initializer methods called

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
InjectionIntoNonContextualComponentTest.testServletListenerInitializerMethodCalled()github
ak)

Test non-contextual session bean fields injected

Coverage

org.jboss.cdi.tck.tests.lookup.injection.enterprise
SessionBeanInjectionTest.testInjectionOnNonContextualSessionBean()github
al)

Test non-contextual session bean initializer methods called

Coverage

org.jboss.cdi.tck.tests.lookup.injection.enterprise
SessionBeanInjectionTest.testInjectionOnNonContextualSessionBean()github
am)

Test tag handler fields injected

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
InjectionIntoNonContextualComponentTest.testInjectionIntoTagHandler()github
an)

Test tag handler initializer methods called

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
InjectionIntoNonContextualComponentTest.testInjectionIntoTagHandler()github
ao)

Test EJB interceptor fields injected

Coverage

org.jboss.cdi.tck.tests.lookup.injection.enterprise
SessionBeanInjectionTest.testInjectionOnEJBInterceptor()github
ap)

Test EJB interceptor initializer methods called

Coverage

org.jboss.cdi.tck.tests.lookup.injection.enterprise
SessionBeanInjectionTest.testInjectionOnEJBInterceptor()github
aq)

Test WS endpoint fields injected

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual.ws
WebServiceResourceTest.testInjectionIntoWebServiceEndpoint()github
ar)

Test WS endpoint bean initializer methods called

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual.ws
WebServiceResourceTest.testInjectionIntoWebServiceEndpoint()github
as)

Test tag handler listener fields injected

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
InjectionIntoNonContextualComponentTest.testInjectionIntoTagLibraryListener()github
at)

Test tag handler listener initializer methods called

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
InjectionIntoNonContextualComponentTest.testTagLibraryListenerInitializerMethodCalled()github
au)

Test JSF managed bean fields injected

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
InjectionIntoNonContextualComponentTest.testInjectionIntoJSFManagedBean()github
av)

Test JSF managed bean initializer methods called

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
InjectionIntoNonContextualComponentTest.testInjectionIntoJSFManagedBean()github

The container must ensure that: Initializer methods declared by a class X in the type hierarchy of the bean are called after all injected fields declared by X or by superclasses of X have been initialized, and after all Java EE component environment resource dependencies declared by X or by superclasses of X have been injected. Any @PostConstruct callback declared by a class X in the type hierarchy of the bean is called after all initializer meth- ods declared by X or by superclasses of X have been called, after all injected fields declared by X or by superclasses of X have been initialized, and after all Java EE component environment resource dependencies declared by X or by superclasses of X have been injected. Any servlet init() method is called after all initializer methods have been called, all injected fields have been initialized and all Java EE component environment resource dependencies have been injected.

ba)

Test session bean initializer methods called after injected field of X

Coverage

org.jboss.cdi.tck.tests.lookup.injection.enterprise
SessionBeanInjectionTest.testInjectionOnContextualSessionBean()github
bb)

Test session bean initializer methods called after injected field of superclass of X

Coverage

org.jboss.cdi.tck.tests.lookup.injection.enterprise
SessionBeanInjectionOrderingTest.testInitializerCalledAfterFieldInjectionOfSuperclass()github
bc)

Test session bean initializer methods called after EE resource injection of X

Coverage

org.jboss.cdi.tck.tests.lookup.injection.enterprise
SessionBeanInjectionOrderingTest.testInitializerCalledAfterResourceInjection()github
bd)

Test session bean initializer methods called after EE resource injection of superclass of X

Coverage

org.jboss.cdi.tck.tests.lookup.injection.enterprise
SessionBeanInjectionOrderingTest.testInitializerCalledAfterResourceInjection()github
be)

Test session bean @PostConstruct called after initializer of X

Coverage

org.jboss.cdi.tck.tests.lookup.injection.enterprise
SessionBeanInjectionTest.testInjectionOnContextualSessionBean()github
bf)

Test session bean @PostConstruct called after initializer of superclass of X

Coverage

org.jboss.cdi.tck.tests.lookup.injection.enterprise
SessionBeanInjectionOrderingTest.testPostConstructCalledAfterInitializerOfSuperclass()github
bg)

Test managed bean initializer methods called after injected field of X

Coverage

org.jboss.cdi.tck.tests.lookup.injection
InjectionTest.testInjectionFieldsAndInitializerMethods()github
bh)

Test managed bean initializer methods called after injected field of superclass of X

Coverage

org.jboss.cdi.tck.tests.lookup.injection
InjectionTest.testInjectionFieldsAndInitializerMethods()github
bi)

Test managed bean initializer methods called after EE resource injection of X

Coverage

No tests exist for this assertion

bj)

Test managed bean initializer methods called after EE resource injection of superclass of X

Coverage

No tests exist for this assertion

bk)

Test managed bean @PostConstruct called after initializer of X

Coverage

org.jboss.cdi.tck.tests.lookup.injection
InjectionTest.testInjectionFieldsAndInitializerMethods()github
bl)

Test managed bean @PostConstruct called after initializer of superclass of X

Coverage

org.jboss.cdi.tck.tests.lookup.injection
InjectionTest.testInjectionFieldsAndInitializerMethods()github
bm)

Servlet init() method called after initializer method

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
InjectionIntoNonContextualComponentTest.testServletInitializerMethodCalled()github
bn)

Servlet init() method called after injected fields

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
InjectionIntoNonContextualComponentTest.testInjectionIntoServlet()github
bo)

Servlet init() method called after Java EE resource injection

Coverage

No tests exist for this assertion

bp)

Servlet Filter init() method called after initializer method

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
InjectionIntoNonContextualComponentTest.testFilterInitializerMethodCalled()github
bq)

Servlet Filter init() method called after injected fields

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
InjectionIntoNonContextualComponentTest.testInjectionIntoFilter()github
br)

Servlet Filter init() method called after Java EE resource injection

Coverage

No tests exist for this assertion

Section 5.5.3 - Destruction of dependent objects

a)

When the container destroys an instance of a bean, enum or of any Java EE component class supporting injection, the container destroys all dependent objects, as defined in Section 6.4.2, "Destruction of objects with scope @Dependent", after the @PreDestroy callback completes and after the servlet destroy() method is called.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.lifecycle
EnterpriseBeanLifecycleTest.testDependentObjectsDestroyed()github
org.jboss.cdi.tck.tests.implementation.simple.lifecycle
SimpleBeanLifecycleTest.testDependentsDestroyedAfterPreDestroy()github

Section 5.5.4 - Invocation of producer or disposer methods

a)

When the container calls a producer method, if the method is static, the container must invoke the method.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testStaticMethod()github
b)

When the container calls a disposer method, if the method is static, the container must invoke the method.

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition
DisposalMethodDefinitionTest.testBindingTypesAppliedToDisposalMethodParameters()github
c)

When the container calls a producer method, if the method is non-static the container must obtain a contextual instance of the bean which declares the method, as defined by Section 6.5.2 "Contextual instance of a bean", then invoke the method upon this instance.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.lifecycle
ProducerMethodLifecycleTest.testProducerMethodFromSpecializedBeanUsed()github
org.jboss.cdi.tck.tests.inheritance.specialization.producer.method.enterprise
EnterpriseProducerMethodSpecializationTest.testSpecializingProducerMethod()github
org.jboss.cdi.tck.tests.inheritance.specialization.producer.method
ProducerMethodSpecializationTest.testSpecializingProducerMethod()github
d)

When the container calls a disposer method, if the method is non-static the container must obtain a contextual instance of the bean which declares the method, as defined by Section 6.5.2 "Contextual instance of a bean", then invoke the method upon this instance.

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testDependentsDestroyedWhenDisposerMethodCompletes()github
e)

The container passes an injectable reference to each injected method parameter.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.definition
ProducerMethodDefinitionTest.testBindingTypesAppliedToProducerMethodParameters()github
org.jboss.cdi.tck.tests.implementation.disposal.method.definition
DisposalMethodDefinitionTest.testDisposalMethodParametersGetInjected()github
f)

The container is also responsible for destroying dependent objects created during this invocation, as defined in Section 6.4.2, "Destruction of objects with scope @Dependent".

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testDependentsDestroyedWhenProducerMethodCompletes()github
DependentContextTest.testDependentsDestroyedWhenDisposerMethodCompletes()github

Section 5.5.5 - Access to producer field values

a)

When the container accesses the value of a producer field, if the producer field is static, the container must access the field value.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.lifecycle
ProducerFieldLifecycleTest.testProducerStaticFieldBean()github
b)

When the container accesses the value of a producer field, if the producer field is non-static, the container must obtain a contextual instance of the bean which declares the producer field, as defined by Section 6.5.2 "Contextual instance of a bean", then access the field value of this instance.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.lifecycle
ProducerFieldLifecycleTest.testProducerFieldBeanCreate()github

Section 5.5.6 - Invocation of observer methods

a)

When the container calls an observer method (defined in Section 10.4 "Observer methods"), if the observer method is static, the container must invoke the method.

Coverage

org.jboss.cdi.tck.tests.event
EventTest.testStaticObserverMethodInvoked()github
baa)

When the container calls an observer method (defined in Section 10.4 "Observer methods"), if the observer method is non-static, the container must obtain a contextual instance of the bean according to Section 6.5.2 "Contextual instance of a bean". If this observer method is a conditional observer method, obtain the contextual instance that already exists, only if the scope of the bean that declares the observer method is currently active, without creating a new contextual instance. Finally, the container must invoke the observer method on the resulting instance, if any, as a business method invocation, as defined in Section 7.2 "Container invocations and interception".

Coverage

org.jboss.cdi.tck.tests.event.observer.conditional
ConditionalObserverTest.testObserverMethodInvokedOnReturnedInstanceFromContext()github
ConditionalObserverTest.testConditionalObserver()github
org.jboss.cdi.tck.tests.event
EventTest.testObserverCalledOnSpecializedBeanOnly()github
c)

The container must pass the event object to the event parameter and an injectable instance to each injected method parameter.

Coverage

org.jboss.cdi.tck.tests.event
EventTest.testObserverMethodParameterInjectionPoints()github
d)

The container is also responsible for destroying dependent objects created during this invocation, as defined in Section 6.4.2, "Destruction of objects with scope @Dependent".

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testDependentsDestroyedWhenObserverMethodEvaluationCompletes()github

Section 5.5.7 - Injection point metadata

aa)

The javax.enterprise.inject.spi.InjectionPoint.getBean() method returns the Bean object representing the bean that defines the injection point.

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint
InjectionPointTest.testGetBean()github
aaa)

If the injection point does not belong to a bean, getBean() returns a null value.

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint.non.contextual
NonContextualInjectionPointTest.testEnumInjectionPointGetBean()github
NonContextualInjectionPointTest.testEjbInjectionPointGetBean()github
aab)

If the injection point represents a dynamically obtained instance, the getBean() method should return the Bean object representing the bean that defines the Instance injection point.

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint.dynamic
DynamicInjectionPointTest.testInjectionPointGetBean()github
ba)

The javax.enterprise.inject.spi.InjectionPoint.getType() method returns the declared type of the injection point.

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint
InjectionPointTest.testGetType()github
baa)

If the injection point represents a dynamically obtained instance, the javax.enterprise.inject.spi.InjectionPoint.getType() method returns the required type (as defined by Instance.select()).

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint.dynamic
DynamicInjectionPointTest.testInjectionPointGetType()github
bc)

The javax.enterprise.inject.spi.InjectionPoint.getQualifiers() method returns the declared qualifiers of the injection point.

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint
InjectionPointTest.testGetBindingTypes()github
bca)

If the injection point represents a dynamically obtained instance, the javax.enterprise.inject.spi.InjectionPoint.getQualifiers() method returns required qualifiers of the injection point including any additional required qualifers (as defined by Instance.select()).

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint.dynamic
DynamicInjectionPointTest.testInjectionPointGetQualifiers()github
ca)

The javax.enterprise.inject.spi.InjectionPoint.getMember() method returns the Field object in the case of field injection.

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint
InjectionPointTest.testGetMemberField()github
caa)

If the injection point represents a dynamically obtained instance, the javax.enterprise.inject.spi.InjectionPoint.getMember() method returns the Field object representing the field that defines the Instance injection point in the case of field injection.

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint.dynamic
DynamicInjectionPointTest.testInjectionPointGetMember()github
cb)

The javax.enterprise.inject.spi.InjectionPoint.getMember() method returns the Method object in the case of method parameter injection.

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint
InjectionPointTest.testGetMemberMethod()github
cba)

If the injection point represents a dynamically obtained instance, the javax.enterprise.inject.spi.InjectionPoint.getMember() method returns the Method object representing the method that defines the Instance injection point in the case of method parameter injection.

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint.dynamic
DynamicInjectionPointTest.testInjectionPointGetMember()github
cc)

The javax.enterprise.inject.spi.InjectionPoint.getMember() method returns the Constructor object in the case of constructor parameter injection.

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint
InjectionPointTest.testGetMemberConstructor()github
cca)

If the injection point represents a dynamically obtained instance, the javax.enterprise.inject.spi.InjectionPoint.getMember() method returns the Constructor object representing the constructor that defines the Instance injection point in the case of constructor parameter injection.

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint.dynamic
DynamicInjectionPointTest.testInjectionPointGetMember()github
daa)

The getAnnotated() method returns an instance of javax.enterprise.inject.spi.AnnotatedField or javax.enterprise.inject.spi.AnnotatedParameter, depending upon whether the injection point is an injected field or a constructor/method parameter.

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint
InjectionPointTest.testGetAnnotatedField()github
InjectionPointTest.testGetAnnotatedParameter()github
dab)

If the injection point represents a dynamically obtained instance, then the getAnnotated() method returns an instance of javax.enterprise.inject.spi.AnnotatedField or javax.enterprise.inject.spi.AnnotatedParameter representing the Instance injection point, depending upon whether the injection point is an injected field or a constructor/method parameter.

Coverage

No tests exist for this assertion

dba)

The isDelegate() method returns true if the injection point is a decorator delegate injection point, and false otherwise.

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint
InjectionPointTest.testIsDelegate()github
dbb)

If the injection point represents a dynamically obtained instance then isDelegate() returns false.

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint.dynamic
DynamicInjectionPointTest.testInjectionPointIsDelegate()github
dca)

The isTransient() method returns true if the injection point is a transient field, and false otherwise.

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint
InjectionPointTest.testIsTransient()github
dcb)

If the injection point represents a dynamically obtained instance then the isTransient() method returns true if the Instance injection point is a transient field, and false otherwise.

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint.dynamic
DynamicInjectionPointTest.testInjectionPointIsTransient()github
ea)

The container must provide a bean with scope @Dependent, bean type InjectionPoint and qualifier @Default, allowing dependent objects, as defined in Section 6.4.1, "Dependent objects", to obtain information about the injection point to which they belong.

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint
InjectionPointTest.testDependentScope()github
InjectionPointTest.testApiTypeInjectionPoint()github
InjectionPointTest.testCurrentBinding()github
eb)

The built-in implementation must be a passivation capable dependency, as defined in Section 6.6.2, "Passivation capable dependencies".

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint
InjectionPointTest.testPassivationCapability()github
f)

If a bean that declares any scope other than @Dependent has an injection point of type InjectionPoint and qualifier @Default, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint.broken.normal.scope
NormalScopedBeanWithInjectionPoint.testSessionScopedBeanWithInjectionPoint()github
ga)

If a Java EE component class supporting injection that is not a bean has an injection point of type InjectionPoint and qualifier @Default, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint.broken.not.bean
InjectionPointTest.testDefinitionErrorDetected()github
h)

The InjectionPoint injected into a disposer method represents the producer method for which the disposer method is being invoked.

Coverage

org.jboss.cdi.tck.tests.implementation.disposal.method.definition.injectionpoint
DisposalMethodInjectionPointTest.test()github
i)

The InjectionPoint injected into a decorator represents the injection point on the bean the decorated type is injected into.

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint
InjectionPointTest.testDecoratorInjectionPoint()github

Section 5.5.8 - Bean metadata

The container must provide beans allowing a bean instance to obtain a Bean, Interceptor or Decorator instance containing its metadata.

a)

Bean with scope @Dependent, qualifier @Default and type Bean can be injected into any bean instance.

Coverage

org.jboss.cdi.tck.tests.implementation.builtin.metadata
BuiltinMetadataBeanTest.testBeanMetadata()github
BuiltinMetadataBeanTest.testProducerAndDisposerMethodMetadata()github
b)

Bean with scope @Dependent, qualifier @Default and type Interceptor can be injected into any interceptor instance.

Coverage

org.jboss.cdi.tck.tests.implementation.builtin.metadata
BuiltinMetadataBeanTest.testInterceptorMetadata()github
c)

Bean with scope @Dependent, qualifier @Default and type Decorator which can be injected into any decorator instance.

Coverage

org.jboss.cdi.tck.tests.implementation.builtin.metadata
BuiltinMetadataBeanTest.testDecoratorMetadata()github

Additionally, the container must provide beans allowing interceptors and decorators to obtain information about the beans they intercept and decorate.

d)

Bean with scope @Dependent, qualifier @@Decorated and type Bean can be injected into any decorator instance.

Coverage

org.jboss.cdi.tck.tests.implementation.builtin.metadata
BuiltinMetadataBeanTest.testInterceptorMetadata()github
e)

Bean with scope @Dependent, qualifier @Intercepted and type Bean which can be injected into any interceptor instance.

Coverage

org.jboss.cdi.tck.tests.implementation.builtin.metadata
BuiltinMetadataBeanTest.testDecoratorMetadata()github
f)

These beans are passivation capable dependencies, as defined in Section 6.6.2, "Passivation capable dependencies".

Coverage

org.jboss.cdi.tck.tests.implementation.builtin.metadata
BuiltinMetadataBeanTest.testBeanMetadata()github
BuiltinMetadataBeanTest.testProducerAndDisposerMethodMetadata()github
BuiltinMetadataBeanTest.testInterceptorMetadata()github
BuiltinMetadataBeanTest.testDecoratorMetadata()github
h)

If an Interceptor instance is injected into a bean instance other than an interceptor instance, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.builtin.metadata.broken.injection
BuiltinInterceptorInjectionTest.testDeploymentFails()github
i)

If a Decorator instance is injected into a bean instance other than a decorator instance, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.builtin.metadata.broken.injection
BuiltinDecoratorInjectionTest.testDeploymentFails()github

The injection of bean metadata is restricted.

j)

If the injection point is a field, an initializer method parameter or a bean constructor, with qualifier @Default and type parameter of the injected Bean is not the same as the type declaring the injection point, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.builtin.metadata.broken.typeparam
BeanTypeParamInitializerTest.testDeploymentFails()github
BeanTypeParamConstructorTest.testDeploymentFails()github
BeanTypeParamFieldTest.testDeploymentFails()github
k)

If the injection point is a field, an initializer method parameter or a bean constructor, with qualifier @Default and type parameter of the injected Interceptor is not the same as the type declaring the injection point, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.builtin.metadata.broken.typeparam.interceptor
InterceptorTypeParamInitializerTest.testDeploymentFails()github
InterceptorTypeParamFieldTest.testDeploymentFails()github
InterceptorTypeParamConstructorTest.testDeploymentFails()github
l)

If the injection point is a field, an initializer method parameter or a bean constructor, with qualifier @Default and type parameter of the injected Decorator is not the same as the type declaring the injection point, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.builtin.metadata.broken.typeparam.decorator
DecoratorTypeParamFieldTest.testDeploymentFails()github
DecoratorTypeParamInitializerTest.testDeploymentFails()github
DecoratorTypeParamConstructorTest.testDeploymentFails()github
m)

If the injection point is a field, an initializer method parameter or a bean constructor of an interceptor, with qualifier @Intercepted and the type parameter of the injected Bean is not an unbounded wildcard, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.builtin.metadata.broken.typeparam.interceptor
InterceptedBeanTypeParamInitializerTest.testDeploymentFails()github
InterceptedBeanTypeParamConstructorTest.testDeploymentFails()github
InterceptedBeanTypeParamFieldTest.testDeploymentFails()github
n)

If he injection point is a field, an initializer method parameter or a bean constructor of a decorator, with qualifier @Decorated and the type parameter of the injected Bean is not the same as the delegate type, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.builtin.metadata.broken.typeparam.decorator
DecoratoredBeanTypeParamInitializerTest.testDeploymentFails()github
DecoratoredBeanTypeParamConstructorTest.testDeploymentFails()github
DecoratoredBeanTypeParamFieldTest.testDeploymentFails()github
o)

If the injection point is a producer method parameter and the type parameter of the injected Bean is not the same as the producer method return type, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.builtin.metadata.broken.typeparam
BeanTypeParamProducerTest.testDeploymentFails()github
p)

If the injection point is a disposer method parameter and the type parameter of the injected Bean is not the same as the disposed parameter, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.implementation.builtin.metadata.broken.typeparam
BeanTypeParamDisposerTest.testDeploymentFails()github
q)

If a Bean instance is injected into a disposer method, it represents the producer method to which the disposer method is bound.

Coverage

org.jboss.cdi.tck.tests.implementation.builtin.metadata
BuiltinMetadataBeanTest.testProducerAndDisposerMethodMetadata()github

Section 5.6 - Programmatic lookup

aa)

An instance of the javax.enterprise.inject.Instance interface may be injected.

Coverage

org.jboss.cdi.tck.tests.lookup.dynamic
DynamicLookupTest.testObtainsInjectsInstanceOfInstance()github
ba)

The method javax.enterprise.inject.Instance.get() returns a contextual reference.

Coverage

org.jboss.cdi.tck.tests.lookup.dynamic
DynamicLookupTest.testGetMethod()github
ca)

Any combination of qualifiers may be specified at the injection point.

Coverage

org.jboss.cdi.tck.tests.lookup.dynamic
DynamicLookupTest.testGetMethod()github
da)

The @Any qualifier may be used to allow the application to specify qualifiers dynamically.

Coverage

org.jboss.cdi.tck.tests.lookup.dynamic
DynamicLookupTest.testIsAmbiguous()github
e)

The @New qualifier may be used, allowing the application to obtain a @New qualified bean, as defined in Section 3.12, "@New qualified beans".

Coverage

org.jboss.cdi.tck.tests.lookup.dynamic
DynamicLookupTest.testNewBean()github

Section 5.6.1 - The Instance interface

aa)

The Instance interface provides a method for obtaining instances of beans with a specified combination of required type and qualifiers, and inherits the ability to iterate beans with that combination of required type and qualifiers from java.lang.Iterable.

Coverage

org.jboss.cdi.tck.tests.lookup.dynamic
DynamicLookupTest.testGetMethod()github
DynamicLookupTest.testIteratorMethod()github
ab)

For an injected Instance, the required type is the type parameter specified at the injection point, and the required qualifiers are the qualifiers specified at the injection point.

Coverage

org.jboss.cdi.tck.tests.lookup.dynamic
DynamicLookupTest.testGetMethod()github
ba)

The select() method returns a child Instance for a given required type and additional required qualifiers. If no required type is given, the required type is the same as the parent.

Coverage

org.jboss.cdi.tck.tests.lookup.dynamic
DynamicLookupTest.testIteratorMethod()github
c)

If an injection point of raw type Instance is defined, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.lookup.dynamic.broken.raw
RawInstanceConstructorInjectionTest.testDefinitionError()github
RawInstanceProcessInjectionPointTest.testDefinitionError()github
RawInstanceInitMethodInjectionTest.testDefinitionError()github
RawInstanceObserverInjectionTest.testDefinitionError()github
RawInstanceDisposerInjectionTest.testDefinitionError()github
RawInstanceCustomBeanTest.testDefinitionError()github
RawInstanceProducerMethodInjectionTest.testDefinitionError()github
RawInstanceFieldInjectionTest.testDefinitionError()github
da)

If two instances of the same qualifier type are passed to select(), an IllegalArgumentException is thrown.

Coverage

org.jboss.cdi.tck.tests.lookup.dynamic
DynamicLookupTest.testDuplicateBindingsThrowsException()github
e)

If an instance of an annotation that is not a qualifier type is passed to select(), an IllegalArgumentException is thrown.

Coverage

org.jboss.cdi.tck.tests.lookup.dynamic
DynamicLookupTest.testNonBindingThrowsException()github
org.jboss.cdi.tck.tests.lookup.dynamic.destroy.normal
DestroyingNormalScopedInstanceTest.testUnsupportedOperationExceptionThrownIfUnderlyingContextNotAlterable()github
fa)

The get() method must identify a bean that has the required type and required qualifiers and is eligible for injection into the class into which the parent Instance was injected, according to the rules of typesafe resolution, as defined in Section 5.2, "Typesafe resolution", resolving ambiguities according to Section 5.2.1, "Unsatisfied and ambiguous dependencies".

Coverage

org.jboss.cdi.tck.tests.lookup.dynamic
DynamicLookupTest.testGetMethod()github
fba)

If typesafe resolution results in an unsatisfied dependency, throw an UnsatisfiedResolutionException.

Coverage

org.jboss.cdi.tck.tests.lookup.dynamic
DynamicLookupTest.testUnsatisfiedDependencyThrowsException()github
fbb)

If typesafe resolution results in an unresolvable ambiguous dependency, throw an AmbiguousResolutionException.

Coverage

org.jboss.cdi.tck.tests.lookup.dynamic
DynamicLookupTest.testAmbiguousDependencyThrowsException()github
fc)

Otherwise, obtain a contextual reference for the bean and the required type, as defined in Section 6.5.3, "Contextual reference for a bean".

Coverage

org.jboss.cdi.tck.tests.lookup.dynamic
DynamicLookupTest.testGetMethod()github
ja)

The iterator() method must identify the set of beans that have the required type and required qualifiers and are eligible for injection into the class into which the parent Instance was injected, according to the rules of typesafe resolution, as defined in Section 5.2, "Typesafe resolution".

Coverage

org.jboss.cdi.tck.tests.lookup.dynamic
DynamicLookupTest.testIteratorMethod()github
ka)

The iterator() method must return an Iterator, that iterates over the set of contextual references for the resulting beans and required type, as defined in Section 6.5.3, "Contextual reference for a bean".

Coverage

org.jboss.cdi.tck.tests.lookup.dynamic
DynamicLookupTest.testIteratorMethod()github
l)

The method isUnsatisfied() returns true if there is no bean that has the required type and qualifiers and is eligible for injection into the class into which the parent Instance was injected, or false otherwise.

Coverage

org.jboss.cdi.tck.tests.lookup.dynamic
DynamicLookupTest.testIsUnsatisfied()github
m)

The method isAmbiguous() returns true if there is more than one bean that has the required type and qualifiers and is eligible for injection into the class into which the parent Instance was injected, or false otherwise.

Coverage

org.jboss.cdi.tck.tests.lookup.dynamic
DynamicLookupTest.testIsAmbiguous()github

The method destroy() instructs the container to destroy the instance. The bean instance passed to destroy() should be a dependent scoped bean instance, or a client proxy for a normal scoped bean. Applications are encouraged to always call destroy() when they no longer require an instance obtained from Instance.

n)

Test dependent scoped bean instance passed to destroy().

Coverage

org.jboss.cdi.tck.tests.lookup.dynamic.destroy.dependent
DestroyingDependentInstanceTest.testDestroyingDependentInstances()github
DestroyingDependentInstanceTest.testDestroyingInterceptedDependentBean()github
o)

Test client proxy passed to destroy().

Coverage

org.jboss.cdi.tck.tests.lookup.dynamic.destroy.normal
DestroyingNormalScopedInstanceTest.testApplicationScopedComponent()github
DestroyingNormalScopedInstanceTest.testRequestScopedComponent()github
DestroyingNormalScopedInstanceTest.testCustomScopedComponent()github
DestroyingNormalScopedInstanceTest.testContextDestroyCalled()github
DestroyingNormalScopedInstanceTest.testNullParameter()github
The following assertion is not made explicitly by the spec, however it is implied p)

Test UnsupportedOperationException is thrown when if the active context object for the scope type of the bean does not support destroying bean instances.

Coverage

No tests exist for this assertion

Section 5.6.2 - The built-in Instance

a)FIXME - see also CDI-232.

The container must provide a built-in bean with Instance<X> and Provider<X> for every legal bean type x in its set of bean types.

b)FIXME - see also CDI-232.

The container must provide a built-in bean with every qualifier type in its set of qualifier types.

d)

The container must provide a built-in bean with scope @Dependent.

Coverage

org.jboss.cdi.tck.tests.lookup.dynamic.builtin
BuiltinInstanceTest.testScopeOfBuiltinInstance()github
e)

The container must provide a built-in bean with no bean EL name.

Coverage

org.jboss.cdi.tck.tests.lookup.dynamic.builtin
BuiltinInstanceTest.testNameOfBuiltinInstance()github
f)

The container must provide a built-in bean with an implementation provided automatically by the container.

Coverage

org.jboss.cdi.tck.tests.lookup.dynamic.builtin
BuiltinInstanceTest.testInstanceProvidedForEveryLegalBeanType()github
g)

The built-in implementation must be a passivation capable dependency, as defined in Section 6.6.2, "Passivation capable dependencies".

Coverage

org.jboss.cdi.tck.tests.lookup.dynamic.builtin
BuiltinInstanceTest.testInstanceIsPassivationCapable()github

Section 5.6.3 - Using AnnotationLiteral and TypeLiteral

The following assertion is not made explicitly by the spec, however it is implied a)

Test javax.enterprise.util.AnnotationLiteral when using Instance.select() to specify qualifiers.

Coverage

org.jboss.cdi.tck.tests.lookup.dynamic
DynamicLookupTest.testIteratorMethod()github
The following assertion is not made explicitly by the spec, however it is implied b)

Test javax.enterprise.util.TypeLiteral when specifying a parameterized type with actual type parameters when calling Instance.select().

Coverage

org.jboss.cdi.tck.tests.lookup.dynamic
DynamicLookupTest.testNewBean()github

Section 6.1 - The Contextual interface

a0)

If an exception occurs while creating an instance, the exception is rethrown by the create() method. If the exception is a checked exception, it must be wrapped and rethrown as an (unchecked) CreationException.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.lifecycle
SimpleBeanLifecycleTest.testCreationExceptionWrapsCheckedExceptionThrownFromCreate()github
SimpleBeanLifecycleTest.testUncheckedExceptionThrownFromCreateNotWrapped()github
org.jboss.cdi.tck.tests.implementation.producer.method.lifecycle
ProducerMethodLifecycleTest.testCreateRethrowsUncheckedException()github
ProducerMethodLifecycleTest.testCreateWrapsCheckedExceptionAndRethrows()github
a1)

If an exception occurs while destroying an instance, the exception must be caught by the destroy() method.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.lifecycle
SimpleBeanLifecycleTest.testContextualDestroyCatchesException()github
a2)A statement about container specific behavior which is not spec defined

If the application invokes a contextual instance after it has been destroyed, the behavior is undefined.

a)Advice only

The container and portable extensions may define implementations of the Contextual interface that do not extend Bean, but it is not recommended that applications directly implement Contextual.

Section 6.1.1 - The CreationalContext interface

ca)introductory text

The interface javax.enterprise.context.spi.CreationalContext provides operations that are used by the Contextual implementation during instance creation and destruction.

d)

push() registers an incompletely initialized contextual instance with the container. A contextual instance is considered incompletely initialized until it is returned by the create() method.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.lifecycle
SimpleBeanLifecycleTest.testCreateReturnsSameBeanPushed()github
e)

release() destroys all dependent objects, as defined in Section 6.4.1, "Dependent objects", of the instance which is being destroyed, by passing each dependent object to the destroy() method of its Contextual object.

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testCallingCreationalContextReleaseDestroysDependents()github
f)

The implementation of Contextual is not required to call push(). However, for certain bean scopes, invocation of push() between instantiation and injection helps the container minimize the use of client proxy objects (which would otherwise be required to allow circular dependencies).

g)

If Contextual.create() calls push(), it must also return the instance passed to push().

Coverage

org.jboss.cdi.tck.tests.implementation.simple.lifecycle
SimpleBeanLifecycleTest.testCreateReturnsSameBeanPushed()github
h)Advice

Contextual.create() should use the given CreationalContext when obtaining contextual references to inject, as defined in Section 6.5.3, "Contextual reference for a bean", in order to ensure that any dependent objects are associated with the contextual instance that is being created.

i)Advice

Contextual.destroy() should call release() to allow the container to destroy dependent objects of the contextual instance.

Section 6.2 - The Context interface

aa)Introductory text

The javax.enterprise.context.spi.Context interface provides an operation for obtaining contextual instances with a particular scope of any contextual type.

ab)

The method getScope() returns the scope type of the context object.

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testContextScopeType()github
ha)

When a context object is active the isActive() method returns true. Otherwise, we say that the context object is inactive and the isActive() method returns false.

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testContextIsActive()github
DependentContextTest.testContextIsActiveWhenInvokingProducerMethod()github
j)

The Context.get() method may either return an existing instance of the given contextual type, or if no CreationalContext is given, return a null value, or if a CreationalContext is given, create a new instance of the given contextual type by calling Contextual.create() and return the new instance.

Coverage

org.jboss.cdi.tck.tests.context
NormalContextTest.testGetReturnsExistingInstance()github
k)

The Context.get() method may either return an existing instance of the given contextual type, or if no CreationalContext is given, return a null value, or if a CreationalContext is given, create a new instance of the given contextual type by calling Contextual.create() and return the new instance.

Coverage

org.jboss.cdi.tck.tests.context
GetWithNoCreationalContextTest.testGetWithoutCreationalContextReturnsNull()github
l)

The Context.get() method may either return an existing instance of the given contextual type, or if no CreationalContext is given, return a null value, or if a CreationalContext is given, create a new instance of the given contextual type by calling Contextual.create() and return the new instance.

Coverage

org.jboss.cdi.tck.tests.context
NormalContextTest.testGetReturnsExistingInstance()github
NormalContextTest.testGetWithCreationalContextReturnsNewInstance()github
org.jboss.cdi.tck.tests.implementation.simple.lifecycle
SimpleBeanLifecycleTest.testContextCreatesNewInstanceForInjection()github
m)

If the context object is inactive, the get() method must throw a ContextNotActiveException.

Coverage

org.jboss.cdi.tck.tests.context
GetOnInactiveContextTest.testInvokingGetOnInactiveContextFails()github
na)

The get() method may not return a null value unless no CreationalContext is given, or Contextual.create() returns a null value.

Coverage

org.jboss.cdi.tck.tests.context
GetWithNoCreationalContextTest.testGetWithoutCreationalContextReturnsNull()github
nb)

The get() method may not return a null value unless no CreationalContext is given, or Contextual.create() returns a null value.

Coverage

org.jboss.cdi.tck.tests.context
NormalContextTest.testGetMayNotReturnNullUnlessContextualCreateReturnsNull()github
o)

The get() method may not create a new instance of the given contextual type unless a CreationalContext is given.

Coverage

org.jboss.cdi.tck.tests.context
GetFromContextualTest.testGetMayNotCreateNewInstanceUnlessCreationalContextGiven()github
s)

When the container calls get() for a context that is associated with a passivating scope it must ensure that the given instance of Contextual and the instance of CreationalContext, if given, are serializable.

Coverage

org.jboss.cdi.tck.tests.context.passivating.custom
CustomPassivatingScopeCalledWithSerializableParametersTest.testWithImplicitBean()github
CustomPassivatingScopeCalledWithSerializableParametersTest.testWithExtensionProvidedBean()github
t)The AlterableContext interface was introduced in Contexts and Dependency Injection for Java EE 1.1 to allow bean instances to be destroyed by the application.

The destroy() method destroys an existing contextual instance, removing it from the context instance.

Coverage

org.jboss.cdi.tck.tests.context.alterable
AlterableContextTest.testApplicationScopedComponent()github
AlterableContextTest.testRequestScopedComponent()github
AlterableContextTest.testCustomScopedComponent()github
AlterableContextTest.testNothingHappensIfNoInstanceToDestroy()github
p)

The context object is responsible for destroying any contextual instance it creates by passing the instance to the destroy() method of the Contextual object representing the contextual type.

Coverage

org.jboss.cdi.tck.tests.context
ContextDestroysBeansTest.testContextDestroysBeansWhenDestroyed()github
q)

A destroyed instance must not subsequently be returned by the get() method.

Coverage

org.jboss.cdi.tck.tests.context
DestroyedInstanceReturnedByGetTest.testDestroyedInstanceMustNotBeReturnedByGet()github
r)

The context object must pass the same instance of CreationalContext to Contextual.destroy() that it passed to Contextual.create() when it created the instance.

Coverage

org.jboss.cdi.tck.tests.context
DestroyForSameCreationalContextTest.testDestroyForSameCreationalContextOnly()github
DestroyForSameCreationalContext2Test.testDestroyForSameCreationalContextOnly()github

Section 6.3 - Normal scopes and pseudo-scopes

a)Not testable through API

There may be no more than one mapped instance of a context object per contextual type per thread

b)A statement of intent

A context may be associated with one or more threads

c)

The get() operation of the Context object for an active normal scope returns the current instance of the given contextual type.

Coverage

org.jboss.cdi.tck.tests.context
NormalContextTest.testGetReturnsExistingInstance()github
d)

When a context is destroyed, all mapped instances belonging to that context are destroyed by passing them to the Contextual.destroy() method.

Coverage

org.jboss.cdi.tck.tests.context
ContextDestroysBeansTest.testContextDestroysBeansWhenDestroyed()github
e)

Contexts with normal scopes must obey the following rule: Suppose beans A, B and Z all have normal scopes. Suppose A has an injection point x, and B has an injection point y. Suppose further that both x and y resolve to bean Z according to the typesafe resolution algorithm. If a is the current instance of A, and b is the current instance of B, then both a.x and b.y refer to the same instance of Z. This instance is the current instance of Z.

Coverage

org.jboss.cdi.tck.tests.context
NormalContextTest.testSameNormalScopeBeanInjectedEverywhere()github
ea)A statement of intent

All normal scopes must be explicitly declared @NormalScope, to indicate to the container that a client proxy is required.

fa)A statement of intent

All pseudo-scopes must be explicitly declared @Scope, to indicate to the container that no client proxy is required.

g)A statement of intent

All scopes defined by this specification, except for the @Dependent pseudo-scope, are normal scopes

Section 6.4 - Dependent pseudo-scope

a)

When a bean is declared to have @Dependent scope, no injected instance of the bean is ever shared between multiple injection points.

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testInstanceNotSharedBetweenInjectionPoints()github
b)

When a bean is declared to have @Dependent scope, any instance of the bean injected into an object that is being created by the container is bound to the lifecycle of the newly created object.

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testDestroyingSimpleParentDestroysDependents()github
DependentContextTest.testDestroyingManagedParentDestroysDependentsOfSameBean()github
ca)

When a bean is declared to have @Dependent scope, when a unified EL expression in a JSF or JSP page that refers to the bean by its EL name is evaluated, at most one instance of the bean is instantiated. This instance exists to service just a single evaluation of the EL expression. It is reused if the bean EL name appears multiple times in the EL expression, but is never reused when the EL expression is evaluated again, or when another EL expression is evaluated.

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testInstanceUsedForElEvaluationNotShared()github

When a bean is declared to have @Dependent scope, any instance of the bean that receives a producer method, producer field, disposer method or observer method invocation exists to service that invocation only

da)

Test with a producer method.

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testInstanceUsedForProducerMethodNotShared()github
db)

Test with a producer field.

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testInstanceUsedForProducerFieldNotShared()github
dc)

Test with a disposer method.

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testInstanceUsedForDisposalMethodNotShared()github
dd)

Test with an observer method.

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testInstanceUsedForObserverMethodNotShared()github
dg)

When a bean id declared to have @Dependent scope, any instance of the bean injected into method parameters of a disposer method or observer method exists to service the method invocation only (except for observer methods of container lifecycle events).

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testInstanceUsedForDisposalMethodNotShared()github
DependentContextTest.testInstanceUsedForObserverMethodNotShared()github
e)

Every invocation of the get() operation of the Context object for the @Dependent scope with a CreationalContext returns a new instance of the given bean.

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testContextGetWithCreationalContextReturnsNewInstance()github
f)

Every invocation of the get() operation of the Context object for the @Dependent scope with no CreationalContext returns a null value.

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testContextGetWithCreateFalseReturnsNull()github
g)

The @Dependent scope is always active.

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testContextIsActiveWhenInvokingProducerField()github
DependentContextTest.testContextIsActiveWhenCreatingObserverMethodInstance()github
DependentContextTest.testContextIsActiveWhenEvaluatingElExpression()github
DependentContextTest.testContextIsActiveDuringBeanCreation()github
DependentContextTest.testContextIsActiveDuringInjection()github
DependentContextTest.testContextIsActive()github
DependentContextTest.testContextIsActiveWhenInvokingProducerMethod()github
DependentContextTest.testContextIsActiveWhenInvokingDisposalMethod()github

Section 6.4.1 - Dependent objects

Instances of interceptors or decorators with scope @Dependent are dependent objects of the bean instance they decorate.

aa)

Test with a @Dependent-scoped interceptor.

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testDependentScopedInterceptorsAreDependentObjectsOfBean()github
ab)

Test with a @Dependent-scoped decorator.

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testDependentScopedDecoratorsAreDependentObjectsOfBean()github

An instance of a bean with scope @Dependent injected into a field, bean constructor or initializer method is a dependent object of the bean or Java EE component class instance into which it was injected.

ga)

Test with @Dependent-scoped bean injected into field.

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testInstanceNotSharedBetweenInjectionPoints()github
DependentContextTest.testDependentBeanIsDependentObjectOfBeanInjectedInto()github
gb)

Test with @Dependent-scoped bean injected into bean constructor.

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testDependentBeanIsDependentObjectOfBeanInjectedInto()github
gc)

Test with @Dependent-scoped bean injected into initializer method.

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testDependentBeanIsDependentObjectOfBeanInjectedInto()github
h)

An instance of a bean with scope @Dependent injected into a producer method is a dependent object of the producer method bean instance that is being produced.

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testDependentsDestroyedWhenProducerMethodCompletes()github
i)

An instance of a bean with scope @Dependent obtained by direct invocation of an Instance is a dependent object of the instance of Instance.

Coverage

org.jboss.cdi.tck.tests.context.dependent.instance
BuiltinInstanceDependentObjectTest.testInstanceDependentObject()github

Section 6.4.2 - Destruction of objects with scope @Dependent

The container must ensure that all dependent objects of a non-contextual instance of a bean or other Java EE component class are destroyed when the instance is destroyed by the container.

aaaa)

Test with a managed bean.

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testDestroyingSimpleParentDestroysDependents()github
DependentContextTest.testDestroyingManagedParentDestroysDependentsOfSameBean()github
aaab)

Test with a Java EE component.

Coverage

org.jboss.cdi.tck.tests.context.dependent.ejb
DependentContextEjbTest.testDestroyingEjbDestroysDependents()github
DependentContextEjbTest.testDestroyingEjbDestroysDependentSimples()github

The container must ensure that all @Dependent scoped contextual instances injected into method parameters of a disposer method or observer method of any other event are destroyed when the invocation completes.

ccc)

Check disposer method

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testDependentsDestroyedWhenDisposerMethodCompletes()github
ccd)

Check observer method

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testDependentsDestroyedWhenObserverMethodEvaluationCompletes()github
org.jboss.cdi.tck.tests.context.dependent.instance
BuiltinInstanceDependentObjectTest.testInstanceDependentObject()github

The container must ensure that any @Dependent scoped contextual instance created to receive a producer method, producer field, disposer method or observer method invocation is destroyed when the invocation completes.

ddd)

Check producer method

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testDependentsDestroyedWhenProducerMethodCompletes()github
dde)

Check producer field

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testDependentsDestroyedWhenProducerFieldCompletes()github
ddf)

Check disposer method

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testDependentsDestroyedWhenDisposerMethodCompletes()github
ddg)

Check observer method

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testDependentsDestroyedWhenObserverMethodEvaluationCompletes()github
eee)

The container must ensure that all @Dependent scoped contextual instances created during evaluation of a Unified EL expression in a JSP or JSF page are destroyed when the evaluation completes.

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testDependentsDestroyedWhenElEvaluationCompletes()github
e)In other words this is unspecified

The container is permitted to destroy any @Dependent scoped contextual instance at any time if the instance is no longer referenced by the application (excluding weak, soft and phantom references).

Section 6.4.3 - Dependent pseudo-scope and Unified EL

a)

Suppose a Unified EL expression in a JSF or JSP page refers to a bean with scope @Dependent by its EL name. Each time the EL expression is evaluated the bean is instantiated at most once, and the resulting instance is reused for every appearance of the EL name, and the resulting instance is destroyed when the evaluation completes.

Coverage

org.jboss.cdi.tck.tests.lookup.el
ResolutionByNameTest.testQualifiedNameLookup()github
b)

Portable extensions that integrate with the container via Unified EL should also ensure that these rules are enforced.

Section 6.5.1 - The active context object for a scope

a)

From time to time, the container must obtain an active context object for a certain scope type. The container must search for an active instance of Context associated with the scope type. If no active context object exists for the scope type, the container throws a ContextNotActiveException.

Coverage

org.jboss.cdi.tck.tests.context
ContextTest.testGetContextWithNoRegisteredContextsFails()github
b)

If more than one active context object exists for the given scope type, the container must throw an IllegalStateException.

Coverage

org.jboss.cdi.tck.tests.context
ContextTest.testGetContextWithTooManyActiveContextsFails()github

Section 6.5.2 - Contextual instance of a bean

a)

From time to time, the container must obtain a contextual instance of a bean. The container must obtain the active context object for the bean scope, then obtain an instance of the bean by calling Context.get(), passing the Bean instance representing the bean and an instance of CreationalContext.

Coverage

org.jboss.cdi.tck.tests.lookup.el
ResolutionByNameTest.testContextCreatesNewInstanceForInjection()github
b)

From time to time, the container attempts to obtain a contextual instance of a bean that already exists, without creating a new contextual instance. The container must determine if the scope of the bean is active and if it is, obtain the active context object for the bean scope, then attempt to obtain an instance of the bean by calling Context.get(), passing the Bean instance representing the bean without passing any instance of CreationalContext.

Coverage

org.jboss.cdi.tck.tests.lookup.el
ResolutionByNameTest.testContextCreatesNewInstanceForInjection()github
c)Statement of intent

If the scope is not active, or if Context.get() returns a null value, there is no contextual instance that already exists.

e)

For a custom implementation of the Bean interface defined in Section 11.1, "The Bean interface", the container calls getScope() to determine the bean scope.

Coverage

org.jboss.cdi.tck.tests.definition.bean.custom
CustomBeanImplementationTest.testGetScopeTypeCalled()github

Section 6.5.3 - Contextual reference for a bean

a0)

Contextual references must be obtained with a given CreationalContext, allowing any instance of scope @Dependent that is created to be later destroyed.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.lifecycle
SimpleBeanLifecycleTest.testContextualDestroyDisposesWhenNecessary()github
a)

If the bean has a normal scope and the given bean type cannot be proxied by the container, as defined in Section 5.4.1, "Unproxyable bean types", the container throws an UnproxyableResolutionException.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.lifecycle.unproxyable
UnproxyableManagedBeanTest.testNormalScopedUnproxyableBeanResolution()github
b)

If the bean has a normal scope, then the contextual reference for the bean is a client proxy, as defined in Section 5.4, "Client proxies", created by the container, that implements the given bean type and all bean types of the bean which are Java interfaces.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.lifecycle
EnterpriseBeanLifecycleTest.testCreateSFSB()github
c)

If the bean has a pseudo-scope, the container must obtain a contextual instance of the bean. If the bean has scope @Dependent, the container must associate it with the CreationalContext.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.lifecycle
SimpleBeanLifecycleTest.testContextualDestroyDisposesWhenNecessary()github
d)

The container must ensure that every injection point of type InjectionPoint and qualifier @Default of any dependent object instantiated during this process receives an instance of InjectionPoint representing the injection point into which the dependent object will be injected, or a null value if it is not being injected into any injection point.

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint
InjectionPointTest.testGetBean()github

Section 6.5.4 - Contextual reference validity

a)

Any reference to a bean with a normal scope is valid as long as the application maintains a hard reference to it. However, it may only be invoked when the context associated with the normal scope is active. If it is invoked when the context is inactive, a ContextNotActiveException is thrown by the container.

Coverage

org.jboss.cdi.tck.tests.lookup.clientProxy
ClientProxyTest.testInactiveScope()github
b)Describes unspecified behavior

Any reference to a bean with a pseudo-scope (such as @Dependent) is valid until the bean instance to which it refers is destroyed. It may be invoked even if the context associated with the pseudo-scope is not active. If the application invokes a method of a reference to an instance that has already been destroyed, the behavior is undefined.

Section 6.5.5 - Injectable references

a)

From time to time, the container must obtain an injectable reference for an injection point. The container must identify a bean according to the rules defined in Section 5.2, "Typesafe resolution" and resolving ambiguities according to Section 5.2.1, "Unsatisfied and ambiguous dependencies", then obtain a contextual reference for this bean and the type of the injection point according to Section 6.5.3, "Contextual reference for a bean".

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint
InjectableReferenceTest.testGetInjectableReferenceOnBeanManager()github
b)

For certain combinations of scopes, the container is permitted to optimize the procedure for obtaining an injectable reference for an injection point - the container is permitted to directly inject a contextual instance of the bean, as defined in Section 6.5.2, "Contextual instance of a bean", and if an incompletely initialized instance of the bean is registered with the current CreationalContext, as defined in Section 6.1, "The Contextual interface", the container is permitted to directly inject this instance.

Section 6.5.6 - Injectable reference validity

a)

Injectable references to a bean must respect the rules of contextual reference validity, with the following exceptions - a reference to a bean injected into a field, bean constructor or initializer method is only valid until the object into which it was injected is destroyed, a reference to a bean injected into a producer method is only valid until the producer method bean instance that is being produced is destroyed, and a reference to a bean injected into a disposer method or observer method is only valid until the invocation of the method completes.

Coverage

No tests exist for this assertion

b)Behavior is undefined.

The application should not invoke a method of an invalid injected reference. If the application invokes a method of an invalid injected reference, the behavior is undefined.

Section 6.6 - Passivation and passivating scopes

The following assertion is not made explicitly by the spec, however it is implied a)

Test that passivation occurs.

Coverage

org.jboss.cdi.tck.tests.context.passivating
PassivatingContextTest.testPassivationOccurs()github

Section 6.6.1 - Passivation capable beans

As defined by the EJB specification, all stateful session beans are passivation capable if and only if all interceptors and decorators of the bean are passivation capable. Stateless and singleton session beans are not passivation capable.

a)

Test passivation capable stateful session bean.

Coverage

org.jboss.cdi.tck.tests.context.passivating.enterprise.valid
PassivationCapableSessionBeanTest.testDeployment()github

A managed bean is passivation capable if and only if the bean class is serializable and all interceptors and decorators of the bean are passivation capable.

ba)

Tests with a serializable bean class.

Coverage

org.jboss.cdi.tck.tests.context.passivating
PassivatingContextTest.testManagedBeanWithSerializableImplementationClassOK()github
bb)

Tests with a serializable interceptor.

Coverage

org.jboss.cdi.tck.tests.context.passivating
PassivatingContextTest.testManagedBeanWithSerializableInterceptorClassOK()github
bc)

Tests with a serializable decorator.

Coverage

org.jboss.cdi.tck.tests.context.passivating
PassivatingContextTest.testManagedBeanWithSerializableDecoratorOK()github
c)Tested in

A producer method is passivation capable if and only if it never returns a value which is not passivation capable at runtime.

d)Tested in

A producer field is passivation capable if and only if it never refers to a value which is not passivation capable at runtime.

A producer method is passivation capable if and only if it never returns a value which is not passivation capable at runtime.

caa)

Test that a producer method with a primitive return type is passivation capable.

A test exists for this untestable assertion!
ca)

Test that a producer method with a serializable return type is passivation capable.

Coverage

org.jboss.cdi.tck.tests.context.passivating
PassivatingContextTest.testPassivationCapableProducerMethodIsOK()github

A producer field is passivation capable if and only if it never refers to a value which is not passivation capable at runtime.

daa)

Test that a producer field with a primitive type is passivation capable.

Coverage

org.jboss.cdi.tck.tests.context.passivating.producer
ProducerWithPrimitiveFieldTypePassivationTest.testProducerFieldWithPrimitiveType()github
da)

Test that a producer field with a serializable type is passivation capable.

Coverage

org.jboss.cdi.tck.tests.context.passivating
PassivatingContextTest.testPassivationCapableProducerFieldIsOK()github
ea)

A custom implementation of Bean is passivation capable if it implements the interface PassivationCapable.

Coverage

No tests exist for this assertion

f)

An implementation of Contextual that is not a bean is passivation capable if it implements both PassivationCapable and Serializable.

Coverage

No tests exist for this assertion

g)This is a requirement of the implementation

The getId() method of the PassivationCapable implementation must return a value that uniquely identifies the instance of Bean or Contextual.

h)Recommendation only

The getId() method of the PassivationCapable implementation must return a value that uniquely identifies the instance of Bean or Contextual. It is recommended that the string contain the package name of the class that implements Bean or Contextual.

Section 6.6.2 - Passivation capable dependencies

a)

The container must guarantee that all session beans are passivation capable dependencies.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.lifecycle
EnterpriseBeanLifecycleTest.testSerializeSFSB()github
b)

The container must guarantee that all beans with normal scope are passivation capable dependencies.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.lifecycle
SimpleBeanLifecycleTest.testSerializeRequestScoped()github
SimpleBeanLifecycleTest.testSerializeSessionScoped()github
c)

The container must guarantee that all passivation capable beans with scope @Dependent are passivation capable dependencies.

Coverage

org.jboss.cdi.tck.tests.context.passivating
PassivatingContextTest.testInjectionOfDependentPrimitiveProductIntoNormalBean()github
PassivatingContextTest.testInjectionOfDependentSerializableProductIntoNormalBean()github
da)

The container must guarantee that all resources are passivation capable dependencies.

Coverage

No tests exist for this assertion

e)

The container must guarantee that the built-in beans of type Instance, Event, InjectionPoint and BeanManager are passivation capable dependencies.

Coverage

org.jboss.cdi.tck.tests.event.implicit
ImplicitEventTest.testImplicitEventIsPassivationCapable()github
fa)

A custom implementation of Bean is a passivation capable dependency if it implements PassivationCapable or if getScope() returns a normal scope type.

Coverage

No tests exist for this assertion

Section 6.6.3 - Passivating scopes

A passivating scope requires that beans with the scope are passivation capable, and implementations of Contextual passed to any context object for the scope are passivation capable.

a)

Test that a bean with the scope is passivation capable.

Coverage

org.jboss.cdi.tck.tests.context.passivating
PassivatingContextTest.testManagedBeanWithSerializableImplementationClassOK()github
org.jboss.cdi.tck.tests.context.passivating.broken.nonPassivationCapableManagedBeanHasPassivatingScope
NonPassivationManagedBeanHasPassivatingScopeTest.testSimpleWebBeanWithNonSerializableImplementationClassFails()github
b)This is in essence enforced by the stuff in 6.6.4

Test that an implementation of Contextual passed to the context object for the scope is passivation capable.

b)A statement of intent

Passivating scopes must be explicitly declared @NormalScope(passivating=true).

Section 6.6.4 - Validation of passivation capable beans and dependencies

If a managed bean or stateful session bean which declares a passivating scope is not passivation capable, then the container automatically detects the problem and treats it as a deployment problem.

a)

Test managed bean.

Coverage

org.jboss.cdi.tck.tests.deployment.lifecycle.broken.passivatingScope
AddingPassivatingScopeTest.testAddingScopeType()github
org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes.broken.passivation
PassivationCapabilityErrorCausedByExtensionDetectedTest.test()github
org.jboss.cdi.tck.tests.context.passivating.broken.nonPassivationCapableManagedBeanHasPassivatingScope
NonPassivationManagedBeanHasPassivatingScopeTest.testSimpleWebBeanWithNonSerializableImplementationClassFails()github
b)

Test stateful session bean.

Coverage

org.jboss.cdi.tck.tests.context.passivating.broken.enterpriseBeanWithNonPassivatingInterceptor
EnterpriseBeanWithNonPassivatingInterceptorTest.testEnterpriseBeanWithNonPassivatingDecoratorFails()github
org.jboss.cdi.tck.tests.context.passivating.broken.enterpriseBeanWithNonPassivatingDecorator
EnterpriseBeanWithNonPassivatingDecoratorTest.testEnterpriseBeanWithNonPassivatingDecoratorFails()github
aa)

If a managed bean which declares a passivating scope has a non-transient injected field that does not resolve to a passivation capable dependency, then the container automatically detects the problem and treats it as a deployment problem.

Coverage

org.jboss.cdi.tck.tests.context.passivating.broken.passivatingManagedBeanWithNonPassivatingInjcetedField
PassivatingManagedBeanWithNonPassivatingInjcetedFieldTest.testBeanWithNonSerializableImplementationInjectedIntoNonTransientFieldOfBeanWithPassivatingScopeFails()github
org.jboss.cdi.tck.tests.context.passivating.broken.sessionBeanWithPassivatingScopeNotSerializable
NonPassivationCapableEjbWithPassivatingScopeTest.testDeployment()github
org.jboss.cdi.tck.tests.context.passivating
PassivatingContextTest.testBeanWithNonSerializableImplementationInjectedIntoTransientFieldOK()github

If a managed bean which declares a passivating scope has an interceptor or decorator with a non-transient injected field that does not resolve to a passivation capable dependency, then the container automatically detects the problem and treats it as a deployment problem.

aac)

Test interceptor with injected field.

Coverage

org.jboss.cdi.tck.tests.context.passivating.broken.interceptorWithNonPassivatingInjectedField
PassivationCapableBeanWithNonPassivatingInterceptorTest.testPassivationCapableBeanWithNonPassivatingInterceptorFails()github
aaf)

Test decorator with injected field.

Coverage

org.jboss.cdi.tck.tests.context.passivating.broken.decoratorWithNonPassivatingInjectedField
DecoratorWithNonPassivatingInjectedFieldTest.testPassivationCapableBeanWithNonPassivatingDecoratorInjectedFieldFails()github
ba)

If a stateful session bean which declares a passivating scope has a non-transient injected field that does not resolve to a passivation capable dependency, then the container automatically detects the problem and treats it as a deployment problem.

Coverage

org.jboss.cdi.tck.tests.context.passivating.broken.unserializableSimpleInjectedIntoPassivatingEnterpriseBean
UnserializableSimpleInjectedIntoPassivatingEnterpriseBeanTest.testSimpleDependentWebBeanWithNonSerializableImplementationInjectedIntoStatefulSessionBeanFails()github

If a stateful session bean has an interceptor or decorator with a non-transient injected field that does not resolve to a passivation capable dependency, then the container automatically detects the problem and treats it as a deployment problem.

bda)

Test an interceptor with an injected field.

Coverage

org.jboss.cdi.tck.tests.context.passivating.broken.enterpriseBeanWithNonPassivatingInjectedFieldInInterceptor
EnterpriseBeanWithNonPassivatingInjectedFieldInInterceptorTest.testSessionBeanWithNonPassivatingInjectedFieldInInterceptorFails()github
bdd)

Test a decorator with an injected field.

Coverage

org.jboss.cdi.tck.tests.context.passivating.broken.enterpriseBeanWithNonPassivatingInjectedFieldInDecorator
EnterpriseBeanWithNonPassivatingInjectedFieldInDecoratorTest.testSessionBeanWithNonPassivatingInjectedFieldInDecoratorFails()github
ca)

If a producer method declares a passivating scope and has a return type that is declared final and does not implement or extend Serializable then the container automatically detects the problem and treats it as a deployment problem.

Coverage

org.jboss.cdi.tck.tests.context.passivating.broken.nonPassivationCapableProducerMethod
NonPassivationCapableProducerMethodTest.testNonPassivationCapableProducerMethodNotOk()github
ea)

If a producer method declares a passivating scope and doesn't only return Serializable types at runtime, then the container must throw an IllegalProductException.

Coverage

org.jboss.cdi.tck.tests.context.passivating
PassivatingContextTest.testPassivatingScopeProducerMethodReturnsUnserializableObjectNotOk()github
d)

If a producer field declares a passivating scope and has a type that is declared final and does not implement or extend Serializable then the container automatically detects the problem and treats it as a deployment problem.

Coverage

org.jboss.cdi.tck.tests.context.passivating.broken.nonPassivationCapableProducerField
NonPassivationCapableProducerFieldTest.testNonPassivationCapableProducerFieldNotOk()github
eb)

If a producer field declares a passivating scope and doesn't only contain Serializable values at runtime then the container must throw anIllegalProductException.

Coverage

org.jboss.cdi.tck.tests.context.passivating
PassivatingContextTest.testNonSerializableProducerFieldDeclaredPassivatingThrowsIllegalProductException()github

If a producer method or field of scope @Dependent returns an unserializable object for injection into an injection point that requires a passivation capable dependency, the container must throw an IllegalProductException

fab)

Test for a runtime exception with a producer method.

Coverage

org.jboss.cdi.tck.tests.context.passivating.broken.dependentScopedProducerMethodReturnsNonSerializableObjectForInjectionIntoStatefulSessionBean
EnterpriseBeanWithIllegalDependencyTest.test()github
fbb)

Test for a runtime exception with a producer field.

Coverage

org.jboss.cdi.tck.tests.context.passivating.broken.dependentScopedProducerFieldReturnsNonSerializableObjectForInjectionIntoStatefulSessionBean
EnterpriseBeanWithIllegalDependencyTest.test()github

For a custom implementation of Bean, the container calls getInjectionPoints() to determine the injection points, and InjectionPoint.isTransient() to determine whether the injected point is a transient field.

ga)

Test calling getInjectionPoints().

Coverage

org.jboss.cdi.tck.tests.definition.bean.custom
CustomBeanImplementationTest.testGetInjectionPointsCalled()github
gb)

Test calling InjectionPoint.isTransient().

Coverage

org.jboss.cdi.tck.tests.definition.bean.custom
CustomBeanImplementationTest.testGetInjectionPointsCalled()github

If a bean which declares a passivating scope type has a decorator or interceptor which is not a passivation capable dependency, the container automatically detects the problem and treats it as a deployment problem.

ha)

Test a bean with decorator which is not a passivation capable dependency.

Coverage

org.jboss.cdi.tck.tests.context.passivating.broken.managedBeanWithNonPassivatingDecorator
ManagedBeanWithNonPassivatingDecoratorTest.testManagedBeanWithNonPassivatingDecoratorFails()github
hb)

Test a stateful session bean with decorator which is not a passivation capable dependency.

Coverage

org.jboss.cdi.tck.tests.context.passivating.broken.enterpriseBeanWithNonPassivatingDecorator
EnterpriseBeanWithNonPassivatingDecoratorTest.testEnterpriseBeanWithNonPassivatingDecoratorFails()github
hc)

Test a bean with interceptor which is not a passivation capable dependency.

Coverage

org.jboss.cdi.tck.tests.context.passivating.broken.managedBeanWithNonSerializableInterceptorClass
ManagedBeanWithNonSerializableInterceptorClassTest.testManagedBeanWithNonSerializableInterceptorClassNotOK()github
hd)

Test a stateful session bean with interceptor which is not a passivation capable dependency.

Coverage

org.jboss.cdi.tck.tests.context.passivating.broken.enterpriseBeanWithNonPassivatingInterceptor
EnterpriseBeanWithNonPassivatingInterceptorTest.testEnterpriseBeanWithNonPassivatingDecoratorFails()github
The following assertion is not made explicitly by the spec, however it is implied ia)This was not allowed in CDI 1.0

Managed bean which declares a passivating scope may have bean constructor parameter or initializer method parameter that does not resolve to a passivation capable dependency.

Coverage

org.jboss.cdi.tck.tests.context.passivating.injection
NonPassivatingInjectionIntoPassivatingBeanTest.test()github
The following assertion is not made explicitly by the spec, however it is implied ib)This was not allowed in CDI 1.0

Stateful session bean which declares a passivating scope may have bean constructor parameter or initializer method parameter that does not resolve to a passivation capable dependency.

Coverage

org.jboss.cdi.tck.tests.context.passivating.injection
NonPassivatingInjectionIntoPassivatingBeanTest.test()github
The following assertion is not made explicitly by the spec, however it is implied j)This was not allowed in CDI 1.0

Stateful session bean which does not declare a passivating scope needn't be passivation capable.

Coverage

org.jboss.cdi.tck.tests.context.passivating.enterprise
NonPassivationCapableSessionBeanTest.testDeployment()github
The following assertion is not made explicitly by the spec, however it is implied k)

Passivation capable interceptor with non-passivation capable dependencies is allowed unless it intercepts a bean declaring passivation scope.

Coverage

org.jboss.cdi.tck.tests.context.passivating.validation
InterceptorWithNonPassivationCapableDependenciesTest.test()github
The following assertion is not made explicitly by the spec, however it is implied l)

Passivation capable decorator with non-passivation capable dependencies is allowed unless it decorates a bean declaring passivation scope.

Coverage

org.jboss.cdi.tck.tests.context.passivating.validation
DecoratorWithNonPassivationCapableDependenciesTest.testDeploymentValid()github

Section 6.7 - Context management for built-in scopes

The built-in request and application context objects are active during servlet, web service and EJB invocations, and the built in session and request context objects are active during servlet and web service invocations. For other kinds of invocations, a portable extension may define a custom context object for any or all of the built-in scopes.

Section 6.7.1 - Request context lifecycle

The request scope is active during the service() method of any servlet in the web application, during the doFilter() method of any servlet filter and when the container calls any ServletRequestListener or AsyncListener.

aa)

Check service() method.

Coverage

org.jboss.cdi.tck.tests.context.request
RequestContextTest.testRequestScopeActiveDuringServiceMethod()github
ab)

Check doFilter() method.

Coverage

org.jboss.cdi.tck.tests.context.request
RequestContextTest.testRequestScopeActiveDuringServletFilter()github
ac)

Check ServletRequestListener.

Coverage

org.jboss.cdi.tck.tests.context.request
RequestContextTest.testRequestScopeActiveDuringServiceMethod()github
RequestContextTest.testRequestScopeActiveDuringServletFilter()github
ad)

Check AsyncListener.

Coverage

org.jboss.cdi.tck.tests.context.request.async
RequestContextAsyncListenerTest.testRequestContextActiveOnTimeout()github
RequestContextAsyncListenerTest.testRequestContextActiveOnError()github
RequestContextAsyncListenerTest.testRequestContextActiveOnStartAsync()github
RequestContextAsyncListenerTest.testRequestContextActiveOnComplete()github
c)

The request scope is active during any Java EE web service invocation.

Coverage

org.jboss.cdi.tck.tests.context.request.jaxrs
RequestContextTest.testRequestScopeActiveDuringWebServiceInvocation()github
org.jboss.cdi.tck.tests.context.request.ws
RequestContextTest.testRequestScopeActiveDuringWebServiceInvocation()github

The request scope is active during any remote method invocation of any EJB, during any asynchronous method invocation of any EJB, during any call to an EJB timeout method and during message delivery to any EJB message-driven bean.

ga)

Test the request scope is active during a remote method invocation of any EJB.

Coverage

org.jboss.cdi.tck.tests.context.request.ejb
EJBRequestContextTest.testRequestScopeActiveDuringRemoteCallToEjb()github
gb)

Test the request scope is active during any asynchronous method invocation of any EJB.

Coverage

org.jboss.cdi.tck.tests.context.request.ejb
EJBRequestContextTest.testRequestScopeActiveDuringAsyncCallToEjb()github
gc)

Test the request scope is active during any call to an EJB timeout method.

Coverage

org.jboss.cdi.tck.tests.context.request.ejb
EJBRequestContextTest.testRequestScopeActiveDuringCallToEjbTimeoutMethod()github
gd)

Test the request scope is active during message delivery to any EJB message-driven bean.

Coverage

org.jboss.cdi.tck.tests.context.jms
MessageDrivenBeanContextTest.testRequestScopeActiveDuringMessageDelivery()github
e)

The request scope is active during @PostConstruct callback of any bean.

Coverage

org.jboss.cdi.tck.tests.context.request.postconstruct
SimpleBeanPostConstructCallbackTest.testSimplePostConstructCallback()github
EagerSingletonPostConstructCallbackTest.testEagerSingletonPostConstructCallback()github

The request context is destroyed at the end of the servlet request, after the service() method and all doFilter() methods, and all requestDestroyed() and onComplete() notifications return.

ba)

Check service() method.

Coverage

org.jboss.cdi.tck.tests.context.request
RequestContextTest.testRequestScopeIsDestroyedAfterServletRequest()github
bb)

Check doFilter() methods.

Coverage

org.jboss.cdi.tck.tests.context.request
RequestContextTest.testRequestScopeIsDestroyedAfterServletRequest()github
bc)

Check requestDestroyed() notification.

Coverage

org.jboss.cdi.tck.tests.context.request
RequestContextTest.testRequestScopeIsDestroyedAfterServletRequest()github
bd)

Check onComplete() notification.

Coverage

org.jboss.cdi.tck.tests.context.request.async
RequestContextAsyncListenerTest.testRequestContextActiveOnComplete()github
d)

The request context is destroyed after the web service invocation completes.

Coverage

org.jboss.cdi.tck.tests.context.request.jaxrs
RequestContextTest.testRequestScopeActiveDuringWebServiceInvocation()github
org.jboss.cdi.tck.tests.context.request.ws
RequestContextTest.testRequestScopeActiveDuringWebServiceInvocation()github

The request context is destroyed after the EJB remote method invocation, asynchronous method invocation, timeout or message delivery completes.

ha)

Test the request context is destroyed after an EJB remote method invocation.

Coverage

org.jboss.cdi.tck.tests.context.request.ejb
EJBRequestContextTest.testRequestScopeActiveDuringRemoteCallToEjb()github
hb)

Test the request context is destroyed after an EJB asynchronous method invocation.

Coverage

org.jboss.cdi.tck.tests.context.request.ejb
EJBRequestContextTest.testRequestScopeActiveDuringAsyncCallToEjb()github
hc)

Test the request context is destroyed after the EJB timeout.

Coverage

org.jboss.cdi.tck.tests.context.request.ejb
EJBRequestContextTest.testRequestScopeDestroyedAfterCallToEjbTimeoutMethod()github
hd)

Test the request context is destroyed after the message delivery completes.

Coverage

org.jboss.cdi.tck.tests.context.jms
MessageDrivenBeanContextTest.testRequestScopeActiveDuringMessageDelivery()github
f)

The request context is destroyed after the after the @PostConstruct callback completes, if it did not already exist when the @PostConstruct callback occurred.

Coverage

org.jboss.cdi.tck.tests.context.request.postconstruct
SimpleBeanPostConstructCallbackTest.testSimplePostConstructCallback()github
EagerSingletonPostConstructCallbackTest.testEagerSingletonPostConstructCallback()github

An event with qualifier @Initialized(RequestScoped.class) is fired when the request context is initialized and an event with qualifier @Destroyed(RequestScoped.class) when the request context is destroyed.

ja)

The event payload is the ServletRequestEvent if the context is initialized or destroyed due to a servlet request.

Coverage

org.jboss.cdi.tck.tests.deployment.shutdown
ApplicationShutdownLifecycleTest.testShutdown()github
org.jboss.cdi.tck.tests.context.request.event
RequestScopeEventTest.test()github
jb)

The event payload is the ServletRequestEvent if the context is initialized or destroyed due to a web service invocation.

Coverage

org.jboss.cdi.tck.tests.context.request.jaxrs
RequestContextTest.testRequestScopeActiveDuringWebServiceInvocation()github
jc)

The event payload is the java.lang.Object if the context is initialized or destroyed due to a EJB remote method invocation.

Coverage

org.jboss.cdi.tck.tests.context.request.event.remote
RequestScopeEventRemoteTest.testRequestScopeActiveDuringRemoteCallToEjb()github
jd)

The event payload is the java.lang.Object if the context is initialized or destroyed due to a EJB asynchronous method invocation.

Coverage

org.jboss.cdi.tck.tests.context.request.event.async
RequestScopeEventAsyncTest.testEventsFired()github
je)

The event payload is the java.lang.Object if the context is initialized or destroyed due to a EJB timeout method invocation.

Coverage

org.jboss.cdi.tck.tests.context.request.event.timeout
RequestScopeEventTimeoutTest.testEventsFired()github
jf)

The event payload is the java.lang.Object if the context is initialized or destroyed due to a message delivery to any EJB message-driven bean.

Coverage

org.jboss.cdi.tck.tests.context.request.event.jms
RequestScopeEventMessageDeliveryTest.testEventsFired()github

Section 6.7.2 - Session context lifecycle

aa)

The session scope is active during the service() method of any servlet in the web application , during the doFilter() method of any servlet filter and when the container calls any HttpSessionListener, AsyncListener or ServletRequestListener.

Coverage

org.jboss.cdi.tck.tests.context.session
SessionContextTest.testSessionScopeActiveDuringServiceMethod()github
ab)

The session scope is active during the service() method of any servlet in the web application, during the doFilter() method of any servlet filter and when the container calls any HttpSessionListener, AsyncListener or ServletRequestListener.

Coverage

org.jboss.cdi.tck.tests.context.session
SessionContextTest.testSessionScopeActiveDuringDoFilterMethod()github
b)

The session context is shared between all servlet requests that occur in the same HTTP servlet session.

Coverage

org.jboss.cdi.tck.tests.context.session
SessionContextTest.testSessionContextSharedBetweenServletRequestsInSameHttpSession()github
ca)

The session context is destroyed when the HTTPSession times out, after all HttpSessionListeners have been called, and at the very end of any request in which invalidate() was called, after all filters and ServletRequestListeners have been called.

Coverage

org.jboss.cdi.tck.tests.context.session
SessionContextTest.testSessionContextDestroyedWhenHttpSessionInvalidated()github
cb)

The session context is destroyed when the HTTPSession times out, after all HttpSessionListeners have been called, and at the very end of any request in which invalidate() was called, after all filters and ServletRequestListeners have been called.

Coverage

org.jboss.cdi.tck.tests.context.session
SessionContextTest.testSessionContextDestroyedWhenHttpSessionTimesOut()github
cd)

The session context is destroyed when the HTTPSession times out, after all HttpSessionListeners have been called, and at the very end of any request in which invalidate() was called, after all filters and ServletRequestListeners have been called.

Coverage

org.jboss.cdi.tck.tests.context.session.event
SessionScopeEventTest.test()github
da)

An event with the HttpSessionEvent as payload and with qualifier @Initialized(SessionScoped.class) is fired when the session context is initialized.

Coverage

org.jboss.cdi.tck.tests.context.session.event
SessionScopeEventTest.test()github
db)

An event with the HttpSessionEvent as payload and with qualifier @Destroyed(SessionScoped.class) is fired when the session context is destroyed.

Coverage

org.jboss.cdi.tck.tests.context.session.event
SessionScopeEventTest.test()github

Section 6.7.3 - Application context lifecycle

The application scope is active during the service() method of any servlet in the web application, during the doFilter() method of any servlet filter and when the container calls any ServletContextListener, HttpSessionListener, AsyncListener or ServletRequestListener.

aa)

Check service method

Coverage

org.jboss.cdi.tck.tests.context.application
ApplicationContextTest.testApplicationScopeActiveDuringServiceMethod()github
ab)

Check filter.

Coverage

org.jboss.cdi.tck.tests.context.application
ApplicationContextTest.testApplicationScopeActiveDuringDoFilterMethod()github
ac)

Check ServletContextListener.

Coverage

org.jboss.cdi.tck.tests.context.application
ApplicationContextTest.testApplicationScopeActiveDuringServletContextListenerInvocation()github
ad)

Check HttpSessionListener

Coverage

org.jboss.cdi.tck.tests.context.application
ApplicationContextTest.testApplicationScopeActiveDuringHttpSessionListenerInvocation()github
ae)

Check AsyncListener

Coverage

org.jboss.cdi.tck.tests.context.application.async
ApplicationContextAsyncListenerTest.testApplicationContextActiveOnComplete()github
ApplicationContextAsyncListenerTest.testApplicationContextActiveOnTimeout()github
ApplicationContextAsyncListenerTest.testApplicationContextActiveOnError()github
ApplicationContextAsyncListenerTest.testApplicationContextActiveOnStartAsync()github
af)

Check ServletRequestListener

Coverage

org.jboss.cdi.tck.tests.context.application
ApplicationContextTest.testApplicationScopeActiveDuringServletRequestListenerInvocation()github
b)

The application scope is active during any Java EE web service invocation.

Coverage

org.jboss.cdi.tck.tests.context.request.ws
RequestContextTest.testRequestScopeActiveDuringWebServiceInvocation()github

The application scope is also active during any remote method invocation of any EJB, during any asynchronous method invocation of any EJB, during any call to an EJB timeout method and during message delivery to any EJB message-driven bean.

da)

Test remote method invocation

Coverage

org.jboss.cdi.tck.tests.context.application.ejb
ApplicationContextSharedTest.testApplicationScopeActiveDuringRemoteCallToEjb()github
db)

Test asynchronous method invocation

Coverage

org.jboss.cdi.tck.tests.context.application.ejb
ApplicationContextSharedTest.testApplicationScopeActiveDuringAsyncCallToEjb()github
dc)

Test EJB timeout method

Coverage

org.jboss.cdi.tck.tests.context.application.ejb
ApplicationContextSharedTest.testApplicationScopeActiveDuringCallToEjbTimeoutMethod()github
dd)

Test message delivery to any EJB message-driven bean.

Coverage

org.jboss.cdi.tck.tests.context.jms
MessageDrivenBeanContextTest.testRequestScopeActiveDuringMessageDelivery()github

The application scope is active when the disposer method or @PreDestroy callback of any bean with any normal scope other than @ApplicationScoped is called.

dg)

Test disposer method

Coverage

org.jboss.cdi.tck.tests.context.application.disposer
ApplicationContextDisposerTest.testApplicationContextActiveDuringDispose()github
dh)

Test @PreDestroy method

Coverage

org.jboss.cdi.tck.tests.context.application.predestroy
ApplicationContextPreDestroyTest.testApplicationContextActivePreDestroy()github
h)

The application scope is active during @PostConstruct callback of any bean.

Coverage

org.jboss.cdi.tck.tests.context.application.postconstruct
SimpleBeanPostConstructCallbackTest.testSimplePostConstructCallback()github
EagerSingletonPostConstructCallbackTest.testEagerSingletonPostConstructCallback()github
e)A single test needs check *all* these request types

The application context is shared between all servlet requests, asynchronous observer method notifications, web service invocations, EJB remote method invocations, EJB asynchronous method invocations, EJB timeouts and message deliveries to message driven beans that execute within the same application.

Coverage

org.jboss.cdi.tck.tests.context.application
ApplicationContextTest.testApplicationContextSharedBetweenServletRequests()github
ApplicationContextTest.testApplicationContextSharedBetweenJaxRsRequests()github
org.jboss.cdi.tck.tests.context.application.ejb
ApplicationContextSharedTest.testApplicationContextShared()github
f)

The application context is destroyed when the application is shut down.

Coverage

org.jboss.cdi.tck.tests.context.application.destroy
ApplicationContextDestructionTest.testApplicationContextDestroyed()github

An event with qualifier @Initialized(ApplicationScoped.class) is fired when the application context is initialized and an event with qualifier @Destroyed(ApplicationScoped.class) is fired when the application is destroyed.

ga)

The event payload is the ServletContextEvent if the application is a web application deployed to a Servlet container.

Coverage

org.jboss.cdi.tck.tests.context.application.event
ApplicationScopeEventTest.testServletContextInitializedInvoked()github
org.jboss.cdi.tck.tests.deployment.shutdown
ApplicationShutdownLifecycleTest.testShutdown()github
org.jboss.cdi.tck.tests.context.application.event
ApplicationScopeEventMultiWarTest.testDeployment()github
gb)Specification not finished yet

the ??? in ???

Section 6.7.4 - Conversation context lifecycle

The conversation scope is active during all Servlet requests.

a)

Test JSF request.

Coverage

org.jboss.cdi.tck.tests.context.conversation
ClientConversationContextTest.testConversationActiveDuringNonFacesRequest()github
aa)Test required since CDI 1.0 defined conversation for JSF requests only.

Test non-JSF servlet request.

Coverage

org.jboss.cdi.tck.tests.context.conversation.servlet
ServletConversationTest.testTransientConversation()github
ServletConversationTest.testLongRunningConversation()github
ServletConversationTest.testPost()github

An event with qualifier @Initialized(ConversationContext.class) is fired when the conversation context is initialized and an event with qualifier @Destroyed(ConversationScoped.class) is fired when the conversation is destroyed. The event payload is the conversation id if the conversation context is destroyed and is not associated with a current Servlet request, the ServletRequestEvent if the application is a web application deployed to a Servlet container, any java.lang.Object for other types of application.

ba)

An event with the ServletRequestEvent as the payload and with qualifier @Initialized(ConversationContext.class) is fired when the conversation context is initialized.

Coverage

org.jboss.cdi.tck.tests.context.conversation.event
TransientConversationLifecycleEventTest.testLifecycleEventFiredForTransientConversation()github
LongRunningConversationLifecycleEventTest.testLifecycleEventFiredForLongRunningConversation()github
bb)

An event with the ServletRequestEvent as the payload and with qualifier @Destroyed(ConversationContext.class) is fired when the conversation context is destroyed.

Coverage

org.jboss.cdi.tck.tests.context.conversation.event
TransientConversationLifecycleEventTest.testLifecycleEventFiredForTransientConversation()github
LongRunningConversationLifecycleEventTest.testLifecycleEventFiredForLongRunningConversation()github
bc)

An event with the conversation id as the payload and with qualifier @Destroyed(ConversationContext.class) is fired when the conversation context is destroyed and is not associated with a current Servlet request.

Coverage

org.jboss.cdi.tck.tests.context.conversation.event.notattached
DestroyConversationNotAssociatedWithCurrentRequestEventTest.testLifecycleEventFired()github
c)We have no portable way how to test it

Any Servlet request has exactly one associated conversation.

The conversation associated with a Servlet request is determined at the beginning of the request before calling any service() method of any servlet in the web application, calling the doFilter() method of any servlet filter in the web application and before the container calls any ServletRequestListener or AsyncListener in the web application.

da)This may only be tested indirectly

Test service() method of a servlet.

Coverage

org.jboss.cdi.tck.tests.context.conversation.determination
ConversationDeterminationTest.testConversationDetermination()github
db)This may only be tested indirectly

Test doFilter() method of a servlet filter.

Coverage

org.jboss.cdi.tck.tests.context.conversation.determination
ConversationDeterminationTest.testConversationDetermination()github
dc)This may only be tested indirectly

Test ServletRequestListener.

Coverage

org.jboss.cdi.tck.tests.context.conversation.determination
ConversationDeterminationTest.testConversationDetermination()github
dd)This may only be tested indirectly

Test AsyncListener.

Coverage

org.jboss.cdi.tck.tests.context.conversation.determination
ConversationDeterminationTest.testConversationDetermination()github
e)

By default, a conversation is transient.

Coverage

org.jboss.cdi.tck.tests.context.conversation
ClientConversationContextTest.testTransientConversationHasNullId()github
f)

A transient conversation may be marked long-running by calling Conversation.begin()

Coverage

org.jboss.cdi.tck.tests.context.conversation
ClientConversationContextTest.testConversationBeginMakesConversationLongRunning()github
g)

A long-running conversation may be marked transient by calling Conversation.end()

Coverage

org.jboss.cdi.tck.tests.context.conversation
ClientConversationContextTest.testConversationEndMakesConversationTransient()github
ha)

All long-running conversations have a string-valued unique identifier, which may be set by the application when the conversation is marked long-running, or generated by the container

Coverage

org.jboss.cdi.tck.tests.context.conversation
ClientConversationContextTest.testConversationIdMayBeSetByApplication()github
hb)

All long-running conversations have a string-valued unique identifier, which may be set by the application when the conversation is marked long-running, or generated by the container

Coverage

org.jboss.cdi.tck.tests.context.conversation
ClientConversationContextTest.testConversationIdSetByContainerIsUnique()github
ClientConversationContextTest.testConversationIdMayBeSetByContainer()github
j)

If the conversation associated with the current Servlet request is in the transient state at the end of a Servlet request, it is destroyed, and the conversation context is also destroyed.

Coverage

org.jboss.cdi.tck.tests.context.conversation
ClientConversationContextTest.testTransientConversationInstancesDestroyedAtRequestEnd()github
k)

If the conversation associated with the current Servlet request is in the long-running state at the end of a Servlet request, it is not destroyed.

Coverage

org.jboss.cdi.tck.tests.context.conversation
ClientConversationContextTest.testLongRunningConversationInstancesNotDestroyedAtRequestEnd()github
n)

The long-running conversation associated with a request may be propagated to any Servlet request via use of a request parameter named cid containing the unique identifier of the conversation. In this case, the application must manage this request parameter.

Coverage

org.jboss.cdi.tck.tests.context.conversation
ManualCidPropagationTest.testManualCidPropagation()github
l)

The long-running conversation context associated with a request that renders a JSF view is automatically propagated to any faces request (JSF form submission) that originates from that rendered page.

Coverage

org.jboss.cdi.tck.tests.context.conversation
LongRunningConversationPropagatedByFacesContextTest.testConversationPropagated()github
LongRunningConversationPropagatedByFacesContextTest.testConversationPropagatedAjax()github
m)

The long-running conversation context associated with a request that results in a JSF redirect (via a navigation rule) is automatically propagated to the resulting non-faces request, and to any other subsequent request to the same URL. This is accomplished via use of a request parameter named cid containing the unique identifier of the conversation.

Coverage

org.jboss.cdi.tck.tests.context.conversation
LongRunningConversationPropagatedByFacesContextTest.testConversationPropagatedOverRedirect()github

When no conversation is propagated to a Servlet request, or if a request parameter named conversationPropagation has the value none the request is associated with a new transient conversation.

o)

The request is associated with a new transient conversation.

Coverage

org.jboss.cdi.tck.tests.context.conversation
ClientConversationContextTest.testConversationIdSetByContainerIsUnique()github
oa)

Test request parameter named conversationPropagation.

Coverage

org.jboss.cdi.tck.tests.context.conversation
ClientConversationContextTest.testSuppressedConversationPropagation()github
p)

All long-running conversations are scoped to a particular HTTP servlet session and may not cross session boundaries.

Coverage

org.jboss.cdi.tck.tests.context.conversation
ClientConversationContextTest.testConversationsDontCrossSessionBoundary1()github
ClientConversationContextTest.testConversationsDontCrossSessionBoundary2()github
qa)

When the HTTP servlet session is invalidated, all long-running conversation contexts created during the current session are destroyed, after the servlet service() method completes.

Coverage

org.jboss.cdi.tck.tests.context.conversation
InvalidatingSessionDestroysConversationTest.testInvalidatingSessionDestroysConversation()github
org.jboss.cdi.tck.tests.context.conversation.servlet
ServletConversationTest.testInvalidatingSessionDestroysConversation()github
r)In other words, this is unspecified

The container is permitted to arbitrarily destroy any long-running conversation that is associated with no current JSF request, in order to conserve resources

ta)Not required

The conversation timeout, which may be specified by calling Conversation.setTimeout() is a hint to the container that a conversation should not be destroyed if it has been active within the last given interval in milliseconds.

tb)

If the propagated conversation cannot be restored, the container must associate the request with a new transient conversation and throw an exception of type javax.enterprise.context.NonexistentConversationException.

Coverage

org.jboss.cdi.tck.tests.context.conversation
ClientConversationContextTest.testNonexistentConversationExceptionThrown()github
ua)Not testable until CDI-206 is resolved.

The container ensures that a long-running conversation may be associated with at most one request at a time, by blocking or rejecting concurrent requests. If the container rejects a request, it must associate the request with a new transient conversation and throw an exception of type javax.enterprise.context.BusyConversationException.

Coverage

No tests exist for this assertion

Section 6.7.5 - The Conversation interface

The container provides a built-in bean with bean type Conversation, scope @RequestScoped, and qualifier @Default, named javax.enterprise.context.conversation.

iaa)

Test the bean type is correct.

Coverage

org.jboss.cdi.tck.tests.context.conversation
ClientConversationContextTest.testBeanWithRequestScope()github
ib)

Test the scope is correct.

Coverage

org.jboss.cdi.tck.tests.context.conversation
ClientConversationContextTest.testBeanWithRequestScope()github
id)

Test the qualifier is correct.

Coverage

org.jboss.cdi.tck.tests.context.conversation
ClientConversationContextTest.testBeanWithDefaultQualifier()github
ie)

Test the bean name is correct.

Coverage

org.jboss.cdi.tck.tests.context.conversation
ClientConversationContextTest.testBeanWithNameJavaxEnterpriseContextConversation()github
j)

begin() marks the current transient conversation long-running. A conversation identifier may, optionally, be specified. If no conversation identifier is specified, an identifier is generated by the container.

Coverage

org.jboss.cdi.tck.tests.context.conversation
ClientConversationContextTest.testConversationIdMayBeSetByApplication()github
ClientConversationContextTest.testConversationIdMayBeSetByContainer()github
k)

end() marks the current long-running conversation transient.

Coverage

org.jboss.cdi.tck.tests.context.conversation
ClientConversationContextTest.testConversationEndMakesConversationTransient()github
l)

getId() returns the identifier of the current long-running conversation, or a null value if the current conversation is transient.

Coverage

org.jboss.cdi.tck.tests.context.conversation
ClientConversationContextTest.testTransientConversationHasNullId()github
m)

getTimeout() returns the timeout, in milliseconds, of the current conversation.

Coverage

org.jboss.cdi.tck.tests.context.conversation
ClientConversationContextTest.testConversationHasDefaultTimeout()github
ClientConversationContextTest.testSetConversationTimeoutOverride()github
n)

setTimeout() sets the timeout of the current conversation.

Coverage

org.jboss.cdi.tck.tests.context.conversation
ClientConversationContextTest.testSetConversationTimeoutOverride()github
o)

isTransient() returns true if the conversation is marked transient, or false if it is marked long-running.

Coverage

org.jboss.cdi.tck.tests.context.conversation
ClientConversationContextTest.testConversationEndMakesConversationTransient()github
p)

If any method of Conversation is called when the conversation scope is not active, a ContextNotActiveException is thrown.

Coverage

org.jboss.cdi.tck.tests.context.conversation.inactive
InactiveConversationTest.testContextNotActiveExceptionThrown()github
q)

If end() is called, and the current conversation is marked transient, an IllegalStateException is thrown.

Coverage

org.jboss.cdi.tck.tests.context.conversation
ClientConversationContextTest.testEndTransientConversationThrowsException()github
r)

If begin() is called, and the current conversation is already marked long-running, an IllegalStateException is thrown.

Coverage

org.jboss.cdi.tck.tests.context.conversation
ClientConversationContextTest.testBeginAlreadyLongRunningConversationThrowsException()github
s)

If begin() is called with an explicit conversation identifier, and a long-running conversation with that identifier already exists, an IllegalArgumentException is thrown.

Coverage

org.jboss.cdi.tck.tests.context.conversation
ClientConversationContextTest.testBeginConversationWithExplicitIdAlreadyUsedByDifferentConversation()github

Section 7.2 - Container invocations and interception

a0)

When the application invokes a method of a bean via a contextual reference to the bean, as defined in Section 6.5.3, "Contextual reference for a bean", or a business method of a session bean via an EJB remote or local reference, the invocation is treated as a business method invocation.

a1)

Invocations of initializer methods by the container are not business method invocations.

Coverage

org.jboss.cdi.tck.tests.interceptors.invocation
InterceptorInvocationTest.testInitializerMethodsNotIntercepted()github

Invocations of producer, disposer and observer methods by the container are business method invocations are are intercepted by method interceptors and decorators.

ia)

Verify producer methods are intercepted

Coverage

org.jboss.cdi.tck.tests.interceptors.invocation
InterceptorInvocationTest.testProducerMethodsAreIntercepted()github
ib)

Verify producer methods are decorated

Coverage

org.jboss.cdi.tck.tests.decorators.invocation.producer.method
DecoratorInvocationTest.testDecoratorInvocation()github
ic)

Verify disposer methods are intercepted

Coverage

org.jboss.cdi.tck.tests.interceptors.invocation
InterceptorInvocationTest.testDisposerMethodsAreIntercepted()github
id)

Verify disposer methods are decorated

Coverage

org.jboss.cdi.tck.tests.decorators.invocation.producer.method
DecoratorInvocationTest.testDecoratorInvocation()github
ie)

Verify observer methods are intercepted

Coverage

org.jboss.cdi.tck.tests.interceptors.invocation
InterceptorInvocationTest.testObserverMethodsAreIntercepted()github
if)

Verify observer methods are decorated

Coverage

org.jboss.cdi.tck.tests.decorators.invocation.observer
DecoratorInvocationTest.testDecoratorInvocation()github
ig)

Invocation of EJB timer service timeouts by the container are not business method invocations, but are intercepted by interceptors for EJB timeouts.

Coverage

org.jboss.cdi.tck.tests.interceptors.invocation
InterceptorInvocationTest.testTimeoutMethodIntercepted()github
j)

Invocation of lifecycle callbacks by the container are not business method invocations, but are intercepted by interceptors for lifecycle callbacks.

Coverage

org.jboss.cdi.tck.tests.interceptors.invocation
InterceptorInvocationTest.testLifecycleCallbacksAreIntercepted()github

Invocations of interceptors and decorator methods during method or lifecycle callback interception are not business method invocations, and therefore no recursive interception occurs.

ka)

Verify decorators callbacks are not intercepted

Coverage

org.jboss.cdi.tck.tests.decorators.interceptor
DecoratorAndInterceptorTest.testMethodCallbacks()github
kb)

Verify decorators callbacks are not decorated

Coverage

org.jboss.cdi.tck.tests.decorators.interceptor
DecoratorAndInterceptorTest.testMethodCallbacks()github
org.jboss.cdi.tck.tests.decorators.invocation
DecoratorInvocationTest.testChainedDecoratorInvocation()github
kc)

Verify interceptor callbacks are not intercepted

Coverage

org.jboss.cdi.tck.tests.decorators.interceptor
DecoratorAndInterceptorTest.testMethodCallbacks()github
DecoratorAndInterceptorTest.testLifecycleCallbacks()github
kd)

Verify interceptor callbacks are not decorated

Coverage

org.jboss.cdi.tck.tests.decorators.interceptor
DecoratorAndInterceptorTest.testMethodCallbacks()github
DecoratorAndInterceptorTest.testLifecycleCallbacks()github

Invocations of message listener methods of message-driven beans during message delivery are business method invocations.

la)

Verify message listener methods are intercepted

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.enterprise.jms
MessageDrivenBeanInterceptorInvocationTest.testMessageDrivenBeanMethodIntercepted()github
m)

Invocations of methods declared by java.lang.Object are not business method invocations.

Coverage

org.jboss.cdi.tck.tests.interceptors.invocation
InterceptorInvocationTest.testObjectMethodsAreNotIntercepted()github

If, and only if, the invocation is a business method invocation it passes through method interceptors and decorators, and in the case of a session bean, it is subject to EJB services such a declarative transaction management, concurrency, security and asynchronicity, as defined by the EJB specification.

a)

Verify that a managed bean's business methods are intercepted

Coverage

org.jboss.cdi.tck.tests.interceptors.invocation
InterceptorInvocationTest.testManagedBeanIsIntercepted()github
b)

Verify that a managed bean's business methods are decorated

Coverage

org.jboss.cdi.tck.tests.decorators.invocation
DecoratorInvocationTest.testDecoratorInvocation()github
c)

Verify that a session bean's business methods are intercepted

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.enterprise.simpleInterception
SessionBeanInterceptorDefinitionTest.testSessionBeanIsIntercepted()github
d)

Verify that a session bean's business methods are decorated

Coverage

org.jboss.cdi.tck.tests.decorators.invocation
EJBDecoratorInvocationTest.testEJBDecoratorInvocation()github
org.jboss.cdi.tck.tests.decorators.invocation.enterprise
EnterpriseDecoratorInvocationTest.testContextualDecorated()github
f)This is tested by the EJB TCK

Verify that a session bean's business methods receive EJB services

h)

Verify that a non-contextual session bean's business methods are intercepted

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.enterprise.nonContextualReference
SessionBeanInterceptorOnNonContextualEjbReferenceTest.testNonContextualSessionBeanReferenceIsIntercepted()github
i)

Verify that a non-contextual session bean's business methods are decorated

Coverage

org.jboss.cdi.tck.tests.decorators.invocation.enterprise
EnterpriseDecoratorInvocationTest.testNonContextualDecorated()github
g)

If the invocation is not a business method invocation, it is treated as a normal Java method call and is not intercepted by the container.

Coverage

org.jboss.cdi.tck.tests.interceptors.invocation
InterceptorInvocationTest.testObjectMethodsAreNotIntercepted()github

Section 7.3.1 - Lifecycle of managed beans

aa)

When the create() method of the Bean object that represents a managed bean is called, the container obtains an instance of the bean, as defined by the Managed Beans specification, calling the bean constructor as defined by Section 5.5.1, "Injection using the bean constructor", and performing dependency injection as defined in Section 5.5.2, "Injection of fields and initializer methods".

Coverage

org.jboss.cdi.tck.tests.implementation.simple.lifecycle
SimpleBeanLifecycleTest.testBeanCreateInjectsDependenciesAndInvokesInitializerToInstantiateInstance()github
SimpleBeanLifecycleTest.testCreateInjectsFieldsDeclaredInJava()github
SimpleBeanLifecycleTest.testPostConstructPreDestroy()github
ba)

When the destroy() method is called, the container destroys the instance, as defined by the Managed Beans specification, and any dependent objects, as defined in Section 5.5.3, "Destruction of dependent objects".

Coverage

org.jboss.cdi.tck.tests.implementation.simple.lifecycle
SimpleBeanLifecycleTest.testPostConstructPreDestroy()github
SimpleBeanLifecycleTest.testContextualDestroyDisposesWhenNecessary()github

Section 7.3.2 - Lifecycle of stateful session beans

aa)It's not possible to test container-specific internal local reference that is not directly exposed to the application.

When the create() method of a Bean object that represents a stateful session bean that is called, the container creates and returns a container-specific internal local reference to a new session bean instance. The reference must be passivation capable. This reference is not directly exposed to the application.

bb)

Before injecting or returning a contextual instance to the application, the container transforms its internal reference into an object that implements the bean types expected by the application and delegates method invocations to the underlying stateful session bean instance. This object must be passivation capable.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.lifecycle
EnterpriseBeanLifecycleTest.testCreateSFSB()github
bc)

When the destroy() method is called, and if the underlying EJB was not already removed by direct invocation of a remove method by the application, the container removes the stateful session bean. The @PreDestroy callback must be invoked by the container.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.lifecycle
EnterpriseBeanLifecycleTest.testDestroyRemovesSFSB()github
EnterpriseBeanLifecycleTest.testRemovedEjbIgnored()github

Section 7.3.3 - Lifecycle of stateless session and singleton beans

a)It's not possible to test container-specific internal local reference that is not directly exposed to the application.

When the create() method of a Bean object that represents a stateless session or singleton session bean is called, the container creates and returns a container-specific internal local reference to the session bean. This reference is not directly exposed to the application.

b)

Before injecting or returning a contextual instance to the application, the container transforms its internal reference into an object that implements the bean types expected by the application and delegates method invocations to the underlying session bean. This object must be passivation capable.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.lifecycle
EnterpriseBeanLifecycleTest.testCreateSLSB()github
c)

When the destroy() method is called, the container simply discards this internal reference.

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.lifecycle
EnterpriseBeanLifecycleTest.testDestroyRemovesSFSB()github

Section 7.3.4 - Lifecycle of producer methods

ea)

When the create() method of a Bean object that represents a producer method is called, the container must invoke the producer method as defined by Section 5.5.4, "Invocation of producer or disposer methods". The return value of the producer method, after method interception completes, is the new contextual instance to be returned by Bean.create().

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.lifecycle
ProducerMethodLifecycleTest.testProducerMethodBeanCreate()github
ProducerMethodLifecycleTest.testProducerMethodInvokedOnCreate()github
k)

If the producer method returns a null value and the producer method bean has the scope @Dependent, the create() method returns a null value.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.lifecycle
ProducerMethodLifecycleTest.testCreateReturnsNullIfProducerDoesAndDependent()github
l)

If the producer method returns a null value, and the scope of the producer method is not @Dependent, the create() method throws an IllegalProductException.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.lifecycle
ProducerMethodLifecycleTest.testCreateFailsIfProducerReturnsNullAndNotDependent()github
ma)

When the destroy() method is called, and if there is a disposer method for this producer method, the container must invoke the disposer method as defined by Section 5.5.4, "Invocation of producer or disposer methods", passing the instance given to destroy() to the disposed parameter.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.lifecycle
ProducerMethodLifecycleTest.testProducerMethodBeanDestroy()github
r)

Finally, the container destroys dependent objects, as defined in Section 5.5.3, "Destruction of dependent objects".

Coverage

org.jboss.cdi.tck.tests.implementation.producer.method.lifecycle
ProducerMethodLifecycleTest.testProducerMethodBeanDestroy()github

Section 7.3.5 - Lifecycle of producer fields

ga)

When the create() method of a Bean object that represents a producer field is called, the container must access the producer field as defined by Section 5.5.5, "Access to producer field values" to obtain the current value of the field. The value of the producer field is the new contextual instance to be returned by Bean.create().

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.lifecycle
ProducerFieldLifecycleTest.testProducerFieldBeanCreate()github
m)

If the producer field contains a null value and the producer field bean has the scope @Dependent, the create() method returns a null value.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.lifecycle
ProducerFieldLifecycleTest.testProducerFieldReturnsNullIsDependent()github
n)

If the producer field contains a null value, and the scope of the producer method is not @Dependent, the create() method throws an IllegalProductException.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.lifecycle
ProducerFieldLifecycleTest.testProducerFieldForNullValueNotDependent()github
ProducerFieldLifecycleTest.testProducerFieldReturnsNullIsNotDependent()github
o)

When the destroy() method is called, and if there is a disposer method for this producer field, the container must invoke the disposer method as defined by Section 5.5.4, "Invocation of producer or disposer methods", passing the instance given to destroy() to the disposed parameter.

Coverage

org.jboss.cdi.tck.tests.implementation.producer.field.lifecycle
ProducerFieldLifecycleTest.testProducerFieldBeanDestroy()github
org.jboss.cdi.tck.tests.implementation.disposal.method.definition
DisposalMethodDefinitionTest.testDisposalMethodCalledForProducerField()github

Section 7.3.6 - Lifecycle of resources

When the create() method of a Bean object that represents a resource is called, the container creates and returns a container-specific internal reference to the Java EE component environment resource, entity manager, entity manager factory, remote EJB instance or web service reference. This reference is not directly exposed to the application.

la)

Check Java EE component environment resource

Coverage

org.jboss.cdi.tck.tests.implementation.simple.resource.resource
InjectionOfResourceTest.testProduceResourceProxy()github
org.jboss.cdi.tck.tests.implementation.simple.resource.env
EnvInjectionTest.testProduceEnvProxy()github
lb)

Check Entity Manager

Coverage

org.jboss.cdi.tck.tests.implementation.simple.resource.persistenceContext
PersistenceContextInjectionTest.testInjectionOfPersistenceContext()github
lc)

Check Entity Manager Factory

Coverage

org.jboss.cdi.tck.tests.implementation.simple.resource.persistenceContext
PersistenceContextInjectionTest.testInjectionOfPersistenceUnit()github
PersistenceContextInjectionTest.testPassivationOfPersistenceUnit()github
ld)

Check Remote EJB instance

Coverage

org.jboss.cdi.tck.tests.implementation.simple.resource.ejb
EjbInjectionTest.testInjectionOfEjbs()github
le)

Check Web Service Reference

Coverage

No tests exist for this assertion

Before injecting or returning a contextual instance to the application, the container transforms its internal reference into an object that implements the bean types expected by the application and delegates method invocations to the underlying resource, entity manager, entity manager factory, remote EJB instance or web service reference. This object must be passivation capable.

ma)

Check delegations to underlying Java EE component environment resource

Coverage

org.jboss.cdi.tck.tests.implementation.simple.resource.resource
InjectionOfResourceTest.testProduceResourceProxy()github
org.jboss.cdi.tck.tests.implementation.simple.resource.env
EnvInjectionTest.testProduceEnvProxy()github
mb)

Check injected Java EE component environment resource is passivation capable

Coverage

org.jboss.cdi.tck.tests.implementation.simple.resource.resource
InjectionOfResourceTest.testPassivatingResource()github
mc)

Check delegations to underlying Entity Manager

Coverage

org.jboss.cdi.tck.tests.implementation.simple.resource.persistenceContext
PersistenceContextInjectionTest.testInjectionOfPersistenceContext()github
md)

Check injected Entity Manager is passivation capable

Coverage

org.jboss.cdi.tck.tests.implementation.simple.resource.persistenceContext
PersistenceContextInjectionTest.testPassivationOfPersistenceContext()github
me)

Check delegations to Entity Manager Factory

Coverage

org.jboss.cdi.tck.tests.implementation.simple.resource.persistenceContext
PersistenceContextInjectionTest.testInjectionOfPersistenceUnit()github
mf)

Check injected Entity Manager Factory is passivation capable

Coverage

org.jboss.cdi.tck.tests.implementation.simple.resource.persistenceContext
PersistenceContextInjectionTest.testPassivationOfPersistenceUnit()github
mg)

Check delegations to underlying Remote EJB instance

Coverage

org.jboss.cdi.tck.tests.implementation.simple.resource.ejb
EjbInjectionTest.testInjectionOfEjbs()github
mh)

Check injected Remote EJB instance is passivation capable

Coverage

org.jboss.cdi.tck.tests.implementation.simple.resource.ejb
EjbInjectionTest.testPassivationOfEjbs()github
mj)

Check delegations to underlying Web Service Reference

Coverage

No tests exist for this assertion

mk)

Check injected Web Service Reference is passivation capable

Coverage

No tests exist for this assertion

The container must perform ordinary Java EE component environment injection upon any non-static field that functions as a resource declaration, as defined by the Java EE platform and Common Annotations for the Java platform specifications.

o)

Check @Resource injection

Coverage

org.jboss.cdi.tck.tests.implementation.simple.resource.resource
InjectionOfResourceTest.testProduceResourceProxy()github
org.jboss.cdi.tck.tests.implementation.simple.resource.env
EnvInjectionTest.testProduceEnvProxy()github
p)Defines non-portable behavior

The container is not required to perform Java EE component environment injection upon a static field. Portable applications should not rely upon the value of a static field that functions as a resource declaration.

q)

References to EJBs and web services are always dependent scoped and a new instance must be obtained for every injection performed.

Coverage

No tests exist for this assertion

r)Verify that this assertion is testable.

For an entity manager associated with a resource definition, it must behave as though it were injected directly using @PersistencContext.

Coverage

No tests exist for this assertion

s)

When the destroy() method of a bean which represents a remote stateful EJB reference is called, the container will not automatically destroy the EJB reference.

Coverage

No tests exist for this assertion

Section 8 - Decorators

a)Doesn't specify an error

Decorators may be associated with any managed bean that is not itself an interceptor or decorator or with any EJB session bean.

b)

Decorators are not applied to the return value of a producer method or the current value of a producer field.

Coverage

org.jboss.cdi.tck.tests.decorators.definition.producer
DecoratorNotAppliedToResultOfProducerTest.testDecoratorNotAppliedToResultOfProducerMethod()github
DecoratorNotAppliedToResultOfProducerTest.testDecoratorNotAppliedToResultOfProducerField()github
c)

A decorator instance is a dependent object of the object it decorates.

Coverage

org.jboss.cdi.tck.tests.decorators.definition.lifecycle
DecoratorInstanceIsDependentObjectTest.testDecoratorInstanceIsDependentObject()github

Section 8.1 - Decorator beans

a)Statement of intent

A decorator is a managed bean.

b)

The set of decorated types of a decorator includes all bean types of the managed bean which are Java interfaces, except for java.io.Serializable.

Coverage

org.jboss.cdi.tck.tests.decorators.definition
DecoratorDefinitionTest.testDecoratedTypes()github
c)

The decorator bean class and its superclasses are not decorated types of the decorator.

Coverage

org.jboss.cdi.tck.tests.decorators.definition
DecoratorDefinitionTest.testDecoratedTypes()github
d)

The decorator class may be abstract.

Coverage

org.jboss.cdi.tck.tests.decorators.definition
DecoratorDefinitionTest.testDecoratorIsManagedBean()github
DecoratorDefinitionTest.testAbstractDecoratorNotImplementingMethodOfDecoratedType()github
org.jboss.cdi.tck.tests.decorators.invocation.enterprise
EnterpriseDecoratorInvocationTest.testContextualDecorated()github
EnterpriseDecoratorInvocationTest.testNonContextualDecorated()github
e)

If the set of decorated types of a decorator is empty, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.decorators.definition.broken.nodecoratedtypes
DecoratorWithNoDecoratedTypes2Test.testDeploymentFails()github
DecoratorWithNoDecoratedTypes1Test.testDeploymentFails()github
DecoratorWithNoDecoratedTypes3Test.testDeploymentFails()github
f)

Decorators of a session bean must comply with the bean provider programming restrictions defined by the EJB specification.

Coverage

No tests exist for this assertion

g)

Decorators of a stateful session bean must comply with the rules for instance passivation and conversational state defined by the EJB specification.

Coverage

No tests exist for this assertion

Section 8.1.1 - Declaring a decorator

a)

A decorator is declared by annotating the bean class with the @javax.decorator.Decorator stereotype.

Coverage

org.jboss.cdi.tck.tests.decorators.definition
DecoratorDefinitionTest.testDecoratorIsManagedBean()github
org.jboss.cdi.tck.tests.decorators.invocation.enterprise
EnterpriseDecoratorInvocationTest.testContextualDecorated()github
EnterpriseDecoratorInvocationTest.testNonContextualDecorated()github

Section 8.1.2 - Decorator delegate injection points

a)

All decorators have a delegate injection point. A delegate injection point is an injection point of the bean class. The type and qualifiers of the injection point are called the delegate type and delegate qualifiers. The decorator applies to beans that are assignable to the delegate injection point. The delegate injection point must be be declared by annotating the injection point with the annotation @javax.decorator.Delegate.

Coverage

org.jboss.cdi.tck.tests.decorators.definition
DecoratorDefinitionTest.testDelegateInjectionPoint()github

A decorator must have exactly one delegate injection point. If a decorator has more than one delegate injection point, or does not have a delegate injection point, the container automatically detects the problem and treats it as a definition error.

ca)

Test with more than one delegate injection point.

Coverage

org.jboss.cdi.tck.tests.decorators.definition.broken.multipleDelegateInjectionPoints
MultipleDelegateInjectionPointsTest.testMultipleDelegateInjectionPoints()github
org.jboss.cdi.tck.tests.decorators.custom.broken.toomanydelegateinjectionpoints
CustomDecoratorWithTooManyDelegateInjectionPointsTest.testDeploymentFails()github
cb)

Test a decorator without a delegate injection point.

Coverage

org.jboss.cdi.tck.tests.decorators.definition.broken.noDelegateInjectionPoints
NoDelegateInjectionPointsTest.testNoDelegateInjectionPoints()github
org.jboss.cdi.tck.tests.decorators.custom.broken.nodelegateinjectionpoint
CustomDecoratorWithNoDelegateInjectionPointTest.testDeploymentFails()github

The delegate injection point must be an injected field, initializer method parameter or bean constructor method parameter. If an injection point that is not an injected field, initializer method parameter or bean constructor method parameter is annotated @Delegate, the container automatically detects the problem and treats it as a definition error.

cc)

Check an injected field is ok

Coverage

org.jboss.cdi.tck.tests.decorators.definition.inject.delegateField
DelegateFieldInjectionPointTest.testDecoratorDelegateInjectionPoints()github
org.jboss.cdi.tck.tests.decorators.invocation.enterprise
EnterpriseDecoratorInvocationTest.testContextualDecorated()github
cd)

Check an initializer method parameter is ok

Coverage

org.jboss.cdi.tck.tests.decorators.definition.inject.delegateInitializerMethod
DelegateInjectionPointTest.testDecoratorDelegateInjectionPoints()github
ce)

Check a bean constructor method parameter is ok

Coverage

org.jboss.cdi.tck.tests.decorators.definition.inject.delegateConstructor
DelegateInjectionPointTest.testDecoratorDelegateInjectionPoints()github
cf)

Check that a producer method parameter is not ok

Coverage

org.jboss.cdi.tck.tests.decorators.definition.inject.broken.delegateProducerMethod
DelegateInjectionPointTest.testDecoratorDelegateInjectionPoints()github
cg)

If a bean class that is not a decorator has an injection point annotated @Delegate, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.decorators.definition.broken.nonDecoratorWithDecorates
NonDecoratorWithDecoratesTest.testNonDecoratorWithDecoratesAnnotationNotOK()github
f)

The container must inject a delegate object to the delegate injection point. The delegate object implements the delegate type and delegates method invocations to the remaining uninvoked decorators and eventually to the bean. When the container calls a decorator during business method interception, the decorator may invoke any method of the delegate object.

Coverage

org.jboss.cdi.tck.tests.decorators.invocation
DecoratorInvocationTest.testDecoratorInvocation()github
DecoratorInvocationTest.testChainedDecoratorInvocation()github
g)

If a decorator invokes the delegate object at any other time, the invoked method throws an IllegalStateException.

Coverage

org.jboss.cdi.tck.tests.decorators.invocation
DecoratorInvocationTest.testDecoratorInvokesDelegateMethodOutsideOfBusinessMethodInterception()github

Section 8.1.3 - Decorated types of a decorator

a)

The delegate type of a decorator must implement or extend every decorated type (with exactly the same type parameters). If the delegate type does not implement or extend a decorated type of the decorator (or specifies different type parameters), the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.decorators.definition.broken.notAllDecoratedTypesImplemented
NotAllDecoratedTypesImplementedTest.testNotAllDecoratedTypesImplemented()github
org.jboss.cdi.tck.tests.decorators.definition.types
DelegateTypeImplementsParameterizedDecoratedTypeTest.testDelegateTypeIsValid()github
org.jboss.cdi.tck.tests.decorators.definition.broken.notAllDecoratedTypesImplemented.parameterized
TypeParametersNotTheSameTest.testDeploymentFails()github
ab)

If a decorated type is a parameterized type and the delegate type does not have exactly the same type parameters as the decorated type, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.decorators.definition.broken.parameterizedTypesWithDifferentTypeParameters
DifferentTypeParametersTest.testTypeParametersOnDecoratedTypeAndDelegateTypeDoNotMatch()github
b)

A decorator is not required to implement the delegate type.

Coverage

org.jboss.cdi.tck.tests.decorators.definition
DecoratorDefinitionTest.testDecoratorDoesNotImplementDelegateType()github
c)

A decorator may be an abstract Java class, and is not required to implement every method of every decorated type.

Coverage

org.jboss.cdi.tck.tests.decorators.definition
DecoratorDefinitionTest.testDecoratorIsManagedBean()github
DecoratorDefinitionTest.testAbstractDecoratorNotImplementingMethodOfDecoratedType()github
ca)

Whenever the decorator does not implement a method of the decorated type, the container will provide an implicit implementation that calls the method on the delegate.

Coverage

org.jboss.cdi.tck.tests.decorators.definition
DecoratorDefinitionTest.testAbstractDecoratorNotImplementingMethodOfDecoratedType()github
cb)

If a decorator has abstract methods that are not declared by a decorated type, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.decorators.definition.broken.invalidAbstractMethodOnDecorator
DecoratorWithInvalidAbstractMethodTest.testAbstractMethodsNotDeclaredByDecoratedTypeNotOk()github
d)

The decorator intercepts every method which is declared by a decorated type of the decorator and is implemented by the bean class of the decorator.

Coverage

org.jboss.cdi.tck.tests.decorators.invocation
DecoratorInvocationTest.testDecoratorInvocation()github
DecoratorInvocationTest.testChainedDecoratorInvocation()github

Section 8.2 - Decorator enablement and ordering

aa)This is a statement of intent

Decorators may be enabled for an application, or enabled only for a particular bean archive.

The following assertion is not made explicitly by the spec, however it is implied ab)

By default, a bean archive has no enabled decorators.

Coverage

org.jboss.cdi.tck.tests.decorators.definition
DecoratorDefinitionTest.testNonEnabledDecoratorNotResolved()github
b)

A decorator may be enabled for the entire application by listing its class, along with a priority attribute, under the <decorators> element of the beans.xml file of the bean archive which contains the decorator class.

Coverage

org.jboss.cdi.tck.tests.decorators.ordering.global
GlobalDecoratorOrderingTest.testDecoratorsInWebInfClasses()github
c)

A decorator may be enabled for a bean archive by listing its class under the <decorators> element of the beans.xml file of the bean archive.

Coverage

org.jboss.cdi.tck.tests.deployment.packaging.war.modules
WebArchiveModulesTest.testDecoratorAndCrossModuleEventObserver()github
org.jboss.cdi.tck.tests.decorators.invocation.enterprise
EnterpriseDecoratorInvocationTest.testContextualDecorated()github
org.jboss.cdi.tck.tests.decorators.ordering.global
GlobalDecoratorOrderingTest.testDecoratorsInWebInfClasses()github
d)

A decorator enabled for an application may be disabled for a bean archive by listing its class, along with an enabled flag, under the <decorators> element of the beans.xml file of the bean archive.

Coverage

org.jboss.cdi.tck.tests.decorators.ordering.global
GlobalDecoratorOrderingTest.testDecoratorsInWebInfClasses()github
e)

A decorator may be given a default priority, but not enabled by listing its class, along with a disabled flag and the priority attribute, under the <decorators> element of the beans.xml file of the bean archive which contains the decorator class.

Coverage

org.jboss.cdi.tck.tests.decorators.ordering.global
GlobalDecoratorOrderingTest.testDecoratorsInWebInfClasses()github
f)

A decorator with a default priority may be enabled for a bean archive by listing its class, along with an enabled flag, under the <decorators> element of the beans.xml file of the bean archive.

Coverage

org.jboss.cdi.tck.tests.decorators.ordering.global
GlobalDecoratorOrderingTest.testDecoratorsInWebInfClasses()github
g)

The priority of the decorator declaration, defined in Section 2.9, "Priority ordering", determines the default decorator ordering for the application. The order of the decorator declarations for a bean archive overrides the default decorator order. If the set of decorators enabled for the application and the set of decorators enabled for a bean archive are disjoint, then the first decorator enabled for the bean archive is given a priority of 1000. Decorators which occur earlier in the list are called first.

Coverage

org.jboss.cdi.tck.tests.decorators.definition
DecoratorDefinitionTest.testDecoratorOrdering()github
org.jboss.cdi.tck.tests.decorators.invocation.enterprise
EnterpriseDecoratorInvocationTest.testContextualDecorated()github

Each child <class> element must specify the name of a decorator bean class. If there is no class with the specified name, or if the class with the specified name is not a decorator bean class, the container automatically detects the problem and treats it as a deployment problem.

ha)

Test with a nonexistent class name.

Coverage

org.jboss.cdi.tck.tests.decorators.definition.broken.nonExistantClassInBeansXml
NonExistantDecoratorClassInBeansXmlTest.testNonExistantDecoratorClassInBeansXmlNotOK()github
hb)

Test with a non-decorator class.

Coverage

org.jboss.cdi.tck.tests.decorators.definition.broken.enabledDecoratorIsNotDecorator
EnabledDecoratorNotADecoratorTest.testEnabledDecoratorNotADecoratorTest()github
hc)

If the same class is listed twice under the <decorators> element, the container automatically detects the problem and treats it as a deployment problem.

Coverage

org.jboss.cdi.tck.tests.decorators.definition.broken.decoratorListedTwiceInBeansXml
DecoratorListedTwiceInBeansXmlTest.testDecoratorListedTwiceInBeansXmlNotOK()github
i)

Decorators are called after interceptors.

Coverage

org.jboss.cdi.tck.tests.decorators.interceptor
DecoratorAndInterceptorTest.testMethodCallbacks()github
org.jboss.cdi.tck.tests.decorators.invocation.enterprise
EnterpriseDecoratorInvocationTest.testContextualDecorated()github

Section 8.3 - Decorator resolution

aa)

The process of matching decorators to a certain bean is called decorator resolution. A decorator is bound to a bean if the bean is assignable to the delegate injection point according to the rules defined in Section 5.2, "Typesafe resolution", and the decorator is enabled in the bean archive containing the bean.

Coverage

org.jboss.cdi.tck.tests.decorators.definition
DecoratorDefinitionTest.testDecoratorIsManagedBean()github
DecoratorDefinitionTest.testDecoratorOrdering()github
org.jboss.cdi.tck.tests.deployment.packaging.war.modules
WebArchiveModulesTest.testDecoratorAndCrossModuleEventObserver()github
org.jboss.cdi.tck.tests.decorators.builtin.conversation
BuiltinConversationDecoratorTest.testDecoratorIsResolved()github
org.jboss.cdi.tck.tests.decorators.builtin.http.session
BuiltinHttpSessionDecoratorTest.testDecoratorIsResolved()github
org.jboss.cdi.tck.tests.decorators.builtin.event
BuiltinEventDecoratorTest.testDecoratorIsResolved()github
ab)

If a decorator matches a managed bean, and the managed bean class is declared final, the container automatically detects the problem and treats it as a deployment problem.

Coverage

org.jboss.cdi.tck.tests.decorators.definition.broken.finalBeanClass
FinalBeanClassTest.testAppliesToFinalManagedBeanClass()github
org.jboss.cdi.tck.tests.decorators.custom.broken.finalBeanClass
CustomDecoratorMatchingBeanWithFinalClassTest.testCustomDecoratorDecoratingFinalBean()github
ac)

If a decorator matches a managed bean with a non-static, non-private, final method, and the decorator also implements that method, the container automatically detects the problem and treats it as a deployment problem.

Coverage

org.jboss.cdi.tck.tests.decorators.definition.broken.finalBeanMethod
FinalBeanMethodTest.testAppliesToFinalMethodOnManagedBeanClass()github
b)

For a custom implementation of the Decorator interface defined in Section 11.1.1, "The Decorator interface", the container calls getDelegateType(), getDelegateQualifiers() and getDecoratedTypes() to determine the delegate type and qualifiers and decorated types of the decorator.

Coverage

org.jboss.cdi.tck.tests.decorators.custom
CustomDecoratorTest.testCustomImplementationOfDecoratorInterface()github

Section 8.3.1 - Assignability of raw and parameterized types for delegate injection points

A raw bean type is considered assignable to a parameterized delegate type if the raw types are identical and all type parameters of the delegate type are either unbounded type variables or java.lang.Object.

aa)

Check all type parameters are unbounded type variables

Coverage

org.jboss.cdi.tck.tests.decorators.resolution
DecoratorResolutionTest.testUnboundedTypeVariables()github
ab)

Check all type parameters are Object

Coverage

org.jboss.cdi.tck.tests.decorators.resolution
DecoratorResolutionTest.testObject()github
ac)

Check mix

Coverage

org.jboss.cdi.tck.tests.decorators.resolution
DecoratorResolutionTest.testUnboundedTypeVariablesAndObject()github

A parameterized bean type is considered assignable to a parameterized delegate type if they have identical raw type and for each parameter: the delegate type parameter and the bean type parameter are actual types with identical raw type, and, if the type is parameterized, the bean type parameter is assignable to the delegate type parameter according to these rules, or the delegate type parameter is a wildcard, the bean type parameter is an actual type and the actual type is assignable to the upper bound, if any, of the wildcard and assignable from the lower bound, if any, of the wildcard, or the delegate type parameter is a wildcard, the bean type parameter is a type variable and the upper bound of the type variable is assignable to the upper bound, if any, of the wildcard and assignable from the lower bound, if any, of the wildcard, or the delegate type parameter and the bean type parameter are both type variables and the upper bound of the bean type parameter is assignable to the upper bound, if any, of the delegate type parameter, or the delegate type parameter is a type variable, the bean type parameter is an actual type, and the actual type is assignable to the upper bound, if any, of the type variable.

c)

Check both have identical type parameters

Coverage

org.jboss.cdi.tck.tests.decorators.resolution
DecoratorResolutionTest.testIdenticalTypeParamerters()github
d)

Check nested identical type parameters

Coverage

org.jboss.cdi.tck.tests.decorators.resolution
DecoratorResolutionTest.testNestedIdenticalTypeParamerters()github
e)

Check delegate type parameter is a wildcard, the bean type parameter is an actual type and the actual type is assignable to the upper bound of the wildcard and assignable from the lower bound of the wildcard

Coverage

org.jboss.cdi.tck.tests.decorators.resolution
DecoratorResolutionTest.testDelegateWildcardBeanActualType()github
f)

Check delegate type parameter is a wildcard, the bean type parameter is a type variable and the upper bound of the type variable is assignable to the upper bound of the wildcard and assignable from the lower bound of the wildcard

Coverage

org.jboss.cdi.tck.tests.decorators.resolution
DecoratorResolutionTest.testDelegateWildcardBeanTypeVariable()github
g)

Check the delegate type parameter and the bean type parameter are both type variables and the upper bound of the bean type parameter is assignable to the upper bound of the delegate type parameter

Coverage

org.jboss.cdi.tck.tests.decorators.resolution
DecoratorResolutionTest.testDelegateTypeVariableBeanTypeVariable()github
h)

Check the delegate type parameter is a type variable, the bean type parameter is an actual type, and the actual type is as- signable to the upper bound of the type variable

Coverage

org.jboss.cdi.tck.tests.decorators.resolution
DecoratorResolutionTest.testDelegateTypeVariableBeanActualType()github

Section 8.4 - Decorator invocation

Whenever a business method is invoked on an instance of a bean with decorators, the container intercepts the business method invocation and, after processing all interceptors of the method, invokes decorators of the bean. The container searches for the first decorator of the instance that implements the method that is being invoked as a business method. If such decorator exists, the container calls the method of the decorator.

aa)

Test decorator of managed bean is called.

Coverage

org.jboss.cdi.tck.tests.decorators.invocation
DecoratorInvocationTest.testDecoratorInvocation()github
ab)

Test decorator of session bean is called .

Coverage

org.jboss.cdi.tck.tests.decorators.invocation
EJBDecoratorInvocationTest.testEJBDecoratorInvocation()github
aca)

Test injected Event

Coverage

org.jboss.cdi.tck.tests.decorators.builtin.event.complex
ComplexEventDecoratorTest.testOrderedEvents()github
org.jboss.cdi.tck.tests.decorators.builtin.event
BuiltinEventDecoratorTest.testDecoratorIsResolved()github
BuiltinEventDecoratorTest.testDecoratorIsInvoked()github
BuiltinEventDecoratorTest.testMultipleDecorators()github
acb)

Test injected Instance

Coverage

org.jboss.cdi.tck.tests.decorators.builtin.instance
BuiltinInstanceDecoratorTest.testDecoratorIsResolved()github
BuiltinInstanceDecoratorTest.testDecoratorIsInvoked()github
ach)

Test injected Conversation

Coverage

org.jboss.cdi.tck.tests.decorators.builtin.conversation
BuiltinConversationDecoratorTest.testDecoratorIsResolved()github
BuiltinConversationDecoratorTest.testDecoratorIsInvoked()github
aci)

Test injected HttpServletRequest

Coverage

org.jboss.cdi.tck.tests.decorators.builtin.http.request
BuiltinHttpServletRequestDecoratorTest.testDecoratorIsResolved()github
BuiltinHttpServletRequestDecoratorTest.testDecoratorIsInvoked()github
acj)

Test injected HttpSession

Coverage

org.jboss.cdi.tck.tests.decorators.builtin.http.session
BuiltinHttpSessionDecoratorTest.testDecoratorIsResolved()github
BuiltinHttpSessionDecoratorTest.testDecoratorIsInvoked()github
ack)

Test injected ServletContext

Coverage

org.jboss.cdi.tck.tests.decorators.builtin.http.servletcontext
BuiltinServletContextDecoratorTest.testDecoratorIsResolved()github
BuiltinServletContextDecoratorTest.testDecoratorIsInvoked()github
acl)

Test injected InjectionPoint

Coverage

org.jboss.cdi.tck.tests.decorators.builtin.injectionpoint
BuiltinInjectionPointDecoratorTest.testDecoratorIsResolved()github
BuiltinInjectionPointDecoratorTest.testDecoratorInvoked()github
acm)

Test injected Principal

Coverage

org.jboss.cdi.tck.tests.decorators.builtin.principal
BuiltinPrincipalDecoratorTest.testDecoratorIsResolved()github
BuiltinPrincipalDecoratorTest.testDecoratorInvoked()github
acn)

Test injected UserTransaction

Coverage

org.jboss.cdi.tck.tests.decorators.builtin.transaction
BuiltinUserTransactionDecoratorTest.testUserTransactionDecorated()github
b)

If no such decorator exists, the container invokes the business method of the intercepted instance.

Coverage

org.jboss.cdi.tck.tests.decorators.invocation
DecoratorInvocationTest.testDecoratorInvocation()github
d)

When any decorator is invoked by the container, it may in turn invoke a method of the delegate. The container intercepts the delegate invocation and searches for the first decorator of the instance such that the decorator occurs after the decorator invoking the delegate, and the decorator implements the method that is being invoked upon the delegate.

Coverage

org.jboss.cdi.tck.tests.decorators.invocation
DecoratorInvocationTest.testChainedDecoratorInvocation()github
e)

If no such decorator exists, the container invokes the business method of the intercepted instance.

Coverage

org.jboss.cdi.tck.tests.decorators.invocation
DecoratorInvocationTest.testChainedDecoratorInvocation()github
f)

Otherwise, the container calls the method of the decorator.

Coverage

org.jboss.cdi.tck.tests.decorators.invocation
DecoratorInvocationTest.testChainedDecoratorInvocation()github

Section 9.1 - Interceptor binding types

a)

An interceptor binding type is a Java annotation defined as @Target({TYPE, METHOD}) or @Target(TYPE) and @Retention(RUNTIME).

Coverage

org.jboss.cdi.tck.tests.interceptors.definition
InterceptorDefinitionTest.testInterceptorBindingAnnotation()github
b)

An interceptor binding type may be declared by specifying the @javax.interceptor.InterceptorBinding meta-annotation.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition
InterceptorDefinitionTest.testInterceptorBindingAnnotation()github
c)

Multiple interceptors may be bound to the same interceptor binding type or types.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition
InterceptorDefinitionTest.testInterceptorBindingAnnotation()github

Section 9.1.1 - Interceptor binding types with additional interceptor bindings

a)

An interceptor binding type may declare other interceptor bindings.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition
InterceptorDefinitionTest.testInterceptorBindingsCanDeclareOtherInterceptorBindings()github
b)

Interceptor bindings are transitive - an interceptor binding declared by an interceptor binding type is inherited by all beans and other interceptor binding types that declare that interceptor binding type.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition
InterceptorDefinitionTest.testInterceptorBindingsCanDeclareOtherInterceptorBindings()github
c)The behaviour here is undefined.

Interceptor binding types declared @Target(TYPE) may not be applied to interceptor binding types declared @Target({TYPE, METHOD}).

Section 9.1.2 - Interceptor bindings for stereotypes

a)

Interceptor bindings may be applied to a stereotype by annotating the stereotype annotation

Coverage

org.jboss.cdi.tck.tests.interceptors.definition
InterceptorDefinitionTest.testStereotypeInterceptorBindings()github
b)

An interceptor binding declared by a stereotype are inherited by any bean that declares that stereotype.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition
InterceptorDefinitionTest.testStereotypeInterceptorBindings()github
c)The behaviour here is undefined.

If a stereotype declares interceptor bindings, it must be defined as @Target(TYPE).

Section 9.2 - Declaring the interceptor bindings of an interceptor

a)

The interceptor bindings of an interceptor are specified by annotating the interceptor class with the binding types and the @javax.interceptor.Interceptor annotation.

Coverage

org.jboss.cdi.tck.tests.interceptors.invocation
InterceptorInvocationTest.testManagedBeanIsIntercepted()github
ab)

An interceptor class may declare multiple interceptor bindings.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.multipleBindings
MultipleInterceptorBindingsTest.testInterceptorAppliedToBeanWithAllBindings()github
b)Defining interceptor using |ejb-jar.xml| is EJB specific feature and thus it's not tested in this TCK.

If an interceptor does not declare an @Interceptor annotation, it must be bound to beans using @Interceptors or ejb-jar.xml.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.interceptorCalledBeforeDecorator
InterceptorCalledBeforeDecoratorTest.testInterceptorCalledBeforeDecorator()github
c)

All interceptors declared using @Interceptor must specify at least one interceptor binding. If an interceptor declared using @Interceptor does not declare any interceptor binding, non-portable behavior results.

d)

An interceptor for lifecycle callbacks may only declare interceptor binding types that are defined as @Target(TYPE). If an interceptor for lifecycle callbacks declares an interceptor binding type that is defined @Target({TYPE, METHOD}), the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.broken.interceptorForLifecycleTargetMethod
InterceptorForLifecycleTargetMethodTest.testInterceptorForLifecycleTargetMethod()github

Section 9.3 - Binding an interceptor to a bean

a)

An interceptor binding may be declared by annotating the bean class, or a method of the bean class, with the interceptor binding type.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager.bean
SyntheticBeanTest.testSyntheticBeanIntercepted()github
org.jboss.cdi.tck.tests.interceptors.definition.lifecycle.enterprise
EnterpriseLifecycleInterceptorDefinitionTest.testLifecycleInterception()github
org.jboss.cdi.tck.tests.interceptors.definition.lifecycle
LifecycleInterceptorDefinitionTest.testLifecycleInterception()github
org.jboss.cdi.tck.tests.interceptors.definition
InterceptorDefinitionTest.testInterceptorBindingAnnotation()github

A bean class or method of a bean class may declare multiple interceptor bindings.

ba)

A bean class may declare multiple interceptor bindings.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.multipleBindings
MultipleInterceptorBindingsTest.testInterceptorAppliedToBeanWithAllBindings()github
bb)

A method of a bean class may declare multiple interceptor bindings.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.multipleBindings
MultipleInterceptorBindingsTest.testMultipleInterceptorsOnMethod()github

If the bean class of a managed bean declares or inherits a class level interceptor binding or a stereotype with interceptor bindings, it must not be declared final, or have any non-static, non-private, final methods. If a managed bean has a class-level interceptor binding and is declared final or has a non-static, non-private, final method, the container automatically detects the problem and treats it as a definition error.

ca)

If the bean class of a managed bean declares a class level interceptor binding, it must not be declared final.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.broken.finalClassInterceptor
FinalClassClassLevelInterceptorTest.testFinalClassWithClassLevelInterceptor()github
cb)

If the bean class of a managed bean declares a class level interceptor binding, it must not have any non-static, non-private, final methods.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.broken.finalClassInterceptor
FinalMethodClassLevelInterceptorTest.testFinalMethodWithClassLevelInterceptor()github
cc)

If the bean class of a managed bean inherits a class level interceptor binding, it must not be declared final.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.inheritance.broken.binding
FinalClassWithInheritedClassLevelInterceptorTest.testFinalClassWithInheritedClassLevelInterceptor()github
cd)

If the bean class of a managed bean inherits a class level interceptor binding, it must not have any non-static, non-private, final methods.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.inheritance.broken.binding
FinalMethodWithInheritedClassLevelInterceptorTest.testFinalMethodWithInheritedClassLevelInterceptor()github
ce)

If the bean class of a managed bean inherits a stereotype with interceptor bindings, it must not be declared final.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.inheritance.broken.binding
FinalMethodWithInheritedStereotypeInterceptorTest.testFinalClassWithInheritedStereotypeInterceptor()github
cf)

If the bean class of a managed bean inherits a stereotype with interceptor bindings, it must not have any non-static, non-private, final methods.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.inheritance.broken.binding
FinalClassWithInheritedStereotypeInterceptorTest.testFinalMethodWithInheritedStereotypeInterceptor()github

If a non-static, non-private method of a bean class of a managed bean declares a method level interceptor binding, neither the method nor the bean class may be declared final. If a non-static, non-private, final method of a managed bean has a method level interceptor binding, the container automatically detects the problem and treats it as a definition error.

da)

If a non-static, non-private method of a bean class of a managed bean declares a method level interceptor binding, the bean class may not be declared final.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.broken.finalClassInterceptor
FinalClassMethodLevelInterceptorTest.testFinalClassWithMethodLevelInterceptor()github
db)

If a non-static, non-private method of a bean class of a managed bean declares a method level interceptor binding, the method may not be declared final.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.broken.finalClassInterceptor
FinalMethodMethodLevelInterceptorTest.testFinalMethodWithMethodLevelInterceptor()github

Section 9.4 - Interceptor enablement and ordering

aa)This is a statement of intent

Interceptors may be enabled for an application, or enabled only for a particular bean archive.

The following assertion is not made explicitly by the spec, however it is implied ab)

By default, a bean archive has no enabled interceptors.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.interceptorNotListedInBeansXml
InterceptorNotListedInBeansXmlNotEnabledTest.testInterceptorNotListedInBeansXmlNotInvoked()github
ba)

An interceptor may be enabled for the entire application by listing its class, along with a priority attribute, under the <interceptors> element of the beans.xml file of the bean archive which contains the interceptor class.

Coverage

org.jboss.cdi.tck.tests.interceptors.ordering.global
GlobalInterceptorOrderingTest.testOrderingInWebInfClasses()github
GlobalInterceptorOrderingTest.testOrderingInLib()github
bb)

An interceptor may be enabled for a bean archive by listing its class under the <interceptors> element of the beans.xml file of the bean archive.

Coverage

org.jboss.cdi.tck.tests.interceptors.ordering.global
GlobalInterceptorOrderingTest.testOrderingInWebInfClasses()github
org.jboss.cdi.tck.tests.interceptors.definition.interceptorOrder
InterceptorOrderTest.testInterceptorsCalledInOrderDefinedByBeansXml()github
bc)

An interceptor enabled for an application may be disabled for a bean archive by listing its class, along with a disabled flag, under the <interceptors> element of the beans.xml file of the bean archive.

Coverage

org.jboss.cdi.tck.tests.interceptors.ordering.global
GlobalInterceptorOrderingTest.testOrderingInWebInfClasses()github
bd)

An interceptor may be given a default priority, but not enabled by listing its class, along with a disabled flag and the priority attribute, under the <interceptors> element of the beans.xml file of the bean archive which contains the interceptor class.

Coverage

org.jboss.cdi.tck.tests.interceptors.ordering.global
GlobalInterceptorOrderingTest.testOrderingInWebInfClasses()github
GlobalInterceptorOrderingTest.testOrderingInLib()github
be)

An interceptor with a default priority may be enabled for a bean archive by listing its class, along with an enabled flag, under the <interceptors> element of the beans.xml file of the bean archive.

Coverage

org.jboss.cdi.tck.tests.interceptors.ordering.global
GlobalInterceptorOrderingTest.testOrderingInWebInfClasses()github
bf)

The priority of the interceptor declaration, defined in Section 2.9, "Priority ordering", determines the default interceptor ordering for the application. The order of the interceptor declarations for a bean archive overrides the default interceptor order. If the set of interceptors enabled for the application and the set of interceptors enabled for a bean archive are disjoint, then the interceptors enabled for the bean archive are given an incrementing priority starting at 1000. Interceptors which occur earlier in the list are called first.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.interceptorOrder
InterceptorOrderTest.testInterceptorsCalledInOrderDefinedByBeansXml()github

Each child <class> element must specify the name of an interceptor class. If there is no class with the specified name, or if the class with the specified name is not an interceptor class, the container automatically detects the problem and treats it as a deployment problem.

caa)

Test with a non-existant class.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.broken.nonExistantClassInBeansXml
NonExistantClassInBeansXmlTest.testNonExistantClassInBeansXmlNotOk()github
cab)

Test with a class that isn't an interceptor.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.broken.nonInterceptorClassInBeansXml
NonInterceptorClassInBeansXmlTest.testNonInterceptorClassInBeansXmlNotOk()github
cb)

If the same class is listed twice under the <interceptors> element, the container automatically detects the problem and treats it as a deployment problem.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.broken.sameClassListedTwiceInBeansXml
SameClassListedTwiceInBeansXmlTest.testSameInterceptorClassListedTwiceInBeansXmlNotOk()github

Interceptors declared using interceptor bindings are called after interceptors declared using @Interceptors or in ejb-jar.xml and before any around-invoke or lifecycle event callback methods declared on the target class or any superclass of the target class.

fa)

Test with a managed bean

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.lifecycle.order
LifecycleInterceptorOrderTest.testLifecycleCallbackInvocationOrder()github
org.jboss.cdi.tck.tests.interceptors.definition.interceptorOrder
InterceptorOrderTest.testInterceptorsInvocationOrder()github
fb)

Test with session bean

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.enterprise.interceptorOrder
SessionBeanInterceptorOrderTest.testInterceptorsDeclaredUsingInterceptorsCalledBeforeInterceptorBinding()github
org.jboss.cdi.tck.tests.interceptors.definition.lifecycle.enterprise.order
EnterpriseLifecycleInterceptorDefinitionTest.testLifecycleInterception()github
g)

Interceptors are called before decorators.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.interceptorCalledBeforeDecorator
InterceptorCalledBeforeDecoratorTest.testInterceptorCalledBeforeDecorator()github
org.jboss.cdi.tck.tests.decorators.interceptor
DecoratorAndInterceptorTest.testMethodCallbacks()github

Section 9.5 - Interceptor resolution

a)

For a lifecycle callback method, the interceptor bindings include the interceptor bindings declared or inherited by the bean at the class level, including, recursively, interceptor bindings declared as meta-annotations of other interceptor bindings and stereotypes.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.inheritance.resolution
InterceptorBindingResolutionTest.testLifecycleInterceptorBindings()github
org.jboss.cdi.tck.tests.interceptors.definition.inheritance.resolution.enterprise
EnterpriseInterceptorBindingResolutionTest.testLifecycleInterceptorBindings()github
org.jboss.cdi.tck.tests.interceptors.definition.lifecycle.enterprise
EnterpriseLifecycleInterceptorDefinitionTest.testLifecycleInterception()github
org.jboss.cdi.tck.tests.interceptors.definition.lifecycle
LifecycleInterceptorDefinitionTest.testLifecycleInterception()github
LifecycleInterceptorDefinitionTest.tesMultipleLifecycleInterceptors()github

For a business method, or EJB timeout method, the bean interceptor bindings include the interceptor bindings declared or inherited by the bean at the class level, including, recursively, interceptor bindings declared as meta-annotations of other interceptor bindings and stereotypes, together with all interceptor bindings declared at the method level, including, recursively, interceptor bindings declared as meta-annotations of other interceptor bindings.

ba)

Check a business method

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.inheritance.resolution
InterceptorBindingResolutionTest.testBusinessMethodInterceptorBindings()github
org.jboss.cdi.tck.tests.interceptors.definition.inheritance.resolution.enterprise
EnterpriseInterceptorBindingResolutionTest.testBusinessMethodInterceptorBindings()github
bb)

Check an EJB timeout method

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.inheritance.resolution.enterprise
EnterpriseInterceptorBindingResolutionTest.testTimeoutMethodInterceptorBindings()github
ca)

An interceptor is bound to a method if the method has all the interceptor bindings of the interceptor. A method has an interceptor binding of an interceptor if it has an interceptor binding with (a) the same type and (b) the same annotation member value for each member which is not annotated @javax.enterprise.util.NonBinding, and the interceptor intercepts the given kind of lifecycle callback or business method, and the interceptor is enabled in the bean archive containing the bean.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.multipleBindings
MultipleInterceptorBindingsTest.testInterceptorAppliedToBeanWithAllBindings()github

For a custom implementation of the Interceptor interface defined in Section 11.1.2, "The Interceptor interface", the container calls getInterceptorBindings() to determine the interceptor bindings of the interceptor and intercepts() to determine if the interceptor intercepts a given kind of lifecycle callback, EJB timeout or business method.

fa)

Check for @PostConstruct

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.custom
CustomInterceptorTest.testCustomPostConstructInterceptor()github
fb)

Check for @PreDestroy

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.custom
CustomInterceptorTest.testCustomPreDestroyInterceptor()github
fc)

Check for @PostActivate

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.custom
CustomInterceptorTest.testCustomPostActivateInterceptor()github
fd)

Check for @PrePassivate

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.custom
CustomInterceptorTest.testCustomPrePassivateInterceptor()github
fe)

Check for @AroundInvoke

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.custom
CustomInterceptorTest.testCustomAroundInvokeInterceptor()github
ff)

Check for @AroundTimeout

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.custom
CustomInterceptorTest.testCustomAroundTimeoutInterceptor()github

Section 9.5.1 - Interceptors with multiple bindings

An interceptor class may specify multiple interceptor bindings.

a)

Test that the interceptor is applied to a bean with all of the bindings.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.multipleBindings
MultipleInterceptorBindingsTest.testInterceptorAppliedToBeanWithAllBindings()github
b)

Test that the interceptor it not applied to a bean with only some of the interceptor bindings.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.multipleBindings
MultipleInterceptorBindingsTest.testInterceptorNotAppliedToBeanWithSomeBindings()github

Section 9.5.2 - Interceptor binding types with members

a)

Interceptor binding types may have annotation members.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.member
InterceptorBindingTypeWithMemberTest.testInterceptorBindingTypeWithMember()github
ab)

Annotation member values are compared using equals().

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.member
InterceptorBindingTypeWithMemberTest.testInterceptorBindingTypeMemberValuesComparedWithEquals()github
b)

An annotation member may be excluded from consideration using the @Nonbinding annotation.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.member
InterceptorBindingTypeWithMemberTest.testInterceptorBindingTypeWithNonBindingMember()github
ca)

Array-valued or annotation-valued members of an interceptor binding type should be annotated @Nonbinding in a portable application. If an array-valued or annotation-valued member of an interceptor binding type is not annotated @Nonbinding, non-portable behavior results.

cb)

Interceptor bindings defined on methods may override the interceptor bindings defined on classes.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.binding.overriding
InterceptorBindingOverridingTest.testInterceptorBindingOverriden()github
d)

If the set of interceptor bindings of a bean or interceptor, including bindings inherited from stereotypes and other interceptor bindings, has two instances of a certain interceptor binding type and the instances have different values of some annotation member, the bean or interceptor must override the inherited set by definining an annotation instance of its own, otherwise, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.broken.invalidBindingAnnotations
InvalidStereotypeInterceptorBindingAnnotationsTest.testInterceptorBindingsWithConflictingAnnotationMembersNotOk()github
InvalidTransitiveInterceptorBindingAnnotationsTest.testInterceptorBindingsWithConflictingAnnotationMembersNotOk()github

Section 10.1 - Event types and qualifier types

aa)

An event object is an instance of a concrete Java class with no type variables.

Coverage

org.jboss.cdi.tck.tests.event.eventTypes
EventTypesTest.testEventTypeIsConcreteTypeWithNoTypeVariables()github
c)

The event types of the event include all superclasses and interfaces of the runtime class of the event object.

Coverage

org.jboss.cdi.tck.tests.event.eventTypes
EventTypesTest.testEventTypeIncludesAllSuperclassesAndInterfacesOfEventObject()github
cb)Doesn't specify an error condition

An event type may not contain a type variable.

d)

An event qualifier type is a Java annotation defined as @Target({FIELD, PARAMETER}) or @Target({METHOD, FIELD, PARAMETER, TYPE}) and @Retention(RUNTIME)

Coverage

org.jboss.cdi.tck.tests.event.bindingTypes
EventBindingTypesTest.testEventBindingTypeTargetsMethodFieldParameterElementTypes()github
e)

An event qualifier type is a Java annotation defined as @Target({FIELD, PARAMETER}) or @Target({METHOD, FIELD, PARAMETER, TYPE}) and @Retention(RUNTIME)

Coverage

org.jboss.cdi.tck.tests.event.bindingTypes
EventBindingTypesTest.testEventBindingTypeTargetsFieldParameterElementTypes()github
f)

An event qualifier type is a Java annotation defined as @Target({FIELD, PARAMETER}) or @Target({METHOD, FIELD, PARAMETER, TYPE}) and @Retention(RUNTIME)

Coverage

org.jboss.cdi.tck.tests.event.bindingTypes
EventBindingTypesTest.testNonRuntimeBindingTypeIsNotAnEventBindingType()github
EventBindingTypesTest.testFireEventWithNonRuntimeBindingTypeFails()github
g)

All event qualifier types must specify the @javax.inject.Qualifier meta-annotation

Coverage

org.jboss.cdi.tck.tests.event.bindingTypes
EventBindingTypesTest.testFireEventWithNonBindingAnnotationsFails()github
i)

Every event has the qualifier @javax.enterprise.inject.Any, even if it does not explicitly declare this qualifier.

Coverage

org.jboss.cdi.tck.tests.event.bindingTypes
EventBindingTypesTest.testEventAlwaysHasAnyBinding()github
org.jboss.cdi.tck.tests.event.implicit
ImplicitEventTest.testImplicitEventHasAnyBinding()github
j)

Any Java type may be an observed event type.

Coverage

org.jboss.cdi.tck.tests.event.eventTypes
EventTypesTest.testEventTypeIsConcreteTypeWithNoTypeVariables()github
EventTypesTest.testEventTypeIsArray()github

Section 10.2 - Observer resolution

a)Statement of intent

The process of matching an event to its observer methods is called observer resolution. The container considers event type and qualifiers when resolving observers.

b)Describes non-portable behavior

Observer resolution usually occurs at runtime.

An event is delivered to an observer method if the observer method belongs to an enabled bean, the event object is assignable to the observed event type, taking type parameters into consideration, the observer method has no event qualifiers or has a subset of the event qualifiers. An observer method has an event qualifier if it has an observed event qualifier with (a) the same type and (b) the same annotation member value for each member which is not annotated @javax.enterprise.util.Nonbinding. Also the event is not a container lifecycle event, as defined in Section 11.5 "Container lifecycle events", or the observer method belongs to an extension.

c)

Check an event is delivered if the observer method belongs to an enabled bean, the event object is assignable to the observed event type and has a subset of the event qualifiers.

Coverage

org.jboss.cdi.tck.tests.deployment.packaging.war.modules
WebArchiveModulesTest.testDecoratorAndCrossModuleEventObserver()github
WebArchiveModulesTest.testProducerAndEventDuringDisposal()github
org.jboss.cdi.tck.tests.event.observer
ObserverNotificationTest.testObserversNotified()github
d)

Check an event is not delivered if the observer method belongs to an disabled bean.

Coverage

org.jboss.cdi.tck.tests.event.observer
ObserverNotificationTest.testObserversNotified()github
j)

If the runtime type of the event object contains a type variable, the container must throw an IllegalArgumentException.

Coverage

org.jboss.cdi.tck.tests.event.fires
FireEventTest.testEventFireThrowsExceptionIfEventObjectContainsTypeVariable()github
k)

For a custom implementation of the ObserverMethod interface defined in Section 11.1.3, "The ObserverMethod interface", the container must call getObservedType() and getObservedQualifiers() to determine the observed event type and qualifiers.

Coverage

org.jboss.cdi.tck.tests.event.observer.extension
EventBeanObserverNotificationTest.testNoQualifier()github
EventBeanObserverNotificationTest.testSingleQualifier()github
EventBeanObserverNotificationTest.testMultipleQualifiers()github

Section 10.2.1 - Assignability of type variables, raw and parameterized types

a)

An event type is considered assignable to a type variable if the event type is assignable to the upper bound, if any.

Coverage

org.jboss.cdi.tck.tests.event.resolve.typeWithParameters
CheckTypeParametersWhenResolvingObserversTest.testEventTypeAssignableToATypeVariable()github
b)

A parameterized event type is considered assignable to a raw observed event type if the raw types are identical.

Coverage

org.jboss.cdi.tck.tests.event.resolve.typeWithParameters
CheckTypeParametersWhenResolvingObserversTest.testParameterizedEventTypeAssignableToRawType()github
CheckTypeParametersWhenResolvingObserversTest.testResolvingChecksTypeParameters()github

A parameterized event type is considered assignable to a parameterized observed event type if they have identical raw type and for each parameter the observed event type parameter is an actual type with identical raw type to the event type parameter, and, if the type is parameterized, the event type parameter is assignable to the observed event type parameter according to these rules, or the observed event type parameter is a wildcard and the event type parameter is assignable to the upper bound, if any, of the wildcard and assignable from the lower bound, if any, of the wildcard, or the observed event type parameter is a type variable and the event type parameter is assignable to the upper bound, if any, of the type variable.

c)

Check the event type parameter and the observed event type parameter are actual types with identical raw type.

Coverage

org.jboss.cdi.tck.tests.event.resolve.typeWithParameters
CheckTypeParametersWhenResolvingObserversTest.testObservedEventTypeParameterIsActualType()github
d)

Check the event type parameter and the observed event type parameter are actual types with identical raw type for nested type parameters.

Coverage

org.jboss.cdi.tck.tests.event.resolve.typeWithParameters
CheckTypeParametersWhenResolvingObserversTest.testObservedEventTypeParameterIsActualTypeNested()github
e)

Check the observed event type parameter is a wildcard and the event type parameter is assignable to the upper bound, if any, of the wildcard and assignable from the lower bound, if any, of the wildcard.

Coverage

org.jboss.cdi.tck.tests.event.resolve.typeWithParameters
CheckTypeParametersWhenResolvingObserversTest.testObservedEventTypeParameterIsWildcard()github
f)

Check the observed event type parameter is a type variable and the event type parameter is assignable to the upper bound, if any, of the type variable.

Coverage

org.jboss.cdi.tck.tests.event.resolve.typeWithParameters
CheckTypeParametersWhenResolvingObserversTest.testObservedEventTypeParameterIsTypeVariable()github

Section 10.2.2 - Event qualifier types with members

a)

The qualifier type for an Event qualifier may have annotation members.

Coverage

org.jboss.cdi.tck.tests.event.resolve.binding
ResolvingChecksBindingTypeMembersTest.testResolvingChecksBindingTypeMembers()github
org.jboss.cdi.tck.tests.event.observer.resolve
ResolveEventObserversTest.testObserverMethodMayHaveMultipleBindingTypes()github
b)Since only primitive types are allowed, the call to equals() cannot be checked

The container uses equals() to compare event qualifier type member values.

Section 10.2.3 - Multiple event qualifiers

a)

An event parameter may have multiple qualifiers.

Coverage

org.jboss.cdi.tck.tests.event.observer.resolve
ResolveEventObserversTest.testObserverMethodMayHaveMultipleBindingTypes()github
org.jboss.cdi.tck.tests.event
EventTest.testObserverMethodNotifiedWhenQualifiersMatch()github
b)

An observer method will only be notified if all the observed event qualifiers are specified when the event is fired.

Coverage

org.jboss.cdi.tck.tests.event
EventTest.testObserverMethodNotifiedWhenQualifiersMatch()github

Section 10.3 - Firing events

a)

Beans fire events via an instance of the javax.enterprise.event.Event interface, which may be injected.

Coverage

org.jboss.cdi.tck.tests.event.fires
FireEventTest.testInjectedAnyEventCanFireEvent()github
b)

The method fire() accepts an event object.

Coverage

org.jboss.cdi.tck.tests.event.fires
FireEventTest.testInjectedEventAcceptsEventObject()github
c)

Any combination of qualifiers may be specified at the injection point.

Coverage

org.jboss.cdi.tck.tests.event.fires
FireEventTest.testInjectedEventCanHaveBindings()github
d)

Or, the @Any qualifier may be used, allowing the application to specify qualifiers dynamically.

Coverage

org.jboss.cdi.tck.tests.event.fires
FireEventTest.testInjectedEventCanSpecifyBindingsDynamically()github

Section 10.3.1 - The Event interface

ca)

The Event interface provides a method for firing events with a specified combination of type and qualifiers.

Coverage

org.jboss.cdi.tck.tests.event.fires
FireEventTest.testEventProvidesMethodForFiringEventsWithCombinationOfTypeAndBindings()github
cb)

For an injected Event, the specified type is the type parameter specified at the injection point, and the specified qualifiers are the qualifiers specified at the injection point.

Coverage

org.jboss.cdi.tck.tests.event.fires
FireEventTest.testInjectedEventAcceptsEventObject()github
FireEventTest.testInjectedEventCanHaveBindings()github
eaa)

The select() method returns a child Event for a given specified type and additional specified qualifiers. If no specified type is given, the specified type is the same as the parent.

Coverage

org.jboss.cdi.tck.tests.event.select
SelectEventTest.testEventSelectReturnsEventOfSameType()github
eab)

If the specified type contains a type variable, an IllegalArgumentException is thrown.

Coverage

org.jboss.cdi.tck.tests.event.select
SelectEventTest.testEventSelectThrowsExceptionIfEventTypeHasTypeVariable()github
eba)

If two instances of the same qualifier type are passed to select(), an IllegalArgumentException is thrown.

Coverage

org.jboss.cdi.tck.tests.event.select
SelectEventTest.testEventSelectThrowsExceptionForDuplicateBindingType()github
SelectEventTest.testEventSelectWithSubtypeThrowsExceptionForDuplicateBindingType()github
ec)

If an instance of an annotation that is not a qualifier type is passed to select(), an IllegalArgumentException is thrown.

Coverage

org.jboss.cdi.tck.tests.event.select
SelectEventTest.testEventSelectThrowsExceptionIfAnnotationIsNotBindingType()github
SelectEventTest.testEventSelectWithSubtypeThrowsExceptionIfAnnotationIsNotBindingType()github
eda)

The method fire() fires an event with the specified qualifiers and notifies observers, as defined by Section 10.5, "Observer notification".

Coverage

org.jboss.cdi.tck.tests.event.fires
FireEventTest.testEventSelectedFiresAndObserversNotified()github
f)

If the runtime type of the event object contains a type variable, an IllegalArgumentException is thrown.

Coverage

org.jboss.cdi.tck.tests.event.fires
FireEventTest.testEventFireThrowsExceptionIfEventObjectContainsTypeVariable()github
g)

If the runtime type of the event object is assignable to the type of a container lifecycle event, IllegalArgumentException is thrown.

Coverage

org.jboss.cdi.tck.tests.event.fires
FireEventTest.testFireContainerLifecycleEvent()github

Section 10.3.2 - The built-in Event

a)

The container must provide a built-in bean with Event<X> in its set of bean types, for every Java type x that does not contain a type variable.

Coverage

org.jboss.cdi.tck.tests.event.implicit
ImplicitEventTest.testImplicitEventExistsForEachEventType()github
b)

The container must provide a built-in bean with every event qualifier type in its set of qualifier types.

Coverage

org.jboss.cdi.tck.tests.event.implicit
ImplicitEventTest.testImplicitEventHasAllExplicitBindingTypes()github
d)

The container must provide a built-in bean with scope @Dependent.

Coverage

org.jboss.cdi.tck.tests.event.implicit
ImplicitEventTest.testImplicitEventHasDependentScope()github
e)

The container must provide a built-in bean with no bean EL name.

Coverage

org.jboss.cdi.tck.tests.event.broken.raw
RawEventFieldInjectionTest.testDefinitionError()github
RawEventCustomBeanTest.testDefinitionError()github
RawEventProcessInjectionPointTest.testDefinitionError()github
RawEventInitMethodInjectionTest.testDefinitionError()github
RawEventObserverInjectionTest.testDefinitionError()github
RawEventDisposerInjectionTest.testDefinitionError()github
RawEventProducerMethodInjectionTest.testDefinitionError()github
RawEventConstructorInjectionTest.testDefinitionError()github
org.jboss.cdi.tck.tests.event.implicit
ImplicitEventTest.testImplicitEventHasNoName()github
f)

The container must provide a built-in bean with an implementation provided automatically by the container.

Coverage

org.jboss.cdi.tck.tests.event.implicit
ImplicitEventTest.testImplicitEventHasImplementation()github
e)

If an injection point of raw type Event is defined, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.event.broken.raw
RawEventFieldInjectionTest.testDefinitionError()github
RawEventCustomBeanTest.testDefinitionError()github
RawEventProcessInjectionPointTest.testDefinitionError()github
RawEventInitMethodInjectionTest.testDefinitionError()github
RawEventObserverInjectionTest.testDefinitionError()github
RawEventDisposerInjectionTest.testDefinitionError()github
RawEventProducerMethodInjectionTest.testDefinitionError()github
RawEventConstructorInjectionTest.testDefinitionError()github
org.jboss.cdi.tck.tests.event.implicit
ImplicitEventTest.testImplicitEventHasNoName()github
g)

The built-in implementation must be a passivation capable dependency, as defined in Section 6.6.2, "Passivation capable dependencies".

Coverage

org.jboss.cdi.tck.tests.event.implicit
ImplicitEventTest.testImplicitEventIsPassivationCapable()github

Section 10.4 - Observer methods

a0)A general statement.

An observer method allows the application to receive and respond to event notifications.

aa)

An observer method is a non-abstract method of a managed bean class or session bean class (or of an extension, as defined in Section 11.5, "Container lifecycle events").

Coverage

org.jboss.cdi.tck.tests.event.broken.observer.beanNotManaged
ObserverMethodOnIncorrectBeanTest.testObserverMethodNotOnManagedOrSessionBeanFails()github
org.jboss.cdi.tck.tests.event.resolve.typeWithParameters
CheckTypeParametersWhenResolvingObserversTest.testObservedEventTypeParameterIsActualType()github
c)

An observer method may be either static or non-static.

Coverage

org.jboss.cdi.tck.tests.event
EventTest.testStaticObserverMethodInvoked()github
d)

If the bean is a session bean, the observer method must be either a business method of the EJB or a static method of the bean class.

Coverage

org.jboss.cdi.tck.tests.event.observer.resolve.enterprise
ResolveEnterpriseEventObserverTest.testObserverMethodOnEnterpriseBeanIsBusinessMethodOrStatic()github
org.jboss.cdi.tck.tests.event.broken.observer.notBusinessMethod
EJBObserverMethodNotBusinessMethodTest.testObserverMethodOnEnterpriseBeanNotBusinessMethodOrStaticFails()github
e)

There may be arbitrarily many observer methods with the same event parameter type and qualifiers.

Coverage

org.jboss.cdi.tck.tests.event.observer.resolve
ResolveEventObserversTest.testMultipleObserverMethodsForSameEventPermissible()github
f)

A bean (or extension) may declare multiple observer methods.

Coverage

org.jboss.cdi.tck.tests.event.observer.resolve
ResolveEventObserversTest.testMultipleObserverMethodsOnBeanPermissible()github

Section 10.4.1 - Event parameter of an observer method

a)

Each observer method must have exactly one event parameter, of the same type as the event type it observes. When searching for observer methods for an event, the container considers the type and qualifiers of the event parameter

Coverage

org.jboss.cdi.tck.tests.event.resolve.typeWithParameters
ChecksEventTypeWhenResolvingTest.testResolvingChecksEventType()github
org.jboss.cdi.tck.tests.event.resolve.binding
ResolvingChecksBindingTypeMembersTest.testResolvingChecksBindingTypeMembers()github
org.jboss.cdi.tck.tests.event.broken.observer.tooManyParameters
ObserverMethodWithTwoEventParametersTest.testObserverMethodMustHaveOnlyOneEventParameter()github
b)

If the event parameter does not explicitly declare any qualifier, the observer method observes events with no qualifier.

Coverage

org.jboss.cdi.tck.tests.event.observer.resolve
ResolveEventObserversTest.testObserverMethodWithoutBindingTypesObservesEventsWithoutBindingTypes()github

The event parameter type may contain a type variable or wildcard.

ca)

Test with a type variable.

Coverage

org.jboss.cdi.tck.tests.event.observer.wildcardAndTypeVariable
ObserverMethodWithParametertizedTypeTest.testObserverMethodCanObserveWildcardType()github
cb)

Test with a wildcard.

Coverage

org.jboss.cdi.tck.tests.event.observer.wildcardAndTypeVariable
ObserverMethodWithParametertizedTypeTest.testObserverMethodCanObserveTypeVariable()github

Section 10.4.2 - Declaring an observer method

a)

An observer method may be declared by annotating a parameter @javax.enterprise.event.Observes of a default-access, public, protected or private method. That parameter is the event parameter. The declared type of the parameter is the observed event type.

Coverage

org.jboss.cdi.tck.tests.event.observer.resolve
ResolveEventObserversTest.testMethodWithParameterAnnotatedWithObservesRegistersObserverMethod()github
b)

If a method has more than one parameter annotated @Observes, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.event.broken.observer.tooManyParameters
ObserverMethodWithTwoEventParametersTest.testObserverMethodMustHaveOnlyOneEventParameter()github
c)

Observed event qualifiers may be declared by annotating the event parameter.

Coverage

org.jboss.cdi.tck.tests.event.observer.resolve
ResolveEventObserversTest.testObserverMethodMayHaveMultipleBindingTypes()github
d)

If an observer method is annotated @Produces the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.event.broken.observer.isProducer
ObserverMethodAnnotatedProducesTest.testObserverMethodAnnotatedProducesFails()github
e)

If an observer method is annotated @Inject the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.event.broken.observer.isInitializer
ObserverMethodAnnotatedInitialzerTest.testObserverMethodAnnotatedInitializerFails()github
org.jboss.cdi.tck.tests.deployment.lifecycle.broken.failsDuringBeanDiscovery
DeploymentFailureTest.testDeploymentFailsBeforeNotifyingObserversAfterBeanDiscovery()github
f)

If an observer method has a parameter annotated @Disposes, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.event.broken.observer.isDisposer
ObserverMethodAnnotatedDisposesTest.testObserverMethodWithDisposesParamFails()github
g)

If a non-static method of a session bean class has a parameter annotated @Observes, and the method is not a business method of the EJB, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.event.broken.observer.notBusinessMethod
EJBObserverMethodNotBusinessMethodTest.testObserverMethodOnEnterpriseBeanNotBusinessMethodOrStaticFails()github
h)

Interceptors and decorators may not declare observer methods. If an interceptor or decorator has a method with a parameter annotated @Observes, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.decorators.definition.broken.observer
DecoratorWithObserverMethodTest.testDecoratorWithObserverMethodNotOk()github
org.jboss.cdi.tck.tests.interceptors.definition.broken.observer
InterceptorWithObserverMethodTest.testInterceptorWithObserverMethodNotOk()github
i)

In addition to the event parameter, observer methods may declare additional parameters, which may declare qualifiers. These additional parameters are injection points.

Coverage

org.jboss.cdi.tck.tests.event.observer.broken.validation.unsatisfied
ObserverMethodParameterInjectionValidationTest.test()github
org.jboss.cdi.tck.tests.event.observer.broken.validation.ambiguous
ObserverMethodParameterInjectionValidationTest.test()github
org.jboss.cdi.tck.tests.event
EventTest.testObserverMethodParameterInjectionPoints()github

Section 10.4.3 - Conditional observer methods

a)

A conditional observer method may be declared by specifying receive=IF_EXISTS.

Coverage

org.jboss.cdi.tck.tests.event.observer.conditional
ConditionalObserverTest.testConditionalObserver()github
b)

Beans with scope @Dependent may not have conditional observer methods. If a bean with scope @Dependent has an observer method declared receive=IF_EXISTS, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.event.broken.observer.dependentIsConditionalObserver
DependentIsConditionalObserverTest.testDependentBeanWithConditionalObserverMethodIsDefinitionError()github
c)

The enumeration javax.enterprise.event.Reception identifies the possible values of receive.

Coverage

org.jboss.cdi.tck.tests.event.observer.conditional
ConditionalObserverTest.testNotifyEnumerationContainsNotifyValues()github

Section 10.4.4 - Transactional observer methods

a)Unverifiable since an observer method cannot detect if a transaction is involved or not

Transactional observer methods are observer methods which receive event notifications during the before or after completion phase of the transaction in which the event was fired. If no transaction is in progress when the event is fired, they are notified at the same time as other observers

Coverage

org.jboss.cdi.tck.tests.event.observer.transactional
TransactionalObserverTest.testSucessfullTransaction()github
TransactionalObserverTest.testFailedTransaction()github
TransactionalObserverTest.testNoTransaction()github
b)Unverifiable since an observer method cannot detect if a transaction is involved or not

A before completion observer method is called during the before completion phase of the transaction

Coverage

org.jboss.cdi.tck.tests.event.observer.transactional
TransactionalObserverTest.testSucessfullTransaction()github
TransactionalObserverTest.testFailedTransaction()github
c)Unverifiable since an observer method cannot detect if a transaction is involved or not

An after completion observer method is called during the after completion phase of the transaction

Coverage

org.jboss.cdi.tck.tests.event.observer.transactional
TransactionalObserverTest.testSucessfullTransaction()github
TransactionalObserverTest.testFailedTransaction()github
d)Unverifiable since an observer method cannot detect if a transaction is involved or not

An after success observer method is called during the after completion phase of the transaction, only when the transaction completes successfully

Coverage

org.jboss.cdi.tck.tests.event.observer.transactional
TransactionalObserverTest.testSucessfullTransaction()github
TransactionalObserverTest.testFailedTransaction()github
e)Unverifiable since an observer method cannot detect if a transaction is involved or not

An after failure observer method is called during the after completion phase of the transaction, only when the transaction fails

Coverage

org.jboss.cdi.tck.tests.event.observer.transactional
TransactionalObserverTest.testSucessfullTransaction()github
TransactionalObserverTest.testFailedTransaction()github
f)Should we just sigtest this?

The enumeration javax.enterprise.event.TransactionPhase identifies the kind of transactional observer method.

gaa)

A transactional observer method may be declared by specifying any value other than IN_PROGRESS for during.

Coverage

org.jboss.cdi.tck.tests.event.observer.transactional
TransactionalObserverTest.testSucessfullTransaction()github
TransactionalObserverTest.testFailedTransaction()github

Section 10.5 - Observer notification

aa)

When an event is fired by the application, the container must determine the observers for that event according to the observer resolution defined by Section 10.2, "Observer resolution", then then for each observer method, either invoke the observer method immediately or register the observer method for later invocation during the transaction completion phase, using a JTA Synchronization.

Coverage

org.jboss.cdi.tck.tests.event.observer.resolve
ResolveEventObserversTest.testObserverMethodRegistration()github
org.jboss.cdi.tck.tests.event.observer
ObserverNotificationTest.testObserversNotified()github
ba)Tested in 5.5.6.

The container calls observer methods as defined in Section 5.5.6, "Invocation of observer methods".

bb)

If the observer method is a transactional observer method and there is currently a JTA transaction in progress, the container calls the observer method during the appropriate transaction completion phase. Otherwise, the container calls the observer immediately.

Coverage

org.jboss.cdi.tck.tests.event.observer.transactional
TransactionalObserverTest.testSucessfullTransaction()github
TransactionalObserverTest.testFailedTransaction()github
bc)

If the observer method is a transactional observer method and there is currently a JTA transaction in progress, the container calls the observer method during the appropriate transaction completion phase. Otherwise, the container calls the observer immediately.

Coverage

org.jboss.cdi.tck.tests.event.observer.transactional
TransactionalObserverTest.testNoTransaction()github
bca)

If the observer method is a conditional observer method and there is no context active for the scope to which the bean declaring the observer method belongs, then the observer method should not be called.

Coverage

org.jboss.cdi.tck.tests.event.observer.conditional
ConditionalObserverTest.testConditionalObserverMethodNotInvokedIfNoActiveContext()github
bcb)

The order in which observer methods are called is not defined, and so portable applications should not rely upon the order in which observers are called.

bda)

Any observer method called before completion of a transaction may call setRollbackOnly() to force a transaction rollback.

Coverage

org.jboss.cdi.tck.tests.event.observer.transactional
TransactionalObserverTest.testObserverFailedTransaction()github
bdb)Doesn't specify what happens if they do

An observer method may not directly initiate, commit or rollback JTA transactions.

ca)We can't verify what is logged

Observers may throw exceptions. If an observer method is a transactional observer method, any exception is caught and logged by the container.

cb)

Observers may throw exceptions. If an observer method is a transactional observer method, any exception is caught and logged by the container. Otherwise, the exception aborts processing of the event.

Coverage

org.jboss.cdi.tck.tests.event.observer.abortProcessing
ObserverExceptionAbortsProcessingTest.testObserverThrowsExceptionAbortsNotifications()github
cc)

Observers may throw exceptions. If an observer method is a transactional observer method, any exception is caught and logged by the container. Otherwise, the exception aborts processing of the event. No other observer methods of that event will be called. The BeanManager.fireEvent() or Event.fire() method rethrows the exception. If the exception is a checked exception, it is wrapped and rethrown as an (unchecked) ObserverException.

Coverage

org.jboss.cdi.tck.tests.event.observer.runtimeException
ObserverExceptionRethrownTest.testNonTransactionalObserverThrowsNonCheckedExceptionIsRethrown()github
cd)

Observers may throw exceptions. If an observer method is a transactional observer method, any exception is caught and logged by the container. Otherwise, the exception aborts processing of the event. No other observer methods of that event will be called. The BeanManager.fireEvent() or Event.fire() method rethrows the exception. If the exception is a checked exception, it is wrapped and rethrown as an (unchecked) ObserverException.

Coverage

org.jboss.cdi.tck.tests.event.observer.checkedException
CheckedExceptionWrappedTest.testNonTransactionalObserverThrowsCheckedExceptionIsWrappedAndRethrown()github

For a custom implementation of the ObserverMethod interface defined in Section 11.1.3, "The ObserverMethod interface", the container must call getTransactionPhase() to determine if the observer method is a transactional observer method, and notify() to invoke the method.

fa)

Check getTransactionPhase() is called.

Coverage

org.jboss.cdi.tck.tests.event.observer.transactional.custom
CustomTransactionalObserverTest.testCustomTransactionalObserver()github
fb)

Check notify() is called.

Coverage

org.jboss.cdi.tck.tests.event.observer.transactional.custom
CustomTransactionalObserverTest.testCustomTransactionalObserver()github
fd)

CDI 1.1 implementations should call the notify method which takes both the event object and the event qualifiers only.

Coverage

org.jboss.cdi.tck.tests.event.observer.extension
BeanManagerObserverNotificationTest.testNoQualifier()github
BeanManagerObserverNotificationTest.testSingleQualifier()github
BeanManagerObserverNotificationTest.testMultipleQualifiers()github
EventBeanObserverNotificationTest.testNoQualifier()github
EventBeanObserverNotificationTest.testSingleQualifier()github
EventBeanObserverNotificationTest.testMultipleQualifiers()github

Section 10.5.1 - Observer method invocation context

ba)

If the observer method is a before completion transactional observer method, it is called within the context of the transaction that is about to complete and with the same client security context and lifecycle contexts.

Coverage

No tests exist for this assertion

c)

If the observer method is any other kind of transactional observer method, it is called in an unspecified transaction context, but with the same client security context and lifecycle contexts as the transaction that just completed.

Coverage

No tests exist for this assertion

da)

If an observer method is not a before completion transactional method, and not any other kind of transactional observer method, then the observer method is called in the same transaction context, client security context and lifecycle contexts as the invocation of Event.fire() or BeanManager.fireEvent().

Coverage

No tests exist for this assertion

e)

The transaction and security contexts for a business method of a session bean also depend upon the transaction attribute and @RunAs descriptor, if any.

Coverage

No tests exist for this assertion

Section 11 - Portable extensions

a)

A portable extension may integrate with the container by providing its own beans, interceptors and decorators to the container.

b)

A portable extension may integrate with the container by injecting dependencies into its own objects using the dependency injection service.

c)

A portable extension may integrate with the container by providing a context implementation for a custom scope.

f)

Augmenting or overriding the annotation-based metadata with metadata from some other source.

Section 11.1 - The Bean interface

aa)

Implementations of Bean must also implement the inherited operations defined by the Contextual interface defined in Section 6.1, "The Contextual interface".

Coverage

org.jboss.cdi.tck.tests.context.dependent
DependentContextTest.testContextIsActiveWhenInvokingDisposalMethod()github
org.jboss.cdi.tck.tests.context
DestroyedInstanceReturnedByGetTest.testDestroyedInstanceMustNotBeReturnedByGet()github
ba)

getTypes(), getQualifiers(), getScope(), getName() and getStereotypes() must return the bean types, qualifiers, scope type, EL name and stereotypes of the bean, as defined in Chapter 2, Concepts.

Coverage

org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes.broken.invalid
InvalidTypesTest.test()github
InvalidQualifierTest.test()github
InvalidScopeTest.test()github
InvalidStereotypeTest.test()github
org.jboss.cdi.tck.tests.definition.bean
BeanDefinitionTest.testQualifiersNonEmpty()github
BeanDefinitionTest.testHasScopeType()github
BeanDefinitionTest.testBeanTypes()github
BeanDefinitionTest.testMultipleStereotypes()github
bb)

getBeanClass() returns the bean class of the managed bean or session bean or of the bean that declares the producer method or field.

Coverage

org.jboss.cdi.tck.tests.definition.bean
BeanDefinitionTest.testBeanClassOnSimpleBean()github
bc)

isAlternative() must return true if the bean is an alternative, and false otherwise.

Coverage

org.jboss.cdi.tck.tests.alternative
AlternativeAvailabilityTest.testIsAlternative()github
bd)

isNullable() must return true if the method create() sometimes returns a null value, and false otherwise, as defined in Section 5.2.4, "Primitive types and null values".

Coverage

org.jboss.cdi.tck.tests.definition.bean
BeanDefinitionTest.testIsNullable()github
c)

getInjectionPoints() returns a set of InjectionPoint objects, defined in Section 5.5.7, "Injection point metadata", representing injection points of the bean, that will be validated by the container at initialization time.

Coverage

org.jboss.cdi.tck.tests.definition.qualifier
QualifierDefinitionTest.testDefaultQualifierForInjectionPoint()github
f)

An instance of Bean exists for every enabled bean.

Coverage

org.jboss.cdi.tck.tests.deployment.lifecycle
DeploymentTest.testOnlyEnabledBeansDeployed()github
g)

A portable extension may add support for new kinds of beans beyond those defined by the this specification (managed beans, session beans, producer methods, producer fields and resources) by implementing Bean and registering beans with the container, using the mechanism defined in Section 11.5.2, "AfterBeanDiscovery event".

Section 11.1.1 - The Decorator interface

a)

The Bean object for a decorator must implement the interface javax.enterprise.inject.spi.Decorator.

Coverage

org.jboss.cdi.tck.tests.decorators.definition
DecoratorDefinitionTest.testDecoratorIsManagedBean()github
b)

getDecoratedTypes() returns the decorated types of the decorator.

Coverage

org.jboss.cdi.tck.tests.decorators.definition
DecoratorDefinitionTest.testDecoratedTypes()github
c)

getDelegateType() and getDelegateQualifiers() return the delegate type and qualifiers of the decorator.

Coverage

org.jboss.cdi.tck.tests.decorators.definition
DecoratorDefinitionTest.testDelegateInjectionPoint()github
d)

An instance of Decorator exists for every enabled decorator.

Coverage

org.jboss.cdi.tck.tests.decorators.definition
DecoratorDefinitionTest.testInstanceOfDecoratorForEachEnabled()github

Section 11.1.2 - The Interceptor interface

a)

The Bean object for an interceptor must implement javax.enterprise.inject.spi.Interceptor.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition
InterceptorDefinitionTest.testInterceptorsImplementInterceptorInterface()github
b)

getInterceptorBindings() returns the interceptor bindings of the interceptor.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition
InterceptorDefinitionTest.testInterceptorBindingTypes()github
c)

intercepts() returns true if the interceptor intercepts the specified kind of lifecycle callback or method invocation, and false otherwise.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition
InterceptorDefinitionTest.testInterceptionType()github
d)

intercept() invokes the specified kind of lifecycle callback or method invocation interception upon the given instance of the interceptor.

Coverage

org.jboss.cdi.tck.tests.extensions.interceptors.custom
CustomInterceptorInvocationTest.testCustomInterceptorInvocation()github
e)

An InterceptionType identifies the kind of lifecycle callback, EJB timeout method or business method.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition
InterceptorDefinitionTest.testInterceptionType()github
f)

An instance of Interceptor exists for every enabled interceptor.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition
InterceptorDefinitionTest.testInstanceOfInterceptorForEveryEnabledInterceptor()github

Section 11.1.3 - The ObserverMethod interface

a)

The interface javax.enterprise.inject.spi.ObserverMethod defines everything the container needs to know about an observer method.

b)

getBeanClass() returns the bean class of the bean that declares the observer method.

Coverage

org.jboss.cdi.tck.tests.event.observer.method
ObserverMethodTest.testGetBeanClassOnObserverMethod()github
c)

getObservedType() and getObservedQualifiers() return the observed event type and qualifiers.

Coverage

org.jboss.cdi.tck.tests.event.observer.method
ObserverMethodTest.testGetObservedTypeOnObserverMethod()github
ObserverMethodTest.testGetObservedQualifiersOnObserverMethod()github
d)

getReception() returns IF_EXISTS for a conditional observer and ALWAYS otherwise.

Coverage

org.jboss.cdi.tck.tests.event.observer.method
ObserverMethodTest.testGetNotifyOnObserverMethod()github
e)

getTransactionPhase() returns the appropriate transaction phase for a transactional observer method or IN_PROGRESS otherwise.

Coverage

org.jboss.cdi.tck.tests.event.observer.method
ObserverMethodTest.testGetTransactionPhaseOnObserverMethod()github
f)

notify() calls the observer method, as defined in Section 5.5.6 "Invocation of observer methods".

Coverage

org.jboss.cdi.tck.tests.event.observer.method
ObserverMethodTest.testNotifyOnObserverMethod()github
ga)

An instance of ObserverMethod exists for every observer method of every enabled bean.

Coverage

org.jboss.cdi.tck.tests.event.observer.method
ObserverMethodTest.testInstanceOfBeanForEveryEnabledObserverMethod()github

Section 11.2 - The Producer and InjectionTarget interfaces

a)Statement of intent

The interface javax.enterprise.inject.spi.Producer provides a generic operation for producing an instance of a type.

For a Producer that represents a class, produce() calls the constructor annotated @Inject if it exists, or the constructor with no parameters otherwise, as defined in Section 5.5.1, "Injection using the bean constructor". and returns the resulting instance. If the class has interceptors, produce() is responsible for building the interceptors and decorators of the instance.

ba)

Test field injection occurs

Coverage

org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testProduceAndInjectCallsInitializerAndConstructor()github
bb)

Test initializer methods called

Coverage

org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testProduceAndInjectCallsInitializerAndConstructor()github
bc)

Test constructor injected

Coverage

org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testProduceAndInjectCallsInitializerAndConstructor()github
bd)

Test decorator stack built

Coverage

No tests exist for this assertion

be)

Test interceptor stack built

Coverage

No tests exist for this assertion

c)

For a Producer that represents a class, dispose() does nothing.

Coverage

org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testDisposeDoesNothing()github

For a Producer that represents a class, getInjectionPoints() returns a set of InjectionPoint objects representing all injected fields, bean constructor parameters and initializer method parameters.

da)

Test injected fields.

Coverage

org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testGetInjectionPointsForFields()github
db)

Test bean constructor parameters.

Coverage

org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testGetInjectionPointsForConstructorAndInitializer()github
dc)

Test initializer method parameters.

Coverage

org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testGetInjectionPointsForConstructorAndInitializer()github

For a Producer that represents a producer method or field, produce() calls the producer method on, or accesses the producer field of, a contextual instance of the bean that declares the producer method, as defined in Section 5.5.4, "Invocation of producer or disposer methods".

eaa)

Test with producer method.

Coverage

org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testProduceCallsProducerMethod()github
eba)

Test with producer field.

Coverage

org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testProduceAccessesProducerField()github

For a Producer that represents a producer method or field, dispose() calls the disposer method, if any, on a contextual instance of the bean that declares the disposer method, as defined in Section 5.5.4, "Invocation of producer or disposer methods", or performs any additional required cleanup, if any, to destroy state associated with a resource.

faa)

Test with producer method.

Coverage

org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testProducerForMethodDisposesProduct()github
g)

For a Producer that represents a producer method, getInjectionPoints() returns the set of InjectionPoint objects representing all parameters of the producer method.

Coverage

org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testInjectionPointsForProducerMethod()github
h)Statement of intent

The subinterface javax.enterprise.inject.spi.InjectionTarget provides operations for performing dependency injection and lifecycle callbacks on an instance of a type.

i)

inject() performs dependency injection upon the given object. The container performs Java EE component environment injection, according to the semantics required by the Java EE platform specification, sets the value of all injected fields, and calls all initializer methods, as defined in Section 5.5.2, "Injection of fields and initializer methods".

Coverage

org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testInjectionTargetInject()github
j)

postConstruct() calls the @PostConstruct callback, if it exists, according to the semantics required by the Java EE platform specification.

Coverage

org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testInjectionTargetPostConstruct()github
k)

preDestroy() calls the @PreDestroy callback, if it exists, according to the semantics required by the Java EE platform specification.

Coverage

org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testInjectionTargetPreDestroy()github
l)Targeting extension developers

Implementations of Producer and InjectionTarget must ensure that the set of injection points returned by getInjectionPoints() are injected by produce() or inject().

Section 11.3 - The BeanManager object

The container provides a built-in bean with bean type BeanManager, scope @Dependent and qualifier @Default.

aa)

Test the bean type.

Coverage

org.jboss.cdi.tck.tests.lookup.manager
ManagerTest.testContainerProvidesManagerBean()github
ab)

Test the scope.

Coverage

org.jboss.cdi.tck.tests.lookup.manager
ManagerTest.testManagerBeanIsDependentScoped()github
ac)

Test the qualifier.

Coverage

org.jboss.cdi.tck.tests.lookup.manager
ManagerTest.testManagerBeanHasCurrentBinding()github
b)

The built-in implementation must be a passivation capable dependency, as defined in Section 6.6.2, "Passivation capable dependencies".

Coverage

org.jboss.cdi.tck.tests.lookup.manager
ManagerTest.testManagerBeanIsPassivationCapable()github
c)

Any bean may obtain an instance of BeanManager by injecting it.

Coverage

org.jboss.cdi.tck.tests.lookup.manager
ManagerTest.testInjectingManager()github
e)This does not appear to be testable

Any operation of BeanManager may be called at any time during the execution of the application.

Coverage

No tests exist for this assertion

Section 11.3.1 - Obtaining a reference to the CDI container

A portable extension or other object may obtain a reference to the current container by calling CDI.current(). CDI.getBeanManager() may be called at any time after the container fires the BeforeBeanDiscovery container lifecycle event until the container fires the BeforeShutdown container lifecycle event. Other methods on CDI may be called after the application initialization is completed until the application shutdown starts.

aa)

Test CDI.getBeanManager() is called before the application initialization is completed.

Coverage

org.jboss.cdi.tck.tests.lookup.manager.provider.init
CDIProviderInitTest.testAccessingBeanManager()github
ab)

Test CDI.getBeanManager() is called after the application initialization is completed.

Coverage

org.jboss.cdi.tck.tests.lookup.manager.provider.runtime
CDIProviderRuntimeTest.testGetBeanManager()github
ac)

Test lookup of bean instances after the application initialization is completed.

Coverage

org.jboss.cdi.tck.tests.lookup.manager.provider.runtime
CDIProviderRuntimeTest.testLookup()github

The CDIProvider to use may be set by the application or container using the setCDIProvider() method. If the setCDIProvider() has not been called, the first service provider of the service javax.enterprise.inject.spi.CDIProvider declared in META-INF/services is used. If no provider is available an IllegalStateException is thrown.

ba)

Test using CDIProvider set by the application.

Coverage

org.jboss.cdi.tck.tests.lookup.manager.provider.custom
CustomCDIProviderTest.testCustomCDIProvider()github
d)

Java EE components may obtain an instance of BeanManager from JNDI by looking up the name java:comp/BeanManager.

Coverage

org.jboss.cdi.tck.tests.lookup.manager.jndi
ManagerTest.testManagerLookupInJndi()github
ManagerTestEar.testManagerLookupInJndi()github

Section 11.3.2 - Obtaining a contextual reference for a bean

a)

The method BeanManager.getReference() returns a contextual reference for a given bean and bean type, as defined in Section 6.5.3, "Contextual reference for a bean".

Coverage

org.jboss.cdi.tck.tests.lookup.manager
ManagerTest.testGetReferenceReturnsContextualInstance()github
b)

The first parameter is the Bean object representing the bean. The second parameter represents the bean type that must be implemented by any client proxy that is returned. The third parameter is an instance of CreationalContext that may be used to destroy any object with scope @Dependent that is created.

Coverage

org.jboss.cdi.tck.tests.lookup.manager
ManagerTest.testGetReferenceReturnsContextualInstance()github
c)

If the given type is not a bean type of the given bean, an IllegalArgumentException is thrown.

Coverage

org.jboss.cdi.tck.tests.lookup.manager
ManagerTest.testGetReferenceWithIllegalBeanType()github

Section 11.3.3 - Obtaining an injectable reference

a)

The method BeanManager.getInjectableReference() returns an injectable reference for a given injection point, as defined in Section 6.5.5, "Injectable references".

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint
InjectableReferenceTest.testGetInjectableReferenceOnBeanManager()github
ab)

The first parameter represents the target injection point. The second parameter is an instance of CreationalContext that may be used to destroy any object with scope @Dependent that is created.

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint
InjectableReferenceTest.testGetInjectableReferenceOnBeanManager()github
b)

If the InjectionPoint represents a decorator delegate injection point, getInjectableReference() returns a delegate, as defined in Section 8.1.2, "Decorator delegate injection points".

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint
InjectableReferenceTest.testGetInjectableReferenceReturnsDelegateForDelegateInjectionPoint()github
bb)

If typesafe resolution results in an unsatisfied dependency, the container must throw an UnsatisfiedResolutionException.

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint.broken.reference.unresolved
UnsatisfiedInjectableReferenceTest.testUnsatisfiedReference()github
bc)

If typesafe resolution results in an unresolvable ambiguous dependency, the container must throw an AmbiguousResolutionException.

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint.broken.reference.ambiguous
AmbiguousInjectableReferenceTest.testUnsatisfiedReference()github
c)This cannot be well tested at the moment.

Implementations of Bean usually maintain a reference to an instance of BeanManager. When the Bean implementation performs dependency injection, it must obtain the contextual instances to inject by calling BeanManager.getInjectableReference(), passing an instance of InjectionPoint that represents the injection point and the instance of CreationalContext that was passed to Bean.create().

Coverage

No tests exist for this assertion

Section 11.3.4 - Obtaining a CreationalContext

a)

An instance of CreationalContext for a certain instance of Contextual may be obtained by calling BeanManager.createCreationalContext().

Coverage

org.jboss.cdi.tck.tests.lookup.injectionpoint
InjectableReferenceTest.testGetInjectableReferenceOnBeanManager()github
b)

An instance of CreationalContext for a non-contextual object may be obtained by passing a null value to createCreationalContext().

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
CreationalContextForNonContextualTest.testCreationalContext()github

Section 11.3.5 - Obtaining a Bean by type

The method BeanManager.getBeans() returns the set of beans which have the given required type and qualifiers and are available for injection in the module or library containing the class into which the BeanManager was injected or the Java EE component from whose JNDI environment namespace the BeanManager was obtained, according to the rules for candidates of typesafe resolution defined in Section 5.2.1, “Performing typesafe resolution”.

aa)

Test simple scenario.

Coverage

org.jboss.cdi.tck.tests.extensions.bean.bytype
BeanByTypeTest.testGetBeans()github
The following assertion is not made explicitly by the spec, however it is implied ab)CDI-231

Test alternatives are not filtered.

Coverage

org.jboss.cdi.tck.tests.extensions.bean.bytype
BeanByTypeTest.testGetBeansDoesNotResolveAlternatives()github
b)

The first parameter is a required bean type. The remaining parameters are required qualifiers.

Coverage

org.jboss.cdi.tck.tests.extensions.bean.bytype
BeanByTypeTest.testGetBeans()github
c)

If no qualifiers are passed to getBeans(), the default qualifier @Default is assumed.

Coverage

org.jboss.cdi.tck.tests.extensions.bean.bytype
BeanByTypeTest.testNoBindingImpliesCurrent()github
da)

If the given type represents a type variable, an IllegalArgumentException is thrown.

Coverage

org.jboss.cdi.tck.tests.extensions.bean.bytype
BeanByTypeTest.testTypeVariable()github
e)

If two instances of the same qualifier type are given, an IllegalArgumentException is thrown.

Coverage

org.jboss.cdi.tck.tests.extensions.bean.bytype
BeanByTypeTest.testSameBindingTwice()github
f)

If an instance of an annotation that is not a qualifier type is given, an IllegalArgumentException is thrown.

Coverage

org.jboss.cdi.tck.tests.extensions.bean.bytype
BeanByTypeTest.testNonBindingType()github

Section 11.3.6 - Obtaining a Bean by name

aa)

The method BeanManager.getBeans() which accepts a string returns the set of beans which have the given EL name and are available for injection in the module or library containing the class into which the BeanManager was injected or the Java EE component from whose JNDI environment namespace the BeanManager was obtained, according to the rules of EL name resolution defined in Section 5.3, "EL name resolution".

Coverage

org.jboss.cdi.tck.tests.lookup.byname
ResolutionByNameTest.testAmbiguousELNamesResolved()github
b)

The parameter is an EL name.

Coverage

org.jboss.cdi.tck.tests.lookup.byname
ResolutionByNameTest.testAmbiguousELNamesResolved()github

Section 11.3.7 - Obtaining a passivation capable bean by identifier

a)

The method BeanManager.getPassivationCapableBean() returns the PassivationCapable bean with the given identifier (see Section 6.6.1, "Passivation capable beans").

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager
PassivationIdTest.testGetPassivationCapableBeanById()github

Section 11.3.8 - Resolving an ambiguous dependency

a)

The method BeanManager.resolve() applies the ambiguous dependency resolution rules defined in Section 5.2.1, "Unsatisfied and ambiguous dependencies" to a set of Beans.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager
BeanManagerTest.testAmbiguousDependencyResolved()github
b)

If the ambiguous dependency resolution rules fail, the container must throw an AmbiguousResolutionException.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager
BeanManagerTest.testAmbiguousDependencyNotResolved()github

The method BeanManager.resolve() must return null, if:

c)

null is passed to resolve(),

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager
BeanManagerTest.testResolveWithNull()github
d)

no beans are passed to resolve(),

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager
BeanManagerTest.testResolveWithEmptySet()github
e)

no bean is available for injection in the module (as defined in Section 5.1, "Modularity"").

Coverage

No tests exist for this assertion

Section 11.3.9 - Validating an injection point

a)Statement of intent

The BeanManager.validate() operation validates an injection point and throws an InjectionException if there is a deployment problem (for example, an unsatisfied or unresolvable ambiguous dependency) associated with the injection point.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager
BeanManagerTest.testValidateThrowsException()github
a)

The method validate() validates the dependency and throws an InjectionException if there is a deployment problem (for example, an unsatisfied or unresolvable ambiguous dependency) associated with the injection point.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager
BeanManagerTest.testValidateThrowsException()github

Section 11.3.10 - Firing an event

a)

The method BeanManager.fireEvent() fires an event and notifies observers, according to Section 10.5, "Observer notification".

Coverage

org.jboss.cdi.tck.tests.event.fires
FireEventTest.testBeanManagerFireEvent()github
b)

The first argument is the event object. The remaining parameters are event qualifiers.

Coverage

org.jboss.cdi.tck.tests.event.fires
FireEventTest.testBeanManagerFireEvent()github
c)

If the runtime type of the event object contains a type variable, an IllegalArgumentException is thrown.

Coverage

org.jboss.cdi.tck.tests.event.fires
FireEventTest.testTypeVariableEventTypeFails()github
d)

If two instances of the same qualifier type are given, an IllegalArgumentException is thrown.

Coverage

org.jboss.cdi.tck.tests.event.fires
FireEventTest.testDuplicateBindingsToFireEventFails()github
e)

If an instance of an annotation that is not a qualifier type is given, an IllegalArgumentException is thrown.

Coverage

org.jboss.cdi.tck.tests.event.fires.nonbinding
NonBindingTypePassedToFireTest.testExceptionThrownIfNonBindingTypePassedToFire()github
f)

If the runtime type of the event object is assignable to the type of a container lifecycle event, IllegalArgumentException is thrown.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager.broken.event
FireContainerLifecycleEventTest.testFireContainerLifecycleEvent()github

Section 11.3.11 - Observer method resolution

a)

The method BeanManager.resolveObserverMethods() resolves observer methods for an event according to the rules of observer resolution defined in Section 10.2, "Observer resolution".

Coverage

org.jboss.cdi.tck.tests.event.resolve.typeWithParameters
CheckTypeParametersWhenResolvingObserversTest.testResolvingChecksTypeParameters()github
org.jboss.cdi.tck.tests.event.observer.resolve
ResolveEventObserversTest.testBeanManagerResolveObserversSignature()github
b)

The first parameter of resolveObserverMethods() is the event object. The remaining parameters are event qualifiers.

Coverage

org.jboss.cdi.tck.tests.event.observer.resolve
ResolveEventObserversTest.testBeanManagerResolveObserversSignature()github
c)

If the runtime type of the event object contains a type variable, an IllegalArgumentException is thrown.

Coverage

org.jboss.cdi.tck.tests.event
EventTest.testEventObjectContainsTypeVariablesWhenResolvingFails()github
d)

If two instances of the same qualifier type are given, an IllegalArgumentException is thrown.

Coverage

org.jboss.cdi.tck.tests.event.resolve.binding
DuplicateBindingTypesWhenResolvingTest.testDuplicateBindingTypesWhenResolvingFails()github
e)

If an instance of an annotation that is not a qualifier type is given, an IllegalArgumentException is thrown.

Coverage

org.jboss.cdi.tck.tests.event.observer.resolve
ResolveEventObserversTest.testBeanManagerResolveObserversWithIllegalQualifier()github

Section 11.3.12 - Decorator resolution

a)

The method BeanManager.resolveDecorators() returns the ordered list of decorators for a set of bean types and a set of qualifiers which are enabled in the module or library containing the class into which the BeanManager was injected or the Java EE component from whose JNDI environment namespace the BeanManager was obtained, as defined in Section 8.3, "Decorator resolution".

Coverage

org.jboss.cdi.tck.tests.decorators.definition
DecoratorDefinitionTest.testDecoratedTypes()github
DecoratorDefinitionTest.testDecoratorOrdering()github
b)

The first argument is the set of bean types of the decorated bean. The annotations are qualifiers declared by the decorated bean.

Coverage

org.jboss.cdi.tck.tests.decorators.definition
DecoratorDefinitionTest.testDecoratedTypes()github
c)

If two instances of the same qualifier type are given, an IllegalArgumentException is thrown.

Coverage

org.jboss.cdi.tck.tests.decorators.definition
DecoratorDefinitionTest.testDuplicateBindingsOnResolveDecoratorsFails()github
d)

If an instance of an annotation that is not a qualifier type is given, an IllegalArgumentException is thrown.

Coverage

org.jboss.cdi.tck.tests.decorators.definition
DecoratorDefinitionTest.testNonBindingsOnResolveDecoratorsFails()github
e)

If the set of bean types is empty, an IllegalArgumentException is thrown.

Coverage

org.jboss.cdi.tck.tests.decorators.definition
DecoratorDefinitionTest.testEmptyTypeSetOnResolveDecoratorsFails()github
org.jboss.cdi.tck.tests.event.resolve.nonbinding
NonBindingTypesWhenResolvingTest.testNonBindingTypeAnnotationWhenResolvingFails()github

Section 11.3.13 - Interceptor resolution

a)

The method BeanManager.resolveInterceptors() returns the ordered list of interceptors for a set of interceptor bindings and a type of interception which are enabled in the module or library containing the class into which the BeanManager was injected or the Java EE component from whose JNDI environment namespace the BeanManager was obtained, as defined in Section 9.5, "Interceptor resolution".

Coverage

org.jboss.cdi.tck.tests.interceptors.definition
InterceptorDefinitionTest.testResolveInterceptorsReturnsOrderedList()github
b)

If two instances of the same interceptor binding type are given, an IllegalArgumentException is thrown.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition
InterceptorDefinitionTest.testSameBindingTypesToResolveInterceptorsFails()github
c)

If no interceptor binding type instance is given, an IllegalArgumentException is thrown.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition
InterceptorDefinitionTest.testNoBindingTypesToResolveInterceptorsFails()github
d)

If an instance of an annotation that is not an interceptor binding type is given, an IllegalArgumentException is thrown.

Coverage

org.jboss.cdi.tck.tests.interceptors.definition
InterceptorDefinitionTest.testNonBindingTypeToResolveInterceptorsFails()github

Section 11.3.14 - Determining if an annotation is a qualifier type, scope type, stereotype or interceptor binding type

A portable extension may test an annotation to determine if it is a qualifier type, scope type, stereotype or interceptor binding type, obtain the set of meta-annotations declared by a stereotype or interceptor binding type, or determine if a scope type is a normal or passivating scope.

aa)

Test qualifier type.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager
BeanManagerTest.testDetermineQualifierType()github
ab)

Test scope type.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager
BeanManagerTest.testDetermineScope()github
ac)

Test stereotype.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager
BeanManagerTest.testDetermineStereotype()github
ad)

Test interceptor binding type.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager
BeanManagerTest.testDetermineInterceptorBindingType()github
ae)

Test meta-annotations for stereotype.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager
BeanManagerTest.testGetMetaAnnotationsForStereotype()github
af)

Test meta-annotations for interceptor binding type.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager
BeanManagerTest.testGetMetaAnnotationsForInterceptorBindingType()github
ag)

Test obtaining a ScopeType.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager
BeanManagerTest.testDetermineScopeType()github

Section 11.3.15 - Determining the hash code and equivalence of qualifiers and interceptor bindings

A portable extension may determine if two qualifiers or two interceptor bindings are considered equivalent for the purposes of typesafe resolution, as defined in Section 5.2.1, "Performing typesafe resolution".

a)

Test equivalence of qualifiers using BeanManager.areQualifiersEquivalent().

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager.equivalence.qualifier
QualifierEquivalenceTest.testAreQualifiersEquivalent()github
b)

Test equivalence of interceptor bindings using BeanManager.areInterceptorBindingsEquivalent().

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager.equivalence.interceptorbinding
InterceptorBindingEquivalenceTest.testAreInterceptorBindingsEquivalent()github

A portable extension may determine the hash code of a qualifier or and interceptor binding, ignoring any members annotated with @Nonbinding.

c)

Determine the hash code of a qualifier using BeanManager.getQualifierHashCode().

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager.equivalence.qualifier
QualifierEquivalenceTest.testGetQualifierHashCode()github
d)

Determine the hash code of an interceptor binding using BeanManager.getInterceptorBindingHashCode().

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager.equivalence.interceptorbinding
InterceptorBindingEquivalenceTest.testGetInterceptorBindingHashCode()github

Section 11.3.16 - Obtaining the active Context for a scope

a)

The method BeanManager.getContext() retrieves an active context object associated with the a given scope, as defined in Section 6.5.1, "The active context object for a scope".

Coverage

org.jboss.cdi.tck.tests.context
ContextTest.testBuiltInContexts()github

Section 11.3.17 - Obtaining the ELResolver

a)

The method BeanManager.getELResolver() returns the javax.el.ELResolver specified in Section 12.4, "Integration with Unified EL".

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager
BeanManagerTest.testGetELResolver()github

Section 11.3.18 - Wrapping a Unified EL ExpressionFactory

a)

The method BeanManager.wrapExpressionFactory() returns a wrapper javax.el.ExpressionFactory that delegates MethodExpression and ValueExpression creation to the given ExpressionFactory.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager.el
WrapExpressionFactoryTest.testWrapping()github
b)

When a Unified EL expression is evaluated using a MethodExpression or ValueExpression returned by the wrapper ExpressionFactory, the rules defined in Section 6.4.3, "Dependent pseudo-scope and Unified EL" are enforced by the container.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager.el
WrapExpressionFactoryTest.testWrapping()github

Section 11.3.19 - Obtaining an AnnotatedType for a class

a)

The method BeanManager.createAnnotatedType() returns an AnnotatedType that may be used to read the annotations of a given Java class or interface.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager
BeanManagerTest.testObtainingAnnotatedType()github
b)

The method BeanManager.getAnnotatedType() returns the AnnotatedType discovered or added during container initialization.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager.annotated
GetAnnotatedTypesTest.testGetAnnotatedType()github
c)

The method BeanManager.getAnnotatedTypes() returns the AnnotatedTypes discovered or added during container initialization.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager.annotated
GetAnnotatedTypesTest.testGetAnnotatedTypes()github

Section 11.3.20 - Obtaining an InjectionTarget for a class

The method BeanManager.createInjectionTarget() returns a container provided implementation of InjectionTarget for a given AnnotatedType or throws an IllegalArgumentException if there is a definition error associated with any injection point of the type.

aa)

Check InjectionTarget is provided.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager
BeanManagerTest.testObtainingInjectionTarget()github
ab)

Check IllegalArgumentException is thrown.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager
BeanManagerTest.testObtainingInjectionTargetWithDefinitionError()github

Section 11.3.21 - Obtaining a Producer for a field or method

The method BeanManager.createProducer() returns a container provided implementation of Producer for a given AnnotatedMethod or AnnotatedField or throws an IllegalArgumentException if there is a definition error associated with the producer method or field.

a)

Test that the method BeanManager.createProducer() returns a container provided implementation of Producer for a given AnnotatedMethod.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager.producer
SyntheticProducerTest.testStaticProducerMethod()github
SyntheticProducerTest.testNonStaticProducerMethod()github
b)

Test that the method BeanManager.createProducer() returns a container provided implementation of Producer for a given AnnotatedField.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager.producer
SyntheticProducerTest.testStaticProducerField()github
SyntheticProducerTest.testNonStaticProducerField()github
c)

Test that the method BeanManager.createProducer() throws an IllegalArgumentException if there is a definition error associated with the producer method.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager.producer
SyntheticProducerTest.testInvalidProducerMethod1()github
SyntheticProducerTest.testInvalidProducerMethod2()github
d)

Test that the method BeanManager.createProducer() throws an IllegalArgumentException if there is a definition error associated with the producer field.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager.producer
SyntheticProducerTest.testInvalidProducerField1()github
SyntheticProducerTest.testInvalidProducerField2()github
SyntheticProducerTest.testInvalidProducerField3()github

Section 11.3.22 - Obtaining an InjectionPoint

The method BeanManager.createInjectionPoint() returns a container provided implementation of InjectionPoint for a given AnnotatedField or AnnotatedParameter or throws an IllegalArgumentException if there is a definition error associated with the injection point.

a)

Test that the method BeanManager.createInjectionPoint() returns a container provided implementation of InjectionPoint for a given AnnotatedField.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager.injectionPoint
CreateInjectionPointTest.testField()github
b)

Test that the method BeanManager.createInjectionPoint() returns a container provided implementation of InjectionPoint for a given AnnotatedParameter.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager.injectionPoint
CreateInjectionPointTest.testConstructorParameter()github
CreateInjectionPointTest.testMethodParameter()github
c)

Test that the method BeanManager.createInjectionPoint() throws an IllegalArgumentException if there is a definition error associated with the injection point.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager.injectionPoint
CreateInjectionPointTest.testInvalidField()github
CreateInjectionPointTest.testInvalidParameter()github

Section 11.3.23 - Obtaining a BeanAttributes

The method BeanManager.createBeanAttributes() returns a container provided implementation of BeanAttributes by reading the annotations of a given AnnotatedType or AnnotatedMember, according to the rules define in Chapter 2, Concepts, or throws an IllegalArgumentException if there is a definition error associated with the declared bean attributes.

a)

Test that the method BeanManager.createBeanAttributes() returns a container provided implementation of BeanAttributes by reading the annotations of a given AnnotatedType.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager.beanAttributes
CreateBeanAttributesTest.testBeanAttributesForManagedBean()github
CreateBeanAttributesTest.testBeanAttributesForManagedBeanWithModifiedAnnotatedType()github
CreateBeanAttributesTest.testBeanAttributesForSessionBean()github
org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes.synthetic
ProcessBeanAttributesFiredForSyntheticBeanTest.testProcessBeanAttributesFired()github
b)

Test that the method BeanManager.createBeanAttributes() returns a container provided implementation of BeanAttributes by reading the annotations of a given AnnotatedMember.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager.beanAttributes
CreateBeanAttributesTest.testBeanAttributesForMethod()github
CreateBeanAttributesTest.testBeanAttributesForField()github
c)

Test that the method BeanManager.createBeanAttributes() throws an IllegalArgumentException if there is a definition error associated with the declared bean attributes.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager.beanAttributes
CreateBeanAttributesTest.testInvalidMember()github

Section 11.3.24 - Obtaining a Bean

The method BeanManager.createBean() returns a container provided implementation of Bean. The method accepts a BeanAttributes, which determines the bean types, qualifiers, scope, name and stereotypes of the returned Bean, and the return values of isAlternative() and isNullable(), and a class, which determines the return value of Bean.getClass().

a)

Test the first version of the method BeanManager.createBean() that also accepts an InjectionTarget, which is used to create and destroy instances of the bean, to perform dependency injection and lifecycle callbacks, and which determines the return value of Bean.getInjectionPoints().

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager.bean
SyntheticBeanTest.testRegisteredBean()github
SyntheticBeanTest.testSerializableBean()github
SyntheticBeanTest.testSyntheticDecorator()github
b)

Test the second version of the method BeanManager.createBean() that also accepts a Producer, which is used to create and destroy instances of the bean, and which determines the return value of Bean.getInjectionPoints().

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager.bean
SyntheticBeanTest.testSyntheticProducerField()github
SyntheticBeanTest.testSyntheticProducerMethod()github

Section 11.3.25 - Obtaining the instance of an Extension

The method BeanManager.getExtension() returns the container's instance of an Extension class declared in META-INF/services, or throws an IllegalArgumentException if the container has no instance of the given class.

a)

Test that the method BeanManager.getExtension() returns the container's instance of an Extension class declared in META-INF/services.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager
BeanManagerTest.testGetExtension()github
b)

Test that the method BeanManager.getExtension() throws an IllegalArgumentException if the container has no instance of the given class.

Coverage

org.jboss.cdi.tck.tests.extensions.beanManager
BeanManagerTest.testGetExtension()github

Section 11.4 - Alternative metadata sources

a)Statement of intent. In fact some assertions in this section do test metadata constructed by container as defined in sections

The interfaces AnnotatedType, AnnotatedField, AnnotatedMethod, AnnotatedConstructor and AnnotatedParameter in the package javax.enterprise.inject.spi allow a portable extension to specify metadata that overrides the annotations that exist on a bean class. The portable extension is responsible for implementing the interfaces, thereby exposing the metadata to the container.

The interface javax.enterprise.inject.spi.AnnotatedType exposes the Class object and members.

aaa)

Test that getConstructors() returns all the constructors declared for the type.

Coverage

org.jboss.cdi.tck.tests.extensions.annotated
AlternativeMetaDataTest.testConstructors()github
aab)

Test that getMethods() returns all the methods declared on the type and those declared on any supertypes.

Coverage

org.jboss.cdi.tck.tests.extensions.annotated
AlternativeMetaDataTest.testMethods()github
aac)

Test that getFields() returns all the fields declared on the type and those declared on any supertypes.

Coverage

org.jboss.cdi.tck.tests.extensions.annotated
AlternativeMetaDataTest.testFields()github
b)

When determining annotations on a type, the container must only consider the special inheritance rules defined for scope types in Section 4.1, "Inheritance of type-level metadata".

Coverage

org.jboss.cdi.tck.tests.extensions.alternative.metadata.annotated
AnnotatedTypeAnnotationsTest.testCreateAnnotatedType()github
AnnotatedTypeAnnotationsTest.testProcessAnnotatedType()github
AnnotatedTypeAnnotationsTest.testGetAnnotatedType()github
AnnotatedTypeAnnotationsTest.testGetAnnotatedTypes()github

The interface javax.enterprise.inject.spi.Annotated exposes the overriding annotations and type declarations.

c)

getBaseType() returns the type of the program element.

Coverage

org.jboss.cdi.tck.tests.extensions.annotated
AlternativeMetaDataTest.testBaseType()github
d)

getTypeClosure() returns all types to which the base type should be considered assignable.

Coverage

org.jboss.cdi.tck.tests.extensions.annotated
AlternativeMetaDataTest.testTypeClosure()github
e)

getAnnotation() returns the program element annotation of the given annotation type, or a null value.

Coverage

org.jboss.cdi.tck.tests.extensions.annotated
AlternativeMetaDataTest.testGetAnnotation()github
f)

getAnnotations() returns all annotations of the program element.

Coverage

org.jboss.cdi.tck.tests.extensions.annotated
AlternativeMetaDataTest.testGetAnnotations()github
g)

isAnnotationPresent() returns true if the program element has an annotation of the given annotation type, or false otherwise.

Coverage

org.jboss.cdi.tck.tests.extensions.annotated
AlternativeMetaDataTest.testIsAnnotationPresent()github
ga)

If the Annotated represents a type, then the annotations returned should include all annotations on the type and it's super types regardless of whether the annotation is marked @Inherited.

Coverage

org.jboss.cdi.tck.tests.extensions.annotated
AlternativeMetaDataTest.testGetAnnotations()github

The container must use the operations of Annotated and its subinterfaces to discover program element types and annotations. The container must not directly call the Java Reflection API. In particular, the container must call Annotated.getBaseType() to determine the type of an injection point, event parameter or disposed parameter, call Annotated.getTypeClosure() to determine the bean types of any kind of bean, call Annotated.getAnnotations() to determine the scope, qualifiers, stereotypes and interceptor bindings of a bean, call Annotated.isAnnotationPresent() and Annotated.getAnnotation() to read any bean annotations defined by this specification, and call AnnotatedType.getConstructors(), AnnotatedType.getMethods() and AnnotatedType.getFields() to determine the members of a bean class.

h)

Check that the container uses the operations of Annotated and its subinterfaces to discover program element types and annotations. and that the container does not use the Java Reflection API.

Coverage

org.jboss.cdi.tck.tests.extensions.alternative.metadata
AlternativeMetadataTest.testContainerUsesOperationsOfAnnotatedNotReflectionApi()github
ha)

Check that getBaseType() is used to determine the type of a field injection point. The base type should be different from the orignal type specified in the class definition

Coverage

org.jboss.cdi.tck.tests.extensions.alternative.metadata
AlternativeMetadataTest.testGetBaseTypeUsedToDetermineTypeOfInjectionPoint()github
hb)

Check that getBaseType() is used to determine the type of an initializer method injection point. The base type should be different from the orignal type specified in the class definition

Coverage

org.jboss.cdi.tck.tests.extensions.alternative.metadata
AlternativeMetadataTest.testGetBaseTypeUsedToDetermineTypeOfInitializerInjectionPoint()github
hc)

Check that getBaseType() is used to determine the type of a constructor injection point. The base type should be different from the orignal type specified in the class definition

Coverage

No tests exist for this assertion

hd)

Check that getBaseType() is used to determine the type of a producer method injection point. The base type should be different from the orignal type specified in the class definition

Coverage

No tests exist for this assertion

he)

Check that getBaseType() is used to determine the type of a observer method injection point. The base type should be different from the orignal type specified in the class definition

Coverage

No tests exist for this assertion

hf)

Check that getBaseType() is used to determine the type of a disposer method injection point. The base type should be different from the orignal type specified in the class definition

Coverage

No tests exist for this assertion

i)

Check that getBaseType() is used to determine the type of an event parameter. The base type should be different from the orignal type specified in the class definition

Coverage

No tests exist for this assertion

j)

Check that getBaseType() is used to determine the type of disposed parameter. The base type should be different from the orignal type specified in the class definition

Coverage

No tests exist for this assertion

ka)

Check that a getTypeClosure() is used to determine the bean types for a managed bean. The type closure should be different from the orignal type specified in the class definition.

Coverage

org.jboss.cdi.tck.tests.extensions.alternative.metadata
AlternativeMetadataTest.testGetTypeClosureUsed()github
kb)

Check that a getTypeClosure() is used to determine the bean types for a session bean. The type closure should be different from the orignal type specified in the class definition.

Coverage

No tests exist for this assertion

kc)

Check that a getTypeClosure() is used to determine the bean types for a producer field. The type closure should be different from the orignal type specified in the class definition.

Coverage

No tests exist for this assertion

kd)

Check that a getTypeClosure() is used to determine the bean types for a producer method. The type closure should be different from the orignal type specified in the class definition.

Coverage

No tests exist for this assertion

l)

Check that getAnnotations() is used to determine the bean scope. The annotations should be different from the orignal type specified in the class definition.

Coverage

org.jboss.cdi.tck.tests.extensions.alternative.metadata
AlternativeMetadataTest.testGetAnnotationUsedForGettingScopeInformation()github
m)

Check that getAnnotations() is used to determine the bean qualifiers. The annotations should be different from the orignal type specified in the class definition.

Coverage

org.jboss.cdi.tck.tests.extensions.alternative.metadata
AlternativeMetadataTest.testGetAnnotationUsedForGettingQualifierInformation()github
n)

Check that getAnnotations() is used to determine the bean stereotypes. The annotations should be different from the orignal type specified in the class definition.

Coverage

org.jboss.cdi.tck.tests.extensions.alternative.metadata
AlternativeMetadataTest.testGetAnnotationUsedForGettingStereotypeInformation()github
p)

Check that getAnnotations() is used to determine the bean interceptors. The annotations should be different from the orignal type specified in the class definition.

Coverage

org.jboss.cdi.tck.tests.extensions.alternative.metadata
AlternativeMetadataTest.testGetAnnotationUsedForGettingInterceptorInformation()github
q)No testable behavior

Check that isAnnotationPresent() returns the provided annotations

r)

Check that a previously non-inject-annotated constructor is used by the container to instantiate a bean.

Coverage

org.jboss.cdi.tck.tests.extensions.alternative.metadata
AlternativeMetadataTest.testPreviouslyNonInjectAnnotatedConstructorIsUsed()github
s)

Check that a qualifier added to a parameter is used by the container to instantiate a bean.

Coverage

No tests exist for this assertion

t)

Check that a previously non-inject-annotated field is injected.

Coverage

org.jboss.cdi.tck.tests.extensions.alternative.metadata
AlternativeMetadataTest.testPreviouslyNonInjectAnnotatedFieldIsInjected()github
u)

Check that an extra qualifier is applied.

Coverage

org.jboss.cdi.tck.tests.extensions.alternative.metadata
AlternativeMetadataTest.testExtraQualifierIsAppliedToInjectedField()github
v)

Check that @Produces added creates a producer field.

Coverage

org.jboss.cdi.tck.tests.extensions.alternative.metadata
AlternativeMetadataTest.testProducesCreatesProducerField()github
w)

Check that a previously non-inject-annotated method is injected.

Coverage

org.jboss.cdi.tck.tests.extensions.alternative.metadata
AlternativeMetadataTest.testInjectCreatesInitializerMethod()github
x)

Check that an extra qualifier is applied to an injectable method

Coverage

org.jboss.cdi.tck.tests.extensions.alternative.metadata
AlternativeMetadataTest.testQualifierAddedToInitializerParameter()github
y)

Check that @Produces added creates a producer method

Coverage

org.jboss.cdi.tck.tests.extensions.alternative.metadata
AlternativeMetadataTest.testProducesCreatesProducerMethod()github
z)

Check that an extra qualifier is applied to a producer method.

Coverage

org.jboss.cdi.tck.tests.extensions.alternative.metadata
AlternativeMetadataTest.testQualifierIsAppliedToProducerMethod()github
aa)

Check that a qualifer added to a producer method parameter is applied.

Coverage

org.jboss.cdi.tck.tests.extensions.alternative.metadata
AlternativeMetadataTest.testQualifierIsAppliedToProducerMethodParameter()github
ab)

Check that @Disposes added to a parameter creates a disposes method

Coverage

No tests exist for this assertion

ac)

Check that an extra qualifier is applied to a disposes method parameter.

Coverage

No tests exist for this assertion

ad)

Check that a qualifer added to a disposes method injectable parameter is applied.

Coverage

No tests exist for this assertion

ae)

Check that @Observes added to a parameter creates a observer method

Coverage

org.jboss.cdi.tck.tests.extensions.alternative.metadata
AlternativeMetadataTest.testObserverMethod()github
af)

Check that an extra qualifier is applied to an observes method parameter.

Coverage

org.jboss.cdi.tck.tests.extensions.alternative.metadata
AlternativeMetadataTest.testExtraQualifierAppliedToObservesMethodParameter()github
ag)

Check that a qualifer added to a observes method injectable parameter is applied.

Coverage

org.jboss.cdi.tck.tests.extensions.alternative.metadata
AlternativeMetadataTest.testObserverMethod()github

Section 11.5 - Container lifecycle events

a)Generic statement

During the application initialization process, the container fires a series of events, allowing portable extensions to integrate with the container initialization process defined in Section 12.2, "Application initialization lifecycle".

b)

Observer methods of these events must belong to extensions. An extension is a service provider of the service javax.enterprise.inject.spi.Extension declared in META-INF/services.

Coverage

org.jboss.cdi.tck.tests.deployment.packaging.visibility
VisibilityOfAnnotatedTypesFromExtensionInBravoBeanArchiveTest.shouldObserveExpectedAnnotatedTypes()github
VisibilityOfAnnotatedTypesFromExtensionInAlphaBeanArchiveTest.shouldObserveExpectedAnnotatedTypes()github
org.jboss.cdi.tck.tests.extensions.registration
BeanRegistrationByExtensionInNonBeanArchiveTest.shouldFindBeanReference()github
org.jboss.cdi.tck.tests.extensions.interceptors
InterceptorExtensionTest.testInterceptorCalled()github
InterceptorExtensionTest.testLifecycleInterceptor()github
org.jboss.cdi.tck.tests.extensions.registration
VisibilityOfBeanRegisteredByExtensionFromNonBeanLibraryTest.shouldFindBeanReference()github
bb)

Service providers may have observer methods, which may observer any event, including any container lifecycle event, and obtain an injected BeanManager reference.

Coverage

org.jboss.cdi.tck.tests.deployment.packaging.war.modules
WebArchiveModulesTest.testExtensionAndContainerEvents()github
org.jboss.cdi.tck.tests.extensions.registration
BeanRegistrationByExtensionInNonBeanArchiveTest.shouldFindBeanReference()github
org.jboss.cdi.tck.tests.extensions.lifecycle
ExtensionLifecycleTest.testContainerDeliversEventNotifications()github
org.jboss.cdi.tck.tests.extensions.interceptors
InterceptorExtensionTest.testInterceptorCalled()github
InterceptorExtensionTest.testLifecycleInterceptor()github
org.jboss.cdi.tck.tests.extensions.registration
VisibilityOfBeanRegisteredByExtensionFromNonBeanLibraryTest.shouldFindBeanReference()github
bc)

An extension may use BeanManager.fireEvent() to deliver events to observer methods defined on extensions.

Coverage

org.jboss.cdi.tck.tests.extensions.communication
ExtensionsCommunicationTest.testEvents()github
bd)Non-portable behavior

The container is not required to deliver events fired during application initialization to observer methods defined on beans.

be)

Any decorators associated with BeanManager will not be applied.

Coverage

org.jboss.cdi.tck.tests.decorators.builtin.beanmanager
BeanManagerDecoratorTest.testDecoratorIsNotApplied()github
d)

The container instantiates a single instance of each extension at the beginning of the application initialization process and maintains a reference to it until the application shuts down. The container delivers event notifications to this instance by calling its observer methods.

Coverage

org.jboss.cdi.tck.tests.extensions.lifecycle
ExtensionLifecycleTest.testContainerInstantiatesSingleInstanceOfExtension()github
ExtensionLifecycleTest.testContainerDeliversEventNotifications()github
e)

For each service provider, the container must provide a bean of scope @ApplicationScoped and qualifier @Default, supporting injection of a reference to the service provider instance. The bean types of this bean include the class of the service provider and all superclases and interfaces.

Coverage

org.jboss.cdi.tck.tests.extensions.lifecycle
ExtensionLifecycleTest.testContainerProvidesBeanForExtension()github
ExtensionLifecycleTest.testContainerInstantiatesSingleInstanceOfExtension()github
ExtensionLifecycleTest.testContainerDeliversEventNotifications()github

Section 11.5.1 - BeforeBeanDiscovery event

a)

The container must fire an event before it begins the bean discovery process. The event object must be of type javax.enterprise.inject.spi.BeforeBeanDiscovery.

Coverage

org.jboss.cdi.tck.tests.deployment.lifecycle
ExtensionsTest.testBeforeBeanDiscoveryEventIsCalled()github
ab)

addQualifier() declares an annotation type as a qualifier type.

Coverage

org.jboss.cdi.tck.tests.deployment.lifecycle
ExtensionsTest.testAddingBindingType()github
ac)

addScope() declares an annotation type as a scope type.

Coverage

org.jboss.cdi.tck.tests.deployment.lifecycle
ExtensionsTest.testAddingScopeType()github
org.jboss.cdi.tck.tests.deployment.lifecycle.broken.normalScope
AddingNormalScopeTest.testAddingScopeType()github
org.jboss.cdi.tck.tests.deployment.lifecycle.broken.passivatingScope
AddingPassivatingScopeTest.testAddingScopeType()github
ad)

addStereotype() declares an annotation type as a stereotype, and specifies its meta-annotations.

Coverage

org.jboss.cdi.tck.tests.extensions.stereotype
StereotypeExtensionTest.testStereotypeWorks()github
ae)

addInterceptorBinding() declares an annotation type as an interceptor binding type, and specifies its meta-annotations.

Coverage

org.jboss.cdi.tck.tests.extensions.interceptors
InterceptorExtensionTest.testInterceptorCalled()github
InterceptorExtensionTest.testLifecycleInterceptor()github

addAnnotatedType() adds a given AnnotatedType to the set of types which will be scanned during bean discovery. More than one AnnotatedType may use the same base type, and the container must consider these as different types.

af)

Test the addAnnotatedType() method.

Coverage

org.jboss.cdi.tck.tests.extensions.registration
BeanRegistrationByExtensionInNonBeanArchiveTest.shouldFindBeanReference()github
VisibilityOfBeanRegisteredByExtensionFromNonBeanLibraryTest.shouldFindBeanReference()github
afa)

Test that more than one AnnotatedType may use the same base type.

Coverage

No tests exist for this assertion

ag)

If any observer method of the BeforeBeanDiscovery event throws an exception, the exception is treated as a definition error by the container.

Coverage

org.jboss.cdi.tck.tests.deployment.lifecycle.broken.beanDiscoveryMethodThrowsException
BeforeBeanDiscoveryThrowsExceptionTest.testThrowsException()github

Section 11.5.2 - AfterBeanDiscovery event

a)

The container must fire a second event when it has fully completed the bean discovery process, validated that there are no definition errors relating to the discovered beans, and registered Bean and ObserverMethod objects for the discovered beans, but before detecting deployment problems. The event object must be of type javax.enterprise.inject.spi.AfterBeanDiscovery.

Coverage

org.jboss.cdi.tck.tests.deployment.lifecycle
DeploymentTest.testDeployedManagerEvent()github
ca)

addDefinitionError() registers a definition error with the container, causing the container to abort deployment after all observers have been notified.

Coverage

org.jboss.cdi.tck.tests.deployment.lifecycle.broken.addDefinitionError
AddDefinitionErrorTest.testObserverDefinitionErrorTreatedAsDefinitionError()github

addBean() fires an event of type ProcessBean containing the given Bean and then registers the Bean with the container, thereby making it available for injection into other beans. The given Bean may implement Interceptor or Decorator.

da)

Check that ProcessBean is fired

Coverage

org.jboss.cdi.tck.tests.extensions.afterBeanDiscovery
AfterBeanDiscoveryTest.testProcessBeanIsFired()github
db)

Check that a bean is registered

Coverage

org.jboss.cdi.tck.tests.extensions.afterBeanDiscovery
AfterBeanDiscoveryTest.testBeanIsAdded()github
dc)

Check that a decorator is registered

Coverage

org.jboss.cdi.tck.tests.decorators.custom
CustomDecoratorTest.testCustomImplementationOfDecoratorInterface()github
dd)

Check that an interceptor is registered

Coverage

org.jboss.cdi.tck.tests.interceptors.definition.custom
CustomInterceptorTest.testCustomPostConstructInterceptor()github
CustomInterceptorTest.testCustomPreDestroyInterceptor()github
CustomInterceptorTest.testCustomPostActivateInterceptor()github
CustomInterceptorTest.testCustomPrePassivateInterceptor()github
CustomInterceptorTest.testCustomAroundInvokeInterceptor()github
CustomInterceptorTest.testCustomAroundTimeoutInterceptor()github
org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes.synthetic.interceptor
SyntheticInterceptorVetoedTest.testSyntheticInterceptorBeanCanBeVetoed()github
org.jboss.cdi.tck.tests.extensions.interceptors.custom
CustomInterceptorRegistrationTest.testCustomInterceptorRegistration()github
CustomInterceptorInvocationTest.testCustomInterceptorInvocation()github

addObserverMethod() fires an event of type ProcessObserverMethod containing the given ObserverMethod and then registers the ObserverMethod with the container, thereby making it available for event notifications.

ea)

Check that the ProcessObserverMethod is fired

Coverage

org.jboss.cdi.tck.tests.extensions.afterBeanDiscovery
AfterBeanDiscoveryTest.testProcessObserverMethodFiredWhileAddingObserverMethod()github
eb)

Check that the observer method is registered

Coverage

org.jboss.cdi.tck.tests.extensions.afterBeanDiscovery
AfterBeanDiscoveryTest.testObserverMethodRegistered()github
org.jboss.cdi.tck.tests.event.observer.extension
EventBeanObserverNotificationTest.testNoQualifier()github
EventBeanObserverNotificationTest.testSingleQualifier()github
EventBeanObserverNotificationTest.testMultipleQualifiers()github
f)Right now only the registation process is tested

addContext() registers a custom Context object with the container.

Coverage

org.jboss.cdi.tck.tests.extensions.afterBeanDiscovery
AfterBeanDiscoveryTest.testAddContext()github
fb)See d*, e* and f

A portable extension may take advantage of this event to register beans, interceptors, decorators, observer methods and custom context objects with the container.

g)

If any observer method of the AfterBeanDiscovery event throws an exception, the exception is treated as a definition error by the container.

Coverage

org.jboss.cdi.tck.tests.deployment.lifecycle.broken.exceptionInAfterBeanDiscoveryObserver
AfterBeanDiscoveryObserverExecutionFailureTest.testObserverFailureTreatedAsDefinitionError()github

Section 11.5.3 - AfterDeploymentValidation event

a)

The container must fire a third event after it has validated that there are no deployment problems and before creating contexts or processing requests. The event object must be of type javax.enterprise.inject.spi.AfterDeploymentValidation.

Coverage

org.jboss.cdi.tck.tests.deployment.lifecycle
DeploymentTest.testDeployedManagerEvent()github
b)

addDeploymentProblem() registers a deployment problem with the container, causing the container to abort deployment after all observers have been notified.

Coverage

org.jboss.cdi.tck.tests.deployment.lifecycle.broken.addDeploymentProblem
AddDeploymentProblemTest.testObserverDeploymentProblemTreatedAsDeploymentError()github
c)

If any observer method of the AfterDeploymentValidation event throws an exception, the exception is treated as a deployment problem by the container.

Coverage

org.jboss.cdi.tck.tests.deployment.lifecycle.broken.exceptionInAfterBeanValidationObserver
AfterDeploymentValidationObserverExecutionFailureTest.testObserverFailureTreatedAsDeploymentError()github
d)

The container must not allow any request to be processed by the deployment until all observers of this event return.

Coverage

No tests exist for this assertion

Section 11.5.4 - BeforeShutdown event

a)

The container must fire a final event after it has finished processing requests and destroyed all contexts. The event object must be of type javax.enterprise.inject.spi.BeforeShutdown.

Coverage

org.jboss.cdi.tck.tests.deployment.shutdown
ApplicationShutdownLifecycleTest.testShutdown()github
ba)This is not testable in a portable way - the only way would be to check successful undeploy.

If any observer method of the BeforeShutdown event throws an exception, the exception is ignored by the container.

Section 11.5.5 - ProcessModule event

a)

The container must fire an event for each bean deployment archive, before it processes the classes packaged in that module. The event object must be of type javax.enterprise.inject.spi.ProcessModule.

Coverage

org.jboss.cdi.tck.tests.extensions.modules
SingleModuleProcessingTest.testProcessedModulesCount()github
MultiModuleProcessingTest.testProcessedModulesCount()github
ba)

getAlternatives() returns the set of enabled alternatives of the bean deployment archive.

Coverage

org.jboss.cdi.tck.tests.extensions.modules
SingleModuleProcessingTest.testAlternatives()github
bb)

getInterceptors() returns the list of enabled interceptors of the bean deployment archive.

Coverage

org.jboss.cdi.tck.tests.extensions.modules
SingleModuleProcessingTest.testInterceptors()github
bc)

getDecorators() returns the list of enabled decorators of the bean deployment archive.

Coverage

org.jboss.cdi.tck.tests.extensions.modules
SingleModuleProcessingTest.testDecorators()github
bd)

getAnnotatedTypes() returns an iterator over AnnotatedType objects representing the Java classes and interfaces in the bean archive.

Coverage

org.jboss.cdi.tck.tests.extensions.modules
SingleModuleProcessingTest.testAnnotatedTypes()github
be)

getBeansXml() returns an input stream which can be used to read in the beans.xml for this module.

Coverage

org.jboss.cdi.tck.tests.extensions.modules
SingleModuleProcessingTest.testBeansXml()github

Any observer of this event is permitted to add classes to, or remove classes from, the set of alternatives, list of interceptors or list of decorators. The container must use the final values of these collections, after all observers have been called, to determine the enabled alternatives, interceptors, and decorators for the bean deployment archive. The initial values of these collections is determined by reading the beans.xml file of the bean deployment archive.

ca)

Check observer is permitted to add classes to the set of alternatives and the container reflects this operation.

Coverage

org.jboss.cdi.tck.tests.extensions.modules
SingleModuleProcessingTest.testAlternatives()github
cb)

Check observer is permitted to remove classes from the set of alternatives and the container reflects this operation.

Coverage

org.jboss.cdi.tck.tests.extensions.modules
SingleModuleProcessingTest.testAlternatives()github
cc)

Check observer is permitted to add classes to the list of interceptors and the container reflects this operation.

Coverage

org.jboss.cdi.tck.tests.extensions.modules
SingleModuleProcessingTest.testInterceptors()github
cd)

Check observer is permitted to remove classes from the list of interceptors and the container reflects this operation.

Coverage

org.jboss.cdi.tck.tests.extensions.modules
SingleModuleProcessingTest.testInterceptors()github
ce)

Check observer is permitted to add classes to the list of decorators and the container reflects this operation.

Coverage

org.jboss.cdi.tck.tests.extensions.modules
SingleModuleProcessingTest.testDecorators()github
cf)

Check observer is permitted to remove classes from the list of decorators and the container reflects this operation.

Coverage

org.jboss.cdi.tck.tests.extensions.modules
SingleModuleProcessingTest.testDecorators()github
cg)

Check the initial values are determined by reading the beans.xml file of the bean deployment archive.

Coverage

org.jboss.cdi.tck.tests.extensions.modules
MultiModuleProcessingTest.test()github
d)

If any observer method of a ProcessModule event throws an exception, the exception is treated as a deployment problem by the container.

Coverage

org.jboss.cdi.tck.tests.extensions.modules.broken
ProblematicExtensionTest.testDeployment()github
e)Implied - see 9.4. Interceptor enablement and ordering

If the final list of enabled interceptors of the bean deployment archive contains duplicate elements, the container automatically detects the problem and treats it as a deployment problem.

Coverage

org.jboss.cdi.tck.tests.extensions.modules.broken
DuplicateInterceptorTest.testDeployment()github
f)Implied - see 8.2. Decorator enablement and ordering

If the final list of enabled decorators of the bean deployment archive contains duplicate elements, the container automatically detects the problem and treats it as a deployment problem.

Coverage

org.jboss.cdi.tck.tests.extensions.modules.broken
DuplicateDecoratorTest.testDeployment()github

Section 11.5.6 - ProcessAnnotatedType event

The container must fire an event, before it processes a type, for each Java class, interface, enum or annotation discovered in a bean archive, Annotated type added by BeforeBeanDiscovery.addAnnotatedType(), annotation added by BeforeBeanDiscovery.addInterceptorBinding(), BeforeBeanDiscovery.addQualifier(), BeforeBeanDiscovery.addScope() or BeforeBeanDiscovery.addStereotype().

aa)

Test class discovered in a bean archive.

Coverage

org.jboss.cdi.tck.tests.extensions.annotated
ProcessAnnotatedTypeTest.testProcessAnnotatedTypeEventsSent()github
ab)

Test interface discovered in a bean archive.

Coverage

org.jboss.cdi.tck.tests.extensions.annotated
ProcessAnnotatedTypeTest.testProcessAnnotatedTypeEventsSent()github
ac)

Test enum discovered in a bean archive.

Coverage

org.jboss.cdi.tck.tests.extensions.annotated
ProcessAnnotatedTypeTest.testProcessAnnotatedTypeFiredForEnum()github
ad)

Test annotation discovered in a bean archive.

Coverage

org.jboss.cdi.tck.tests.extensions.annotated
ProcessAnnotatedTypeTest.testProcessAnnotatedTypeFiredForAnnotation()github
ae)

Test class added by BeforeBeanDiscovery.addAnnotatedType().

Coverage

org.jboss.cdi.tck.tests.extensions.annotated.synthetic
ProcessSyntheticAnnotatedTypeTest.testEventsFired()github
af)

Test interface added by BeforeBeanDiscovery.addAnnotatedType().

Coverage

org.jboss.cdi.tck.tests.extensions.annotated.synthetic
ProcessSyntheticAnnotatedTypeTest.testEventsFired()github
ag)

Test enum added by BeforeBeanDiscovery.addAnnotatedType().

Coverage

No tests exist for this assertion

ah)

Test annotation added by BeforeBeanDiscovery.addInterceptorBinding(), BeforeBeanDiscovery.addQualifier(), BeforeBeanDiscovery.addScope() and BeforeBeanDiscovery.addStereotype().

Coverage

No tests exist for this assertion

An event is not fired for any type annotated with @Vetoed, or in a package annotated with @Vetoed.

ia)

Test @Vetoed class discovered in a bean archive.

Coverage

org.jboss.cdi.tck.tests.vetoed.enterprise
EnterpriseVetoedTest.testClassLevelVeto()github
org.jboss.cdi.tck.tests.vetoed
VetoedTest.testClassLevelVeto()github
ib)

Test @Vetoed interface discovered in a bean archive.

Coverage

org.jboss.cdi.tck.tests.vetoed
VetoedTest.testClassLevelVeto()github
ic)

Test @Vetoed enum discovered in a bean archive.

Coverage

org.jboss.cdi.tck.tests.vetoed
VetoedTest.testVetoedEnum()github
id)

Test @Vetoed annotation discovered in a bean archive.

Coverage

org.jboss.cdi.tck.tests.vetoed
VetoedTest.testVetoedAnnotation()github
ie)

Test @Vetoed class added by BeforeBeanDiscovery.addAnnotatedType().

Coverage

org.jboss.cdi.tck.tests.vetoed.enterprise
EnterpriseVetoedTest.testAnnotatedTypeAddedByExtension()github
org.jboss.cdi.tck.tests.vetoed
VetoedTest.testAnnotatedTypeAddedByExtension()github
if)

Test @Vetoed interface added by BeforeBeanDiscovery.addAnnotatedType().

Coverage

org.jboss.cdi.tck.tests.vetoed
VetoedTest.testAnnotatedTypeAddedByExtension()github
ig)

Test @Vetoed enum added by BeforeBeanDiscovery.addAnnotatedType().

Coverage

No tests exist for this assertion

ih)

Test @Vetoed annotation added by BeforeBeanDiscovery.addInterceptorBinding(), BeforeBeanDiscovery.addQualifier(), BeforeBeanDiscovery.addScope() and BeforeBeanDiscovery.addStereotype().

Coverage

No tests exist for this assertion

ii)

Test @Vetoed package.

Coverage

org.jboss.cdi.tck.tests.vetoed
VetoedTest.testPackageLevelVeto()github

The annotation @WithAnnotations may be applied to the event parameter. If the annotation is applied, the container must only deliver ProcessAnnotatedType events for types which contain at least one of the annotations specified. The annotation can appear on the type, on any field, method or constructor declared by the type, or on any parameter of any method or constructor declared by the type.

fa)

Test annotation on the type.

Coverage

org.jboss.cdi.tck.tests.extensions.annotated.delivery
WithAnnotationsTest.testDelivery()github
WithAnnotationsTest.testDeliveryMetaAnnotation()github
fb)

Test annotation on the field.

Coverage

org.jboss.cdi.tck.tests.extensions.annotated.delivery
WithAnnotationsTest.testDelivery()github
fc)

Test annotation on the method.

Coverage

org.jboss.cdi.tck.tests.extensions.annotated.delivery
EnterpriseWithAnnotationsTest.testDelivery()github
EnterpriseWithAnnotationsTest.testDeliveryMetaAnnotation()github
WithAnnotationsTest.testDelivery()github
fd)

Test annotation on the constructor.

Coverage

org.jboss.cdi.tck.tests.extensions.annotated.delivery
WithAnnotationsTest.testDelivery()github
fe)

Test annotation on the parameter of the method.

Coverage

org.jboss.cdi.tck.tests.extensions.annotated.delivery
WithAnnotationsTest.testDelivery()github
ff)

Test annotation on the parameter of the constructor.

Coverage

org.jboss.cdi.tck.tests.extensions.annotated.delivery
WithAnnotationsTest.testDelivery()github
g)

The annotation may be applied as a meta-annotation on any annotation considered.

Coverage

org.jboss.cdi.tck.tests.extensions.annotated.delivery
EnterpriseWithAnnotationsTest.testDeliveryMetaAnnotation()github
WithAnnotationsTest.testDeliveryMetaAnnotation()github
h)

If the @WithAnnotations annotation is applied to any other event parameter, the container automatically detects the problem and treats it as a definition error.

Coverage

org.jboss.cdi.tck.tests.extensions.annotated.delivery.broken
WithAnnotationsAppliedToIllegalEventParameterTest.testDeploymentFails()github
WithAnnotationsAppliedToIllegalContainerLifecycleEventParameterTest.testDeploymentFails()github
ba)

getAnnotatedType() returns the AnnotatedType object that will be used by the container to read the declared annotations.

Coverage

org.jboss.cdi.tck.tests.extensions.annotated
ProcessAnnotatedTypeTest.testGetAnnotatedType()github
bb)

setAnnotatedType() replaces the AnnotatedType.

Coverage

org.jboss.cdi.tck.tests.extensions.annotated
ProcessAnnotatedTypeTest.testSetAnnotatedType()github
bc)

veto() forces the container to ignore the type.

Coverage

org.jboss.cdi.tck.tests.extensions.annotated
ProcessAnnotatedTypeTest.testVeto()github
org.jboss.cdi.tck.tests.decorators.custom
CustomDecoratorTest.testCustomImplementationOfDecoratorInterface()github
org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes.synthetic.interceptor
SyntheticInterceptorVetoedTest.testSyntheticInterceptorBeanCanBeVetoed()github
org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes.synthetic
ProcessBeanAttributesFiredForSyntheticBeanTest.testProcessBeanAttributesFired()github
bd)

getSource() returns the Extension instance that added the annotated type.

Coverage

org.jboss.cdi.tck.tests.extensions.annotated.synthetic
ProcessSyntheticAnnotatedTypeTest.testEventsSources()github

Any observer of this event is permitted to wrap and/or replace the AnnotatedType. The container must use the final value of this property, after all observers have been called, as the only source of types and annotations for the the program elements.

ca)

Test class added by BeforeBeanDiscovery.addAnnotatedType().

Coverage

org.jboss.cdi.tck.tests.extensions.annotated
ProcessAnnotatedTypeTest.testSetAnnotatedType()github
cb)

Test annotation added by BeforeBeanDiscovery.addAnnotatedType().

Coverage

No tests exist for this assertion

e)

If any observer method of a ProcessAnnotatedType event throws an exception, the exception is treated as a definition error by the container.

Coverage

org.jboss.cdi.tck.tests.extensions.annotated.broken.processAnnotatedObserverThrowsException
ProcessAnnotatedTypeEventThrowsExceptionTest.testProcessAnnotatedTypeEventThrowsExceptionNotOk()github

Section 11.5.7 - ProcessInjectionPoint event

a)

The container must fire an event for every injection point of every Java EE component class supporting injection that may be instantiated by the container at runtime. The event object must be of type javax.enterprise.inject.spi.ProcessInjectionPoint<T, X> where T is the bean class of the bean that declares the injection point, and X is the declared type of the injection point.

Coverage

org.jboss.cdi.tck.tests.extensions.lifecycle.processInjectionPoint
ProcessInjectionPointFiredTest.testFieldInjectionPoint()github
ProcessInjectionPointFiredTest.testConstructorInjectionPoint()github
ProcessInjectionPointFiredTest.testInitializerInjectionPoint()github
ProcessInjectionPointFiredTest.testProducerMethodInjectionPoint1()github
ProcessInjectionPointFiredTest.testProducerMethodInjectionPoint2()github
org.jboss.cdi.tck.tests.extensions.lifecycle.processInjectionPoint.modify
InjectionPointOverridingTest.testOverridingFieldInjectionPoint()github
InjectionPointOverridingTest.testDelegateInjectionPoint()github
InjectionPointOverridingTest.testNewInjectionPointDiscovered()github
ba)

getInjectionPoint() returns the InjectionPoint object that will be used by the container to perform injection.

Coverage

org.jboss.cdi.tck.tests.extensions.lifecycle.processInjectionPoint
ProcessInjectionPointFiredTest.testFieldInjectionPoint()github
ProcessInjectionPointFiredTest.testConstructorInjectionPoint()github
ProcessInjectionPointFiredTest.testInitializerInjectionPoint()github
ProcessInjectionPointFiredTest.testProducerMethodInjectionPoint1()github
ProcessInjectionPointFiredTest.testProducerMethodInjectionPoint2()github
bb)

setInjectionPoint() replaces the InjectionPoint.

Coverage

org.jboss.cdi.tck.tests.extensions.lifecycle.processInjectionPoint.modify
InjectionPointOverridingTest.testOverridingFieldInjectionPoint()github
InjectionPointOverridingTest.testDelegateInjectionPoint()github
InjectionPointOverridingTest.testNewInjectionPointDiscovered()github
bc)

addDefinitionError() registers a definition error with the container, causing the container to abort deployment after bean discovery is complete.

Coverage

org.jboss.cdi.tck.tests.extensions.lifecycle.processInjectionPoint.broken
AddDefinitionErrorTest.testDeployment()github
c)

Any observer of this event is permitted to wrap and/or replace the InjectionPoint. The container must use the final value of this property, after all observers have been called, whenever it performs injection upon the injection point.

Coverage

org.jboss.cdi.tck.tests.extensions.lifecycle.processInjectionPoint.modify
InjectionPointOverridingTest.testOverridingFieldInjectionPoint()github
InjectionPointOverridingTest.testDelegateInjectionPoint()github
InjectionPointOverridingTest.testNewInjectionPointDiscovered()github
d)

If any observer method of a ProcessInjectionPoint event throws an exception, the exception is treated as a definition error by the container.

Coverage

org.jboss.cdi.tck.tests.extensions.lifecycle.processInjectionPoint.broken
ThrowExceptionTest.testDeployment()github

Section 11.5.8 - ProcessInjectionTarget event

The container must fire an event for every Java EE component class supporting injection that may be instantiated by the container at runtime, including every managed bean declared using @ManagedBean, EJB session or message-driven bean, enabled bean, enabled interceptor or enabled decorator. The event object must be of type javax.enterprise.inject.spi.ProcessInjectionTarget<X>, where x is the managed bean class, session bean class or Java EE component class supporting injection.

aaa)

Test event is fired for a managed bean

Coverage

org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testInjectionTargetInject()github
org.jboss.cdi.tck.tests.extensions.container.event
ContainerEventTest.testProcessInjectionTargetFiredForManagedBean()github
aab)

Test event is fired for a session bean

Coverage

org.jboss.cdi.tck.tests.extensions.container.event
ContainerEventTest.testProcessInjectionTargetFiredForSessionBean()github
aaba)

Test event is fired for a message driven bean

Coverage

org.jboss.cdi.tck.tests.extensions.container.event.jms
ContainerEventTest.testProcessInjectionTargetEventFiredForMessageDrivenBean()github
aac)

Test event is fired for a servlet listener

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
ContainerEventTest.testProcessInjectionTargetEventFiredForServletListener()github
aad)

Test event is fired for a tag handler

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
ContainerEventTest.testProcessInjectionTargetEventFiredForTagHandler()github
aae)

Test event is fired for a tag library listener

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
ContainerEventTest.testProcessInjectionTargetEventFiredForTagLibraryListener()github
aaf)

Test event is fired for an EJB Interceptor

Coverage

org.jboss.cdi.tck.tests.extensions.container.event
ContainerEventTest.testProcessInjectionTargetFiredForSessionBeanInterceptor()github
aag)

Test event is fired for a WS endpoint

Coverage

org.jboss.cdi.tck.tests.extensions.container.event.ws
ContainerEventTest.testProcessInjectionTargetFiredForWsEndpoint()github
aah)

Test event is fired for a servlet

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
ContainerEventTest.testProcessInjectionTargetEventFiredForServlet()github
aai)

Test event is fired for a filter

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
ContainerEventTest.testProcessInjectionTargetEventFiredForFilter()github
The following assertion is not made explicitly by the spec, however it is implied aan)See 10.2. Observer resolution

Test supertype for a servlet listener

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
ContainerEventTest.testTypeOfProcessInjectionTargetParameter()github
The following assertion is not made explicitly by the spec, however it is implied aao)See 10.2. Observer resolution

Test supertype and subtype for a tag handler

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
ContainerEventTest.testTypeOfProcessInjectionTargetParameter()github
The following assertion is not made explicitly by the spec, however it is implied aas)See 10.2. Observer resolution|

Test supertype and subtype for a servlet

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
ContainerEventTest.testTypeOfProcessInjectionTargetParameter()github

getAnnotatedType() returns the AnnotatedType representing the managed bean class, session bean or other Java EE component class supporting injection.

aba)

Test type for a managed bean

Coverage

org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testGetAnnotatedTypeOnProcessInjectionTarget()github
abb)

Test type for a session bean

Coverage

org.jboss.cdi.tck.tests.extensions.container.event
ContainerEventTest.testProcessInjectionTargetFiredForSessionBean()github
abba)

Test type for a message driven bean

Coverage

org.jboss.cdi.tck.tests.extensions.container.event.jms
ContainerEventTest.testProcessInjectionTargetEventFiredForMessageDrivenBean()github
abc)

Test type for a servlet listener

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
ContainerEventTest.testProcessInjectionTargetEventFiredForServletListener()github
abd)

Test type for a tag handler

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
ContainerEventTest.testProcessInjectionTargetEventFiredForTagHandler()github
abe)

Test type for a tag library listener

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
ContainerEventTest.testProcessInjectionTargetEventFiredForTagLibraryListener()github
abf)

Test type for an EJB Interceptor

Coverage

org.jboss.cdi.tck.tests.extensions.container.event
ContainerEventTest.testProcessInjectionTargetFiredForSessionBeanInterceptor()github
abg)

Test type for a WS endpoint

Coverage

org.jboss.cdi.tck.tests.extensions.container.event.ws
ContainerEventTest.testProcessInjectionTargetFiredForWsEndpoint()github
abh)

Test type for a servlet

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
ContainerEventTest.testProcessInjectionTargetEventFiredForServlet()github
abi)

Test type for a filter

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
ContainerEventTest.testProcessInjectionTargetEventFiredForFilter()github
ba)

getInjectionTarget() returns the InjectionTarget object that will be used by the container to perform injection.

Coverage

No tests exist for this assertion

bb)

setInjectionTarget() replaces the InjectionTarget.

Coverage

org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testSettingInjectionTargetReplacesIt()github
da)

addDefinitionError() registers a definition error with the container, causing the container to abort deployment after bean discovery is complete.

Coverage

org.jboss.cdi.tck.tests.extensions.producer.broken.injectionTargetError
InjectionTargetDefinitionErrorTest.testAddingDefinitionError()github

Any observer of this event is permitted to wrap and/or replace the InjectionTarget. The container must use the final value of this property, after all observers have been called, whenever it performs injection upon the managed bean, session bean or other Java EE component class supporting injection.

ea)

Test type for a managed bean

Coverage

org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testSettingInjectionTargetReplacesIt()github
eb)

Test type for a session bean

Coverage

No tests exist for this assertion

ec)

Test type for a servlet listener

Coverage

No tests exist for this assertion

ed)

Test type for a tag handler

Coverage

No tests exist for this assertion

ee)

Test type for a tag library listener

Coverage

No tests exist for this assertion

ef)

Test type for an EJB Interceptor

Coverage

No tests exist for this assertion

eg)

Test type for a WS endpoint

Coverage

No tests exist for this assertion

eh)

Test type for a servlet

Coverage

No tests exist for this assertion

ei)

Test type for a filter

Coverage

No tests exist for this assertion

f)

If any observer method of a ProcessInjectionTarget event throws an exception, the exception is treated as a definition error by the container.

Coverage

org.jboss.cdi.tck.tests.extensions.annotated.broken.processInjectionTargetThrowsException
ProcessInjectionTargetEventThrowsExceptionTest.testProcessInjectionTargetEventThrowsExceptionNotOk()github

Section 11.5.9 - ProcessProducer event

The container must fire an event for each producer method or field of each enabled bean, including resources.

aa)

Test producer method

Coverage

org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testProduceCallsProducerMethod()github
ab)

Test producer field

Coverage

org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testProduceAccessesProducerField()github
ac)

Test resource producer field

Coverage

org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testProduceCallsOverridenResourceProducerMethod()github

The event object must be of type javax.enterprise.inject.spi.ProcessProducer<T, X>, where T is the bean class of the bean that declares the producer method or field and X is the return type of the producer method or the type of the producer field.

ba)

Test producer method

Coverage

org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testProduceCallsProducerMethod()github
bb)

Test producer field

Coverage

org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testProduceAccessesProducerField()github

getAnnotatedMember() returns the AnnotatedField representing the producer field or the AnnotatedMethod representing the producer method.

ca)

Test producer method

Coverage

org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testProduceCallsProducerMethod()github
cb)

Test producer field

Coverage

org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testProduceAccessesProducerField()github

getProducer() returns the Producer object that will be used by the container to call the producer method or read the producer field.

da)

Test producer method

Coverage

org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testProduceCallsProducerMethod()github
db)

Test producer field

Coverage

org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testProduceAccessesProducerField()github
e)

setProducer() replaces the Producer.

Coverage

org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testProduceCallsOverridenResourceProducerMethod()github
ProducerTest.testSetProducerOverridesProducer()github
f)

addDefinitionError() registers a definition error with the container, causing the container to abort deployment after bean discovery is complete.

Coverage

org.jboss.cdi.tck.tests.extensions.producer.broken.processing
ProducerProcessingWithDefinitionErrorTest.testExplicitDefinitionError()github

Any observer of this event is permitted to wrap and/or replace the Producer. The container must use the final value of this property, after all observers have been called, whenever it calls the producer or disposer.

ga)

Test producer method

Coverage

No tests exist for this assertion

gb)

Test producer field

Coverage

No tests exist for this assertion

h)

If any observer method of a ProcessProducer event throws an exception, the exception is treated as a definition error by the container.

Coverage

org.jboss.cdi.tck.tests.extensions.producer.broken.processing
ProducerProcessingWithExceptionTest.testException()github

Section 11.5.10 - ProcessBeanAttributes event

The container must fire an event for each enabled bean, interceptor or decorator deployed in a bean archive, before registering the Bean object. No event is fired for any @New qualified bean, defined in Section 3.14, "@New qualified beans". The event object must be of type javax.enterprise.inject.spi.ProcessBeanAttributes<T> where T is the bean class of the managed bean or session bean, the return type of the producer method, or the type of the producer field.

aa)

Event is fired for enabled bean.

Coverage

org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes
VerifyValuesTest.testManagedBeanAttributes()github
VerifyValuesTest.testSessionBeanAttributes()github
VerifyValuesTest.testProducerMethodBeanAttributes()github
VerifyValuesTest.testProducerFieldBeanAttributes()github
org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes.specialization.broken
TypeConflictDetectionTest.testDeployment()github
org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes.synthetic
ProcessBeanAttributesFiredForSyntheticBeanTest.testProcessBeanAttributesFired()github
org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes.specialization
SpecializationTest.testProcessBeanAttributesFiredProperlyForSpecializedBean()github
VetoTest.testSpecializedBeanAvailableAfterSpecializingBeanVetoed()github
ab)

Event is fired for enabled interceptor.

Coverage

org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes.interceptor
InterceptorProcessBeanAttributesTest.testAlphaInterceptorObserved()github
InterceptorProcessBeanAttributesTest.testBravoInterceptorObserved()github
org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes
VerifyValuesTest.testInterceptorBeanAttributes()github
ac)

Event is fired for enabled decorator.

Coverage

org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes.decorator
DecoratorProcessBeanAttributesTest.testAlphaDecoratorObserved()github
DecoratorProcessBeanAttributesTest.testBravoDecoratorObserved()github
org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes
VerifyValuesTest.testDecoratorBeanAttributes()github
ad)

No event is fired for any @New qualified bean.

Coverage

org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes
VerifyValuesTest.testManagedBeanAttributes()github

getAnnotated() returns the AnnotatedType representing the managed bean class or session bean class, the AnnotatedMethod representing the producer field, or the AnnotatedField representing the producer field.

baa)

Test managed bean.

Coverage

org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes
VerifyValuesTest.testManagedBeanAnnotated()github
bab)

Test session bean.

Coverage

org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes
VerifyValuesTest.testSessionBeanAnnotated()github
VerifyValuesTest.testSessionBeanAttributes()github
bac)

Test producer method.

Coverage

org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes
VerifyValuesTest.testProducerMethodAnnotated()github
bad)

Test producer field.

Coverage

org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes
VerifyValuesTest.testProducerFieldAnnotated()github
bb)

getBeanAttributes() returns the BeanAttributes object that will be used by the container to manage instances of the bean.

Coverage

org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes
VerifyValuesTest.testSessionBeanAttributes()github
VerifyValuesTest.testInterceptorBeanAttributes()github
VerifyValuesTest.testDecoratorBeanAttributes()github
org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes.synthetic
ProcessBeanAttributesFiredForSyntheticBeanTest.testProcessBeanAttributesFired()github
bc)

setBeanAttributes() replaces the BeanAttributes.

Coverage

org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes.modify
SetBeanAttributesTest.testBeanModified()github
org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes.synthetic
ProcessBeanAttributesFiredForSyntheticBeanTest.testProcessBeanAttributesFired()github
bd)

addDefinitionError() registers a definition error with the container, causing the container to abort deployment after bean discovery is complete.

Coverage

org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes.broken
AddDefinitionErrorTest.testDeployment()github
be)

veto() forces the container to ignore the bean.

Coverage

org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes.veto
VetoTest.testBeanVetoed()github
org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes.synthetic.interceptor
SyntheticInterceptorVetoedTest.testSyntheticInterceptorBeanCanBeVetoed()github
org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes.specialization
VetoTest.testSpecializedBeanAvailableAfterSpecializingBeanVetoed()github
c)

Any observer of this event is permitted to wrap and/or replace the BeanAttributes. The container must use the final value of this property, after all observers have been called, to manage instances of the bean.

Coverage

org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes.modify
SetBeanAttributesTest.testBeanModified()github
d)

If any observer method of a ProcessBeanAttributes event throws an exception, the exception is treated as a definition error by the container.

Coverage

org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes.broken
ThrowExceptionTest.testDeployment()github

Section 11.5.11 - ProcessBean event

aa)Tested below

The container must fire an event for each enabled bean, interceptor or decorator deployed in a bean archive, after firing the ProcessBeanAttributes for the bean and before registering the Bean object. No event is fired for any @New qualified bean, defined in Section 3.12, "@New qualified beans".

ba)

For a managed bean with bean class X, the container must raise an event of type ProcessManagedBean<X>.

Coverage

org.jboss.cdi.tck.tests.extensions.container.event
ContainerEventTest.testProcessManagedBeanFired()github
org.jboss.cdi.tck.tests.extensions.processBean
ProcessBeanTest.testProcessBeanEvent()github
bb)

Test ProcessManagedBean is fired after ProcessBeanAttributes.

Coverage

org.jboss.cdi.tck.tests.extensions.processBean
ProcessBeanTest.testProcessBeanEvent()github
ca)

For a session bean with bean class X, the container must raise an event of type ProcessSessionBean<X>.

Coverage

org.jboss.cdi.tck.tests.extensions.processBean
ProcessSessionBeanTest.testProcessSessionBeanEvent()github
cb)

Test ProcessSessionBean is fired after ProcessBeanAttributes.

Coverage

org.jboss.cdi.tck.tests.extensions.processBean
ProcessSessionBeanTest.testProcessSessionBeanEvent()github
eaa)

For a producer method with method return type X of a bean with bean class T, the container must raise an event of type ProcessProducerMethod<T, X>.

Coverage

org.jboss.cdi.tck.tests.extensions.processBean
ProcessBeanTest.testProcessProducerMethodEvent()github
eab)

Test ProcessProducerMethod is fired after ProcessBeanAttributes.

Coverage

org.jboss.cdi.tck.tests.extensions.processBean
ProcessBeanTest.testProcessProducerMethodEvent()github
eba)

For a producer field with field type X of a bean with bean class T, the container must raise an event of type ProcessProducerField<T, X>.

Coverage

org.jboss.cdi.tck.tests.extensions.processBean
ProcessBeanTest.testProcessProducerFieldEvent()github
ebb)

Test ProcessProducerField is fired after ProcessBeanAttributes.

Coverage

org.jboss.cdi.tck.tests.extensions.processBean
ProcessBeanTest.testProcessProducerFieldEvent()github
ec)

Resources are considered to be producer fields.

Coverage

org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testResourceAreConsideredToBeProducerField()github

The interface javax.enterprise.inject.spi.ProcessBean is a supertype of all these event types.

eda)

Test ProcessManagedBean

Coverage

org.jboss.cdi.tck.tests.extensions.processBean
ProcessBeanTest.testProcessBeanEvent()github
edb)

Test ProcessSessionBean

Coverage

org.jboss.cdi.tck.tests.extensions.processBean
ProcessSessionBeanTest.testProcessSessionBeanEvent()github
edc)

Test ProcessProducerMethod

Coverage

org.jboss.cdi.tck.tests.extensions.processBean
ProcessBeanTest.testProcessProducerMethodEvent()github
edd)

Test ProcessProducerField

Coverage

org.jboss.cdi.tck.tests.extensions.processBean
ProcessBeanTest.testProcessProducerFieldEvent()github

getAnnotated() returns the AnnotatedType representing the bean class, the AnnotatedMethod representing the producer method, or the AnnotatedField representing the producer field.

efa)

Test ProcessManagedBean

Coverage

org.jboss.cdi.tck.tests.extensions.processBean
ProcessBeanTest.testProcessBeanEvent()github
efb)

Test ProcessSessionBean

Coverage

org.jboss.cdi.tck.tests.extensions.processBean
ProcessSessionBeanTest.testProcessSessionBeanEvent()github
efc)

Test ProcessProducerMethod

Coverage

org.jboss.cdi.tck.tests.extensions.processBean
ProcessBeanTest.testProcessProducerMethodEvent()github
efd)

Test ProcessProducerField

Coverage

org.jboss.cdi.tck.tests.extensions.processBean
ProcessBeanTest.testProcessProducerFieldEvent()github

getBean() returns the Bean object that is about to be registered. The Bean may implement Interceptor or Decorator.

fa)

Test ProcessManagedBean

Coverage

org.jboss.cdi.tck.tests.extensions.processBean
ProcessBeanTest.testProcessBeanEvent()github
fb)

Test ProcessSessionBean

Coverage

org.jboss.cdi.tck.tests.extensions.processBean
ProcessSessionBeanTest.testProcessSessionBeanEvent()github
fc)

Test ProcessProducerMethod

Coverage

org.jboss.cdi.tck.tests.extensions.processBean
ProcessBeanTest.testProcessProducerMethodEvent()github
fd)

Test ProcessProducerField

Coverage

org.jboss.cdi.tck.tests.extensions.processBean
ProcessBeanTest.testProcessProducerFieldEvent()github
h)

addDefinitionError() registers a definition error with the container, causing the container to abort deployment after bean discovery is complete.

Coverage

org.jboss.cdi.tck.tests.extensions.container.event.broken.processBeanObserverRegistersException
AddDefinitionErrorTest.testAddDefinitionError()github
hb)

getEjbName() returns the EJB name of the session bean.

Coverage

org.jboss.cdi.tck.tests.extensions.container.event
ContainerEventTest.testGetEJBName()github
org.jboss.cdi.tck.tests.extensions.processBean
ProcessSessionBeanTest.testProcessSessionBeanEvent()github
hc)

getSessionBeanType() returns a javax.enterprise.inject.spi.SessionBeanType representing the kind of session bean.

Coverage

org.jboss.cdi.tck.tests.extensions.container.event
ContainerEventTest.testGetSessionBeanType()github
org.jboss.cdi.tck.tests.extensions.processBean
ProcessSessionBeanTest.testProcessSessionBeanEvent()github
hd)

If any observer method of a ProcessBean event throws an exception, the exception is treated as a definition error by the container.

Coverage

org.jboss.cdi.tck.tests.extensions.container.event.broken.processBeanObserverThrowsException
ThrowExceptionInProcessBeanObserverTest.testProcessBeanObserverThrowsException()github
The following assertion is not made explicitly by the spec, however it is implied i)

Check the getAnnotatedProducerMethod()

Coverage

org.jboss.cdi.tck.tests.extensions.processBean
ProcessBeanTest.testProcessProducerMethodEvent()github
The following assertion is not made explicitly by the spec, however it is implied j)

Check the getAnnotatedDisposesParameter()

Coverage

org.jboss.cdi.tck.tests.extensions.processBean
ProcessBeanTest.testProcessProducerMethodEvent()github
The following assertion is not made explicitly by the spec, however it is implied k)

Check the getAnnotatedSessionBeanClass()

Coverage

org.jboss.cdi.tck.tests.extensions.processBean
ProcessSessionBeanTest.testProcessSessionBeanEvent()github

Check the getAnnotatedBeanClass()

The following assertion is not made explicitly by the spec, however it is implied l)

Check for managed bean

Coverage

org.jboss.cdi.tck.tests.extensions.processBean
ProcessBeanTest.testProcessBeanEvent()github
The following assertion is not made explicitly by the spec, however it is implied m)

Check for session bean

Coverage

org.jboss.cdi.tck.tests.extensions.processBean
ProcessSessionBeanTest.testProcessSessionBeanEvent()github
The following assertion is not made explicitly by the spec, however it is implied n)

Check the getAnnotatedProducerField()

Coverage

org.jboss.cdi.tck.tests.extensions.processBean
ProcessBeanTest.testProcessProducerFieldEvent()github

Section 11.5.12 - ProcessObserverMethod event

aaa)

The container must fire an event for each observer method of each enabled bean, before registering the ObserverMethod object. The event object must be of type javax.enterprise.inject.spi.ProcessObserverMethod<T, X> where T is the bean class of the bean that declares the observer method and X is the observed event type of the observer method.

Coverage

org.jboss.cdi.tck.tests.extensions.observer
ProcessObserverMethodEventTest.testProcessObserverMethodEventsSent()github
aba)

getAnnotatedEventParameter() returns the AnnotatedParameter representing the event parameter.

Coverage

org.jboss.cdi.tck.tests.extensions.observer
ProcessObserverMethodEventTest.testGetAnnotatedMethod()github
ba)

getObserverMethod() returns the ObserverMethod object that will be used by the container to call the observer method.

Coverage

org.jboss.cdi.tck.tests.extensions.observer
ProcessObserverMethodEventTest.testGetObserverMethod()github
da)

addDefinitionError() registers a definition error with the container, causing the container to abort deployment after bean discovery is complete.

Coverage

org.jboss.cdi.tck.tests.extensions.observer.broken.definitionError
ProcessObserverMethodErrorTest.testAddDefinitionError()github
db)

If any observer method of a ProcessObserverMethod event throws an exception, the exception is treated as a definition error by the container.

Coverage

org.jboss.cdi.tck.tests.extensions.observer.broken.exception
ProcessObserverMethodExceptionTest.testExceptionIsDefinitionError()github

Section 12.1 - Bean deployment archives

aa)

Bean classes of enabled beans must be deployed in bean archives.

a)

A library jar, EJB jar, application client jar or rar archive is a bean archive if it has a file named beans.xml in the META-INF directory.

The WEB-INF/classes directory of a war is a bean archive if there is a file named beans.xml in the WEB-INF directory or in the WEB-INF/classes/META-INF directory of the war.

aba)By default all TCK web archive deployments.

Test the beans.xml file in the WEB-INF directory.

abb)

Test the beans.xml file in the WEB-INF/classes/META-INF directory.

Coverage

org.jboss.cdi.tck.tests.deployment.packaging.war
BeansDescriptorAlternativeLocationTest.testAlternativeLocation()github
ab)

The WEB-INF/classes directory of a war is a bean archive if there is a file named beans.xml in the WEB-INF directory or in the WEB-INF/classes/META-INF directory of the war.

ac)covered in bb*, bc*, bd*

A directory in the JVM classpath is a bean deployment archive if it has a file named beans.xml in the META-INF directory.

b)

The container is not required to support application client jar bean archives.

ba)covered in bb*, bc*, bd*

The container searches for beans in all bean archives in the application classpath.

In an application deployed as an ear, the container searches every bean archive bundled with or referenced by the ear, including bean archives bundled with or referenced by wars and EJB jars contained in the ear. The bean archives might be library jars, EJB jars, rars or war WEB-INF/classes directories.

bba)

Check an EJB jar in an EAR

Coverage

org.jboss.cdi.tck.tests.implementation.enterprise.lifecycle
EnterpriseBeanLifecycleTest.testCreateSFSB()github
bbb)

Check a bundled library in an EAR

Coverage

org.jboss.cdi.tck.tests.deployment.packaging.bundledLibrary
LibraryInEarTest.test()github
bbc)

Check a bundled library in a WAR

Coverage

org.jboss.cdi.tck.tests.deployment.packaging.ear
MultiWebModuleWithExtensionTest.testMultipleWebModulesWithExtension()github
SingleWebModuleWithExtensionTest.testSingleWebModuleWithExtension()github
org.jboss.cdi.tck.tests.deployment.packaging.bundledLibrary
LibraryMissingBeansXmlTest.test()github
bbd)

Check a rar

Coverage

org.jboss.cdi.tck.tests.deployment.packaging.rar
ResourceAdapterArchiveTest.testInjection()github
ResourceAdapterArchiveTest.testResolution()github
bbe)

Check a war in an ear

Coverage

org.jboss.cdi.tck.tests.deployment.packaging.ear
MultiWebModuleWithExtensionTest.testMultipleWebModulesWithExtension()github
SingleWebModuleWithExtensionTest.testSingleWebModuleWithExtension()github
bbf)

Check for a jar installed as a library

Coverage

org.jboss.cdi.tck.tests.deployment.packaging.installedLibrary
InstalledLibraryEarTest.testInjection()github
InstalledLibraryEarTest.testResolution()github

In an application deployed as a war, the container searches every bean archive bundled with or referenced by the war. The bean archives might be library jars or the WEB-INF/classes directory.

bca)

Check classes in the war

Coverage

org.jboss.cdi.tck.tests.deployment.packaging.war.modules
WebArchiveModulesTest.testInjectionChainVisibilityAndInterceptorEnablement()github
org.jboss.cdi.tck.tests.implementation.simple.lifecycle
SimpleBeanLifecycleTest.testCreateInjectsFieldsDeclaredInJava()github
bcb)

Check bundled libraries in the war

Coverage

org.jboss.cdi.tck.tests.deployment.packaging.visibility
VisibilityOfBeanInWebModuleFromBeanManagerInBeanLibraryTest.shouldFindBeanByType()github
VisibilityOfBeanInWebModuleFromBeanManagerInBeanLibraryTest.shouldFindBeanByName()github
org.jboss.cdi.tck.tests.deployment.packaging.bundledLibrary
LibraryInWarTest.test()github
org.jboss.cdi.tck.tests.deployment.packaging.war.modules
WebArchiveModulesTest.testInjectionChainVisibilityAndInterceptorEnablement()github
org.jboss.cdi.tck.tests.deployment.packaging.visibility
JarToJarAlphaVisibilityTest.testDeployment()github
JarToJarReverseAlphaVisibilityTest.testDeployment()github
bcc)

Check for a jar installed as a library

Coverage

org.jboss.cdi.tck.tests.deployment.packaging.installedLibrary
InstalledLibraryWarTest.testInjection()github
InstalledLibraryWarTest.testResolution()github

In an application deployed as an EJB jar, the container searches the EJB jar, if it is a bean archive, and every bean archive referenced by the EJB jar.

bcd)

Check classes in the jar.

Coverage

org.jboss.cdi.tck.tests.deployment.packaging.ejb
EJBJarDeploymentTest.testContainerSearchesEJBJar()github

An embeddable EJB container searches each bean archive in the JVM classpath that is listed in the value of the embeddable container initialization property javax.ejb.embeddable.modules, or every bean archive in the JVM classpath if the property is not specified. The bean archives might be directories, library jars or EJB jars.

bda)1.0 release of the TCK does not cover embeddable EJB

Check modules specified by javax.ejb.embeddable.modules

bdb)1.0 release of the TCK does not cover embeddable EJB

Check libraries

bdc)1.0 release of the TCK does not cover embeddable EJB

Check directories

bda)1.0 release of the TCK does not cover embeddable EJB

Check ejb jars

be)covered in bb*, bc*, bd*

When searching for beans, the container considers any Java class in any bean archive, any ejb-jar.xml file in the metadata directory of any EJB bean archive, any Java class referenced by the @New qualifier of an injection point of another bean, and any interceptor or decorator class declared in the beans.xml file of any bean archive.

d)Describes undefined behavior

If a bean class is deployed in two different bean archives, non-portable behaviour results. Portable applications must deploy each bean class in no more than one bean archive.

e)Non-portable behavior

If an enum declaring injection points is defined in installed library jars, non-portable behavior results.

f)

An extension may be deployed in any archive, including those that are not bean archives.

Coverage

org.jboss.cdi.tck.tests.extensions.registration
BeanRegistrationByExtensionInNonBeanArchiveTest.shouldFindBeanReference()github
org.jboss.cdi.tck.tests.lookup.manager.provider.init
CDIProviderInitTest.testAccessingBeanManager()github

Section 12.2 - Application initialization lifecycle

a)Description

When an application is started, the container performs the following steps.

b)

First, the container must search for service providers for the service javax.enterprise.inject.spi.Extension defined in Section 11.5, "Container lifecycle events", instantiate a single instance of each service provider, and search the service provider class for observer methods of initialization events.

Coverage

org.jboss.cdi.tck.tests.deployment.initialization
ApplicationInitializationLifecycleTest.testInitialization()github
org.jboss.cdi.tck.tests.deployment.lifecycle
ExtensionsTest.testBeforeBeanDiscoveryEventIsCalled()github
org.jboss.cdi.tck.tests.extensions.alternative.deployment
AlternativeInLibraryWithExtensionTest.testAlternative()github
c)

Next, the container must fire an event of type BeforeBeanDiscovery, as defined in Section 11.5.1, "BeforeBeanDiscovery event".

Coverage

org.jboss.cdi.tck.tests.deployment.initialization
ApplicationInitializationLifecycleTest.testInitialization()github
org.jboss.cdi.tck.tests.deployment.lifecycle
ExtensionsTest.testBeforeBeanDiscoveryEventIsCalled()github
i)

Next, the container must fire an event of type ProcessModule for every bean archive, as defined in Section 11.5.5, “ProcessModule event”.

Coverage

org.jboss.cdi.tck.tests.deployment.initialization
ApplicationInitializationLifecycleTest.testInitialization()github

Next, the container must perform bean discovery, and abort initialization of the application if any definition errors exist, as defined in Section 2.8, "Problems detected automatically by the container". Additionally, for every Java EE component class supporting injection that may be instantiated by the container at runtime, the container must create an InjectionTarget for the class, as defined in 11.2, "The Producer and InjectionTarget interfaces", and fire an event of type ProcessInjectionTarget, as defined in Section 11.5.6, "ProcessInjectionTarget event".

da)

Check beans are discovered.

Coverage

org.jboss.cdi.tck.tests.deployment.initialization
ApplicationInitializationLifecycleTest.testInitialization()github
org.jboss.cdi.tck.tests.implementation.simple.lifecycle
SimpleBeanLifecycleTest.testManagedBean()github
db)

Check definitions error occurs.

Coverage

org.jboss.cdi.tck.tests.implementation.simple.definition.constructorHasDisposesParameter
ConstructorHasDisposesParameterTest.testConstructorHasDisposesParameter()github
e)

Next, the container must fire an event of type AfterBeanDiscovery, as defined in Section 11.5.2, "AfterBeanDiscovery event", and abort initialization of the application if any observer registers a definition error.

Coverage

org.jboss.cdi.tck.tests.deployment.lifecycle.broken.addDefinitionError
AddDefinitionErrorTest.testObserverDefinitionErrorTreatedAsDefinitionError()github
f)

Next, the container must detect deployment problems by validating bean dependencies and specialization and abort initialization of the application if any deployment problems exist, as defined in Section 2.8, "Problems detected automatically by the container".

Coverage

org.jboss.cdi.tck.tests.deployment.initialization
ApplicationInitializationLifecycleTest.testInitialization()github
g)

Next, the container must fire an event of type AfterDeploymentValidation, as defined in Section 11.5.3, "AfterDeploymentValidation event", and abort initialization of the application if any observer registers a deployment problem.

Coverage

org.jboss.cdi.tck.tests.deployment.initialization
ApplicationInitializationLifecycleTest.testInitialization()github
ga)

Next, the container must inject any enums declaring injection points.

Coverage

org.jboss.cdi.tck.tests.deployment.initialization
ApplicationInitializationLifecycleTest.testInitialization()github
h)Can only check the inverse, that requests aren't directed to the application before

Finally, the container begins directing requests to the application.

Coverage

org.jboss.cdi.tck.tests.deployment.initialization
ApplicationInitializationLifecycleTest.testInitialization()github

Section 12.3 - Application shutdown lifecycle

When an application is stopped, the container performs the following steps:

a)

First, the container must destroy all contexts.

Coverage

org.jboss.cdi.tck.tests.deployment.shutdown
ApplicationShutdownLifecycleTest.testShutdown()github
b)

Next, the container must destroy dependent objects injected into enums.

Coverage

org.jboss.cdi.tck.tests.deployment.shutdown
ApplicationShutdownLifecycleTest.testShutdown()github
c)

Finally, the container must fire an event of type BeforeShutdown, as defined in Section 11.5.4, "BeforeShutdown event".

Coverage

org.jboss.cdi.tck.tests.deployment.shutdown
ApplicationShutdownLifecycleTest.testShutdown()github

Section 12.4 - Bean discovery

a)Statement of intent

The container automatically discovers managed beans (according to the rules of Section 3.1.1, "Which Java classes are managed beans?") and session beans in bean archives and searches the bean classes for producer methods, producer fields, disposer methods and observer methods.

For each Java class or interface deployed in a bean archive, the container must create an AnnotatedType representing the type and fire an event of type ProcessAnnotatedType, as defined in Section 11.5.5, "ProcessAnnotatedType event".

ba)

Check managed bean

Coverage

org.jboss.cdi.tck.tests.extensions.container.event
ContainerEventTest.testProcessAnnotatedTypeFiredForManagedBean()github
org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testInjectionTargetInject()github
org.jboss.cdi.tck.tests.extensions.annotated
ProcessAnnotatedTypeTest.testProcessAnnotatedTypeEventsSent()github
bb)

Check session bean

Coverage

org.jboss.cdi.tck.tests.extensions.container.event
ContainerEventTest.testProcessAnnotatedTypeFiredForSessionBean()github
bd)

Check JSF managed beans

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
ContainerEventTest.testProcessAnnotatedTypeEventFiredForJsfManagedBean()github
be)

Check servlet listener

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
ContainerEventTest.testProcessAnnotatedTypeEventFiredForServletListener()github
bf)

Check tag handler

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
ContainerEventTest.testProcessAnnotatedTypeEventFiredForTagHandler()github
bg)

Check tag library listener

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
ContainerEventTest.testProcessAnnotatedTypeEventFiredForTagLibraryListener()github
bh)

Check EJB Interceptor

Coverage

org.jboss.cdi.tck.tests.extensions.container.event
ContainerEventTest.testProcessAnnotatedTypeFiredForSessionBeanInterceptor()github
bi)

Check WS endpoint

Coverage

org.jboss.cdi.tck.tests.extensions.container.event.ws
ContainerEventTest.testProcessAnnotatedTypeFiredForWsEndpoint()github
bj)

Check servlet

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
ContainerEventTest.testProcessAnnotatedTypeEventFiredForServlet()github
bk)

Check filter

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
ContainerEventTest.testProcessAnnotatedTypeEventFiredForFilter()github
c)No consequence

For each Java class in any bean archive, the container must inspect the type metadata to determine if it is a bean or other Java EE component class supporting injection.

d)Tested elsewhere

For each Java class in any bean archive, the container must detect definition errors by validating the class and its metadata.

For each Java class in any bean archive, the container must, if the class is a managed bean, session bean, or other Java EE component class supporting injection, create an InjectionTarget for the class, as defined in Section 11.2, "The Producer and InjectionTarget interfaces", and fire an event of type ProcessInjectionTarget, as defined in Section 11.5.6, "ProcessInjectionTarget event"

da)

Check managed bean

Coverage

org.jboss.cdi.tck.tests.extensions.container.event
ContainerEventTest.testProcessInjectionTargetFiredForManagedBean()github
db)

Check session bean

Coverage

org.jboss.cdi.tck.tests.extensions.container.event
ContainerEventTest.testProcessInjectionTargetFiredForSessionBean()github
dd)

Check JSF managed beans

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
ContainerEventTest.testProcessInjectionTargetEventFiredForJsfManagedBean()github
de)

Check servlet listener

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
ContainerEventTest.testProcessInjectionTargetEventFiredForServletListener()github
df)

Check tag handler

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
ContainerEventTest.testProcessInjectionTargetEventFiredForTagHandler()github
dg)

Check tag library listener

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
ContainerEventTest.testProcessInjectionTargetEventFiredForTagLibraryListener()github
dh)

Check EJB Interceptor

Coverage

org.jboss.cdi.tck.tests.extensions.container.event
ContainerEventTest.testProcessInjectionTargetFiredForSessionBeanInterceptor()github
di)

Check WS endpoint

Coverage

org.jboss.cdi.tck.tests.extensions.container.event.ws
ContainerEventTest.testProcessInjectionTargetFiredForWsEndpoint()github
dj)

Check servlet

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
ContainerEventTest.testProcessInjectionTargetEventFiredForServlet()github
dk)

Check filter

Coverage

org.jboss.cdi.tck.tests.lookup.injection.non.contextual
ContainerEventTest.testProcessInjectionTargetEventFiredForFilter()github

For each Java class in any bean archive, the container must, if the class is an enabled bean, interceptor or decorator, create a Bean object that implements the rules defined in Section 7.3.1, "Lifecycle of managed beans", Section 7.3.2, "Lifecycle of stateful session beans" or Section 7.3.3, "Lifecycle of stateless session and singleton beans", and fire an event which is a subtype of ProcessBean, as defined in Section 11.5.8, "ProcessBean event".

fa)

Check a managed bean

Coverage

org.jboss.cdi.tck.tests.extensions.processBean
ProcessBeanTest.testProcessBeanEvent()github
fb)

Check a session bean

Coverage

org.jboss.cdi.tck.tests.extensions.processBean
ProcessSessionBeanTest.testProcessSessionBeanEvent()github
org.jboss.cdi.tck.tests.extensions.container.event
ContainerEventTest.testProcessSessionBeanFiredForStatelessSessionBean()github
ContainerEventTest.testProcessSessionBeanFiredForStatefulSessionBean()github

For each enabled bean, the container must search the class for producer methods and fields, including resources, and for each producer method or field create a Producer, as defined in Section 11.2, "The Producer and InjectionTarget interfaces", and fire an event of type ProcessProducer, as defined in Section 11.5.7, "ProcessProducer event", and then if the producer method or field is enabled, create a Bean object that implements the rules defined in Section 7.3.4, "Lifecycle of producer methods", Section 7.3.5, "Lifecycle of producer fields" or Section 7.3.6, "Lifecycle of resources", and fire an event which is a subtype of ProcessBean, as defined in Section 11.5.8, "ProcessBean event".

ha)

Check a producer method

Coverage

org.jboss.cdi.tck.tests.extensions.processBean
ProcessBeanTest.testProcessProducerMethodEvent()github
org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testProduceCallsProducerMethod()github
hb)

Check a producer field

Coverage

org.jboss.cdi.tck.tests.extensions.processBean
ProcessBeanTest.testProcessProducerFieldEvent()github
org.jboss.cdi.tck.tests.extensions.producer
ProducerTest.testProduceAccessesProducerField()github
i)

For each enabled bean, the container must search the class for observer methods, and for each observer method create an ObserverMethod object, as defined in Section 11.1.3, "The ObserverMethod interface" and fire an event of type ProcessObserverMethod, as defined in Section 11.5.9, "ProcessObserverMethod event".

Coverage

org.jboss.cdi.tck.tests.extensions.observer
ProcessObserverMethodEventTest.testProcessObserverMethodEventsSent()github
ProcessObserverMethodEventTest.testGetObserverMethod()github

The container determines which alternatives, interceptors and decorators are enabled, according to the rules defined in Section 5.1.2, "Enabled and disabled beans", Section 9.4, "Interceptor enablement and ordering" and Section 8.2, "Decorator enablement and ordering", taking into account any <enable>, <interceptors> and <decorators> declarations in the beans.xml files, and registers the Bean and ObserverMethod objects.

ka)

Check only beans for enabled policies registered

Coverage

org.jboss.cdi.tck.tests.alternative
AlternativeAvailabilityTest.testAlternativeAvailability()github
kb)

Check only enabled interceptors registered

Coverage

org.jboss.cdi.tck.tests.interceptors.invocation
InterceptorInvocationTest.testManagedBeanIsIntercepted()github
kc)

Check only enabled decorators registered

Coverage

org.jboss.cdi.tck.tests.decorators.definition
DecoratorDefinitionTest.testDecoratorIsManagedBean()github
l)Checked above

For each enabled bean that is not an interceptor or decorator, the container registers an instance of the Bean interface defined in Section 11.1, "The Bean interface".

m)Checked above

For each enabled interceptor, the container registers an instance of the Interceptor interface as defined in Section 11.1.2, "The Interceptor interface".

n)Checked above

For each enabled decorator, the container registers an instance of the Decorator interface defined in Section 11.1.1, "The Decorator interface".

o)

For each observer method of every enabled bean, the container registers an instance of the ObserverMethod interface defined in Section 11.1.3, "The ObserverMethod interface".

Coverage

org.jboss.cdi.tck.tests.event.observer.resolve
ResolveEventObserversTest.testObserverMethodAutomaticallyRegistered()github
ResolveEventObserversTest.testObserverMethodNotAutomaticallyRegisteredForDisabledBeans()github

Section 12.5 - Integration with Unified EL

a)

The container must provide a Unified EL ELResolver to the servlet engine and JSF implementation that resolves bean EL names using the rules of name resolution defined in 5.3, "EL name resolution" and resolving ambiguities according to Section 5.3.1, "Ambiguous EL names".

Coverage

org.jboss.cdi.tck.tests.lookup.el.integration
IntegrationWithUnifiedELTest.testELResolverRegisteredWithJsf()github
IntegrationWithUnifiedELTest.testELResolverRegisteredWithServletContainer()github
c)

If a name used in an EL expression does not resolve to any bean, the ELResolver must return a null value.

Coverage

org.jboss.cdi.tck.tests.lookup.el
ResolutionByNameTest.testUnresolvedNameReturnsNull()github
d)

Otherwise, if a name used in an EL expression resolves to exactly one bean, the ELResolver must return a contextual instance of the bean, as defined in Section 6.5.2, "Contextual instance of a bean".

Coverage

org.jboss.cdi.tck.tests.lookup.el
ResolutionByNameTest.testELResolverReturnsContextualInstance()github

Unmatched tests

The following 2 tests do not match any known assertions:

SectionAssertionTest ClassTest Method
11.5.11c
org.jboss.cdi.tck.tests.extensions.container.event
ContainerEventTest
testProcessSessionBeanFiredForStatefulSessionBean()
11.5.11c
org.jboss.cdi.tck.tests.extensions.container.event
ContainerEventTest
testProcessSessionBeanFiredForStatelessSessionBean()

Highlighted test groups

Test ClassTest method
broken (0)
incontainer-broken (0)
rewrite (6)
org.jboss.cdi.tck.tests.event.fires
FireEventTest
testEventSelectedFiresAndObserversNotified()
org.jboss.cdi.tck.tests.event.fires
FireEventTest
testInjectedAnyEventCanFireEvent()
org.jboss.cdi.tck.tests.event.fires
FireEventTest
testInjectedEventAcceptsEventObject()
org.jboss.cdi.tck.tests.event.fires
FireEventTest
testInjectedEventCanHaveBindings()
org.jboss.cdi.tck.tests.event.fires
FireEventTest
testInjectedEventCanSpecifyBindingsDynamically()
org.jboss.cdi.tck.tests.implementation.builtin
BuiltInBeansTest
testPrincipalBean()
jboss-as-broken (0)
ri-broken (0)