# Jakarta Contexts and Dependency Injection 3.0 TCK Coverage

## 3.0

### 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 %
--- | --- | --- | --- | --- | --- | --- | ---
1 Architecture | 0 | 0 | 0 | 0 | 0 | 0 |
2 Concepts | 146 | 122 | 0 | 0 | 0 | 0 | 0.00%
3 Programming model | 177 | 172 | 0 | 0 | 0 | 0 | 0.00%
4 Inheritance and specialization | 55 | 49 | 0 | 0 | 0 | 0 | 0.00%
5 Dependency injection and lookup | 198 | 184 | 0 | 0 | 0 | 0 | 0.00%
6 Scopes and contexts | 172 | 143 | 0 | 0 | 0 | 0 | 0.00%
7 Lifecycle of contextual instances | 30 | 30 | 0 | 0 | 0 | 0 | 0.00%
8 Decorators | 61 | 56 | 0 | 0 | 0 | 0 | 0.00%
9 Interceptor bindings | 27 | 24 | 0 | 0 | 0 | 0 | 0.00%
10 Events | 113 | 100 | 0 | 0 | 0 | 0 | 0.00%
11 Portable extensions | 491 | 459 | 0 | 0 | 0 | 0 | 0.00%
12 Packaging and deployment | 65 | 44 | 0 | 0 | 0 | 0 | 0.00%
13 Bootstrapping a CDI container in Java SE | 28 | 25 | 0 | 0 | 0 | 0 | 0.00%
14 Scopes and contexts in Java SE | 4 | 4 | 0 | 0 | 0 | 0 | 0.00%
15 Packaging and deployment in Java SE | 2 | 2 | 0 | 0 | 0 | 0 | 0.00%
16 Portable extensions in Java SE | 1 | 0 | 0 | 0 | 0 | 0 |
17 Extended Concepts for Jakarta EE | 10 | 8 | 0 | 0 | 0 | 0 | 0.00%
18 Addition to programming model for Jakarta EE | 130 | 122 | 0 | 0 | 0 | 0 | 0.00%
19 Dependency injection, lookup and EL in Jakarta EE | 60 | 58 | 0 | 0 | 0 | 0 | 0.00%
20 Scopes and contexts in Jakarta EE | 109 | 103 | 0 | 0 | 0 | 0 | 0.00%
21 Lifecycle of contextual instances | 34 | 30 | 0 | 0 | 0 | 0 | 0.00%
22 Decorators in Jakarta EE | 17 | 17 | 0 | 0 | 0 | 0 | 0.00%
23 Interceptor bindings in Jakarta EE | 2 | 2 | 0 | 0 | 0 | 0 | 0.00%
24 Events in Jakarta EE | 4 | 4 | 0 | 0 | 0 | 0 | 0.00%
25 Portable extensions in Jakarta EE | 49 | 49 | 0 | 0 | 0 | 0 | 0.00%
26 Packaging and deployment in Jakarta EE | 47 | 42 | 0 | 0 | 0 | 0 | 0.00%
Total | 2032 | 1849 | 0 | 0 | 0 | 0 | 0.00%

### Section Summary

Section | Assertions | Testable | Total Tested | Tested (problematic) | Tested (working) | Coverage %
--- | --- | --- | --- | --- | --- | ---
1 Architecture [architecture] | 0 | 0 | 0 | 0 | 0 |
2 Concepts [concepts] | 7 | 6 | 0 | 0 | 0 | 0.00%
2.1 Functionality provided by the container to the bean [capabilities] | 0 | 0 | 0 | 0 | 0 |
2.2 Bean types [bean_types] | 2 | 2 | 0 | 0 | 0 | 0.00%
2.2.1 Legal bean types [legal_bean_types] | 14 | 14 | 0 | 0 | 0 | 0.00%
2.2.2 Restricting the bean types of a bean [restricting_bean_types] | 9 | 9 | 0 | 0 | 0 | 0.00%
2.2.3 Typecasting between bean types [typecasting_between_bean_types] | 1 | 1 | 0 | 0 | 0 | 0.00%
2.3 Qualifiers [qualifiers] | 0 | 0 | 0 | 0 | 0 |
2.3.1 Built-in qualifier types [builtin_qualifiers] | 3 | 3 | 0 | 0 | 0 | 0.00%
2.3.2 Defining new qualifier types [defining_qualifier_types] | 3 | 1 | 0 | 0 | 0 | 0.00%
2.3.3 Declaring the qualifiers of a bean [declaring_bean_qualifiers] | 4 | 4 | 0 | 0 | 0 | 0.00%
2.3.4 Specifying qualifiers of an injected field [injected_field_qualifiers] | 2 | 2 | 0 | 0 | 0 | 0.00%
2.3.5 Specifying qualifiers of a method or constructor parameter [method_constructor_parameter_qualifiers] | 5 | 5 | 0 | 0 | 0 | 0.00%
2.3.6 Repeating qualifiers [repeating_qualifiers] | 1 | 1 | 0 | 0 | 0 | 0.00%
2.4 Scopes [scopes] | 3 | 2 | 0 | 0 | 0 | 0.00%
2.4.1 Built-in scope types [builtin_scopes] | 4 | 3 | 0 | 0 | 0 | 0.00%
2.4.2 Defining new scope types [defining_new_scope_type] | 4 | 2 | 0 | 0 | 0 | 0.00%
2.4.3 Declaring the bean scope [declaring_bean_scope] | 5 | 5 | 0 | 0 | 0 | 0.00%
2.4.4 Default scope [default_scope] | 5 | 5 | 0 | 0 | 0 | 0.00%
2.5 Default bean discovery mode [default_bean_discovery] | 5 | 5 | 0 | 0 | 0 | 0.00%
2.5.1 Bean defining annotations [bean_defining_annotations] | 9 | 8 | 0 | 0 | 0 | 0.00%
2.6 Bean names [names] | 1 | 1 | 0 | 0 | 0 | 0.00%
2.6.1 Declaring the bean name [declaring_bean_name] | 3 | 3 | 0 | 0 | 0 | 0.00%
2.6.2 Default bean names [default_name] | 7 | 7 | 0 | 0 | 0 | 0.00%
2.6.3 Beans with no name [beans_with_no_name] | 2 | 1 | 0 | 0 | 0 | 0.00%
2.7 Alternatives [alternatives] | 1 | 0 | 0 | 0 | 0 |
2.7.1 Declaring an alternative [declaring_alternative] | 7 | 6 | 0 | 0 | 0 | 0.00%
2.8 Stereotypes [stereotypes] | 5 | 4 | 0 | 0 | 0 | 0.00%
2.8.1 Defining new stereotypes [defining_new_stereotype] | 6 | 1 | 0 | 0 | 0 | 0.00%
2.8.1.1 Declaring the default scope for a stereotype [stereotype_default_scope] | 2 | 2 | 0 | 0 | 0 | 0.00%
2.8.1.2 Specifying interceptor bindings for a stereotype [specify_stereotype_interceptor_bindings] | 4 | 4 | 0 | 0 | 0 | 0.00%
2.8.1.3 Declaring a @Named stereotype [named_stereotype] | 5 | 3 | 0 | 0 | 0 | 0.00%
2.8.1.4 Declaring an @Alternative stereotype [alternative_stereotype] | 1 | 1 | 0 | 0 | 0 | 0.00%
2.8.1.5 Stereotypes with additional stereotypes [stereotypes_with_additional_stereotypes] | 3 | 2 | 0 | 0 | 0 | 0.00%
2.8.2 Declaring the stereotypes for a bean [declaring_stereotypes] | 5 | 5 | 0 | 0 | 0 | 0.00%
2.8.3 Built-in stereotypes [builtin_stereotypes] | 1 | 0 | 0 | 0 | 0 |
2.9 Problems detected automatically by the container [exceptions] | 7 | 4 | 0 | 0 | 0 | 0.00%
2.10 Priority ordering [priorities] | 0 | 0 | 0 | 0 | 0 |
3 Programming model [implementation] | 0 | 0 | 0 | 0 | 0 |
3.1 Managed beans [managed_beans] | 5 | 5 | 0 | 0 | 0 | 0.00%
3.1.1 Which Java classes are managed beans? [what_classes_are_beans] | 9 | 8 | 0 | 0 | 0 | 0.00%
3.1.2 Bean types of a managed bean [managed_bean_types] | 2 | 2 | 0 | 0 | 0 | 0.00%
3.1.3 Declaring a managed bean [declaring_managed_bean] | 7 | 6 | 0 | 0 | 0 | 0.00%
3.1.4 Specializing a managed bean [specialize_managed_bean] | 6 | 6 | 0 | 0 | 0 | 0.00%
3.1.5 Default bean name for a managed bean [managed_bean_name] | 1 | 1 | 0 | 0 | 0 | 0.00%
3.2 Producer methods [producer_method] | 14 | 14 | 0 | 0 | 0 | 0.00%
3.2.1 Bean types of a producer method [producer_method_types] | 5 | 5 | 0 | 0 | 0 | 0.00%
3.2.2 Declaring a producer method [declaring_producer_method] | 13 | 13 | 0 | 0 | 0 | 0.00%
3.2.3 Specializing a producer method [specialize_producer_method] | 3 | 3 | 0 | 0 | 0 | 0.00%
3.2.4 Default bean name for a producer method [producer_method_name] | 2 | 2 | 0 | 0 | 0 | 0.00%
3.3 Producer fields [producer_field] | 14 | 13 | 0 | 0 | 0 | 0.00%
3.3.1 Bean types of a producer field [producer_field_types] | 5 | 5 | 0 | 0 | 0 | 0.00%
3.3.2 Declaring a producer field [declaring_producer_field] | 8 | 8 | 0 | 0 | 0 | 0.00%
3.3.3 Default bean name for a producer field [producer_field_name] | 1 | 1 | 0 | 0 | 0 | 0.00%
3.4 Disposer methods [disposer_method] | 4 | 4 | 0 | 0 | 0 | 0.00%
3.4.1 Disposed parameter of a disposer method [disposer_method_disposed_parameter] | 3 | 3 | 0 | 0 | 0 | 0.00%
3.4.2 Declaring a disposer method [declaring_disposer_method] | 10 | 10 | 0 | 0 | 0 | 0.00%
3.4.3 Disposer method resolution [disposer_method_resolution] | 4 | 4 | 0 | 0 | 0 | 0.00%
3.5 Bean constructors [bean_constructors] | 1 | 1 | 0 | 0 | 0 | 0.00%
3.5.1 Declaring a bean constructor [declaring_bean_constructor] | 8 | 8 | 0 | 0 | 0 | 0.00%
3.6 Injected fields [injected_fields] | 1 | 1 | 0 | 0 | 0 | 0.00%
3.6.1 Declaring an injected field [declaring_injected_field] | 2 | 2 | 0 | 0 | 0 | 0.00%
3.7 Initializer methods [initializer_methods] | 4 | 3 | 0 | 0 | 0 | 0.00%
3.7.1 Declaring an initializer method [declaring_initializer] | 8 | 8 | 0 | 0 | 0 | 0.00%
3.8 The default qualifier at injection points [injection_point_default_qualifier] | 1 | 1 | 0 | 0 | 0 | 0.00%
3.9 The qualifier @Named at injection points [named_at_injection_point] | 2 | 2 | 0 | 0 | 0 | 0.00%
3.10 @New qualified beans [new] | 24 | 23 | 0 | 0 | 0 | 0.00%
3.11 Unproxyable bean types [unproxyable] | 10 | 10 | 0 | 0 | 0 | 0.00%
4 Inheritance and specialization [inheritance] | 0 | 0 | 0 | 0 | 0 |
4.1 Inheritance of type-level metadata [type_level_inheritance] | 22 | 18 | 0 | 0 | 0 | 0.00%
4.2 Inheritance of member-level metadata [member_level_inheritance] | 20 | 20 | 0 | 0 | 0 | 0.00%
4.3 Specialization [specialization] | 5 | 4 | 0 | 0 | 0 | 0.00%
4.3.1 Direct and indirect specialization [direct_and_indirect_specialization] | 8 | 7 | 0 | 0 | 0 | 0.00%
5 Dependency injection and lookup [injection_and_resolution] | 2 | 1 | 0 | 0 | 0 | 0.00%
5.1 Modularity [selection] | 5 | 4 | 0 | 0 | 0 | 0.00%
5.1.1 Declaring selected alternatives [declaring_selected_alternatives] | 1 | 0 | 0 | 0 | 0 |
5.1.1.1 Declaring selected alternatives for an application [declaring_selected_alternatives_application] | 4 | 4 | 0 | 0 | 0 | 0.00%
5.1.1.2 Declaring selected alternatives for a bean archive [declaring_selected_alternatives_bean_archive] | 11 | 10 | 0 | 0 | 0 | 0.00%
5.1.2 Enabled and disabled beans [enablement] | 1 | 0 | 0 | 0 | 0 |
5.1.3 Inconsistent specialization [inconsistent_specialization] | 1 | 1 | 0 | 0 | 0 | 0.00%
5.1.4 Inter-module injection [inter_module_injection] | 14 | 13 | 0 | 0 | 0 | 0.00%
5.2 Typesafe resolution [typesafe_resolution] | 0 | 0 | 0 | 0 | 0 |
5.2.1 Performing typesafe resolution [performing_typesafe_resolution] | 12 | 12 | 0 | 0 | 0 | 0.00%
5.2.2 Unsatisfied and ambiguous dependencies [unsatisfied_and_ambig_dependencies] | 9 | 9 | 0 | 0 | 0 | 0.00%
5.2.3 Legal injection point types [legal_injection_point_types] | 3 | 3 | 0 | 0 | 0 | 0.00%
5.2.4 Assignability of raw and parameterized types [assignable_parameters] | 10 | 10 | 0 | 0 | 0 | 0.00%
5.2.5 Primitive types and null values [primitive_types_and_null_values] | 3 | 3 | 0 | 0 | 0 | 0.00%
5.2.6 Qualifier annotations with members [qualifier_annotation_members] | 3 | 1 | 0 | 0 | 0 | 0.00%
5.2.7 Multiple qualifiers [multiple_qualifiers] | 4 | 4 | 0 | 0 | 0 | 0.00%
5.3 EL name resolution [name_resolution] | 2 | 2 | 0 | 0 | 0 | 0.00%
5.3.1 Ambiguous EL names [ambig_names] | 4 | 4 | 0 | 0 | 0 | 0.00%
5.4 Client proxies [client_proxies] | 5 | 3 | 0 | 0 | 0 | 0.00%
5.4.1 Client proxy invocation [client_proxy_invocation] | 3 | 2 | 0 | 0 | 0 | 0.00%
5.5 Dependency injection [injection] | 4 | 4 | 0 | 0 | 0 | 0.00%
5.5.1 Injection using the bean constructor [instantiation] | 2 | 2 | 0 | 0 | 0 | 0.00%
5.5.2 Injection of fields and initializer methods [fields_initializer_methods] | 6 | 6 | 0 | 0 | 0 | 0.00%
5.5.3 Destruction of dependent objects [dependent_objects_destruction] | 1 | 1 | 0 | 0 | 0 | 0.00%
5.5.4 Invocation of producer or disposer methods [producer_or_disposer_methods_invocation] | 6 | 6 | 0 | 0 | 0 | 0.00%
5.5.5 Access to producer field values [producer_fields_access] | 2 | 2 | 0 | 0 | 0 | 0.00%
5.5.6 Invocation of observer methods [observers_method_invocation] | 4 | 4 | 0 | 0 | 0 | 0.00%
5.5.7 Injection point metadata [injection_point] | 24 | 24 | 0 | 0 | 0 | 0.00%
5.5.8 Bean metadata [bean_metadata] | 17 | 17 | 0 | 0 | 0 | 0.00%
5.6 Programmatic lookup [programmatic_lookup] | 5 | 5 | 0 | 0 | 0 | 0.00%
5.6.1 The Instance interface [dynamic_lookup] | 22 | 21 | 0 | 0 | 0 | 0.00%
5.6.2 The built-in Instance [builtin_instance] | 6 | 4 | 0 | 0 | 0 | 0.00%
5.6.3 Using AnnotationLiteral and TypeLiteral [annotationliteral_typeliteral] | 2 | 2 | 0 | 0 | 0 | 0.00%
5.6.4 Built-in annotation literals [built_in_annotation_literals] | 0 | 0 | 0 | 0 | 0 |
6 Scopes and contexts [contexts] | 0 | 0 | 0 | 0 | 0 |
6.1 The Contextual interface [contextual] | 4 | 2 | 0 | 0 | 0 | 0.00%
6.1.1 The CreationalContext interface [creational_context] | 7 | 3 | 0 | 0 | 0 | 0.00%
6.2 The Context interface [context] | 15 | 14 | 0 | 0 | 0 | 0.00%
6.3 Normal scopes and pseudo-scopes [normal_scope] | 8 | 3 | 0 | 0 | 0 | 0.00%
6.4 Dependent pseudo-scope [dependent_context] | 10 | 10 | 0 | 0 | 0 | 0.00%
6.4.1 Dependent objects [dependent_objects] | 7 | 7 | 0 | 0 | 0 | 0.00%
6.4.2 Destruction of objects with scope @Dependent [dependent_destruction] | 11 | 10 | 0 | 0 | 0 | 0.00%
6.5 Contextual instances and contextual references [contextual_instances_and_references] | 0 | 0 | 0 | 0 | 0 |
6.5.1 The active context object for a scope [active_context] | 2 | 2 | 0 | 0 | 0 | 0.00%
6.5.2 Activating Built In Contexts [activating_builtin_contexts] | 1 | 0 | 0 | 0 | 0 |
6.5.2.1 6.5.2.1. Activating a Request Context [activating_request_context] | 9 | 9 | 0 | 0 | 0 | 0.00%
6.5.3 Contextual instance of a bean [contextual_instance] | 4 | 3 | 0 | 0 | 0 | 0.00%
6.5.4 Contextual reference for a bean [contextual_reference] | 6 | 6 | 0 | 0 | 0 | 0.00%
6.5.5 Contextual reference validity [contextual_reference_validity] | 3 | 2 | 0 | 0 | 0 | 0.00%
6.5.6 Injectable references [injectable_reference] | 2 | 1 | 0 | 0 | 0 | 0.00%
6.5.7 Injectable reference validity [injectable_reference_validity] | 2 | 1 | 0 | 0 | 0 | 0.00%
6.6 Passivation and passivating scopes [passivating_scope] | 1 | 1 | 0 | 0 | 0 | 0.00%
6.6.1 Passivation capable beans [passivation_capable] | 13 | 8 | 0 | 0 | 0 | 0.00%
6.6.2 Passivation capable injection points [passivation_capable_injection_points] | 6 | 6 | 0 | 0 | 0 | 0.00%
6.6.3 Passivation capable dependencies [passivation_capable_dependency] | 7 | 7 | 0 | 0 | 0 | 0.00%
6.6.4 Passivating scopes [passivating_scopes] | 3 | 1 | 0 | 0 | 0 | 0.00%
6.6.5 Validation of passivation capable beans and dependencies [passivation_validation] | 22 | 21 | 0 | 0 | 0 | 0.00%
6.7 Context management for built-in scopes [builtin_contexts] | 5 | 2 | 0 | 0 | 0 | 0.00%
6.7.1 Request context lifecycle [request_context] | 7 | 7 | 0 | 0 | 0 | 0.00%
6.7.2 Session context lifecycle [session_context] | 0 | 0 | 0 | 0 | 0 |
6.7.3 Application context lifecycle [application_context] | 3 | 3 | 0 | 0 | 0 | 0.00%
6.7.4 Conversation context lifecycle [conversation_context] | 0 | 0 | 0 | 0 | 0 |
6.7.5 The Conversation interface [conversation] | 14 | 14 | 0 | 0 | 0 | 0.00%
7 Lifecycle of contextual instances [lifecycle] | 0 | 0 | 0 | 0 | 0 |
7.1 Restriction upon bean instantiation [bean_instantiation_restriction] | 0 | 0 | 0 | 0 | 0 |
7.2 Container invocations and interception [biz_method] | 19 | 19 | 0 | 0 | 0 | 0.00%
7.3 Lifecycle of contextual instances [contextual_instance_lifecycle] | 0 | 0 | 0 | 0 | 0 |
7.3.1 Lifecycle of managed beans [managed_bean_lifecycle] | 2 | 2 | 0 | 0 | 0 | 0.00%
7.3.2 Lifecycle of producer methods [producer_method_lifecycle] | 5 | 5 | 0 | 0 | 0 | 0.00%
7.3.3 Lifecycle of producer fields [producer_field_lifecycle] | 4 | 4 | 0 | 0 | 0 | 0.00%
8 Decorators [decorators] | 3 | 2 | 0 | 0 | 0 | 0.00%
8.1 Decorator beans [decorator_bean] | 6 | 5 | 0 | 0 | 0 | 0.00%
8.1.1 Declaring a decorator [decorator_annotation] | 1 | 1 | 0 | 0 | 0 | 0.00%
8.1.2 Decorator delegate injection points [delegate_attribute] | 10 | 10 | 0 | 0 | 0 | 0.00%
8.1.3 Decorated types of a decorator [decorated_types] | 7 | 7 | 0 | 0 | 0 | 0.00%
8.2 Decorator enablement and ordering [enabled_decorators] | 4 | 3 | 0 | 0 | 0 | 0.00%
8.2.1 Decorator enablement and ordering for an application [enabled_decorators_priority] | 4 | 2 | 0 | 0 | 0 | 0.00%
8.2.2 Decorator enablement and ordering for a bean archive [enabled_decorators_bean_archive] | 5 | 5 | 0 | 0 | 0 | 0.00%
8.3 Decorator resolution [decorator_resolution] | 4 | 4 | 0 | 0 | 0 | 0.00%
8.3.1 Assignability of raw and parameterized types for delegate injection points [delegate_assignable_parameters] | 9 | 9 | 0 | 0 | 0 | 0.00%
8.4 Decorator invocation [decorator_invocation] | 8 | 8 | 0 | 0 | 0 | 0.00%
9 Interceptor bindings [interceptors] | 0 | 0 | 0 | 0 | 0 |
9.1 Interceptor binding types [interceptor_bindings] | 0 | 0 | 0 | 0 | 0 |
9.1.1 Interceptor bindings for stereotypes [stereotype_interceptor_bindings] | 3 | 2 | 0 | 0 | 0 | 0.00%
9.2 Declaring the interceptor bindings of an interceptor [declaring_interceptor] | 0 | 0 | 0 | 0 | 0 |
9.3 Binding an interceptor to a bean [binding_interceptor_to_bean] | 4 | 4 | 0 | 0 | 0 | 0.00%
9.4 Interceptor enablement and ordering [enabled_interceptors] | 12 | 11 | 0 | 0 | 0 | 0.00%
9.5 Interceptor resolution [interceptor_resolution] | 8 | 7 | 0 | 0 | 0 | 0.00%
10 Events [events] | 0 | 0 | 0 | 0 | 0 |
10.1 Event types and qualifier types [event_types_and_qualifier_types] | 7 | 6 | 0 | 0 | 0 | 0.00%
10.2 Firing events [firing_events] | 3 | 3 | 0 | 0 | 0 | 0.00%
10.2.1 Firing events synchronously [firing_events_synchronously] | 3 | 3 | 0 | 0 | 0 | 0.00%
10.2.2 Firing events asynchronously [firing_events_asynchronously] | 1 | 1 | 0 | 0 | 0 | 0.00%
10.2.3 The Event interface [event] | 14 | 11 | 0 | 0 | 0 | 0.00%
10.2.4 The built-in Event [builtin_event] | 7 | 7 | 0 | 0 | 0 | 0.00%
10.3 Observer resolution [observer_resolution] | 8 | 6 | 0 | 0 | 0 | 0.00%
10.3.1 Assignability of type variables, raw and parameterized types [observers_assignability] | 6 | 6 | 0 | 0 | 0 | 0.00%
10.3.2 Event qualifier types with members [event_qualifier_types_with_members] | 2 | 1 | 0 | 0 | 0 | 0.00%
10.3.3 Multiple event qualifiers [multiple_event_qualifiers] | 2 | 2 | 0 | 0 | 0 | 0.00%
10.4 Observer methods [observer_methods] | 5 | 4 | 0 | 0 | 0 | 0.00%
10.4.1 Event parameter of an observer method [observer_method_event_parameter] | 7 | 7 | 0 | 0 | 0 | 0.00%
10.4.2 Declaring an observer method [observes] | 11 | 11 | 0 | 0 | 0 | 0.00%
10.4.3 The EventMetadata interface [event_metadata] | 5 | 5 | 0 | 0 | 0 | 0.00%
10.4.4 Conditional observer methods [conditional_observer_methods] | 3 | 3 | 0 | 0 | 0 | 0.00%
10.4.5 Transactional observer methods [transactional_observer_methods] | 8 | 7 | 0 | 0 | 0 | 0.00%
10.5 Observer notification [observer_notification] | 11 | 8 | 0 | 0 | 0 | 0.00%
10.5.1 Handling multiple exceptions thrown during an asynchronous event [async_exception] | 2 | 2 | 0 | 0 | 0 | 0.00%
10.5.2 Observer ordering [observer_ordering] | 3 | 2 | 0 | 0 | 0 | 0.00%
10.5.3 Observer method invocation context [observer_method_invocation_context] | 5 | 5 | 0 | 0 | 0 | 0.00%
11 Portable extensions [spi] | 4 | 0 | 0 | 0 | 0 |
11.1 The Bean interface [bean] | 8 | 6 | 0 | 0 | 0 | 0.00%
11.1.1 The Decorator interface [decorator] | 4 | 4 | 0 | 0 | 0 | 0.00%
11.1.2 The Interceptor interface [interceptor] | 6 | 6 | 0 | 0 | 0 | 0.00%
11.1.3 The ObserverMethod interface [observer_method] | 9 | 8 | 0 | 0 | 0 | 0.00%
11.2 The Producer and InjectionTarget interfaces [injectiontarget] | 19 | 16 | 0 | 0 | 0 | 0.00%
11.3 The BeanManager object [beanmanager] | 17 | 16 | 0 | 0 | 0 | 0.00%
11.3.1 Obtaining a reference to the CDI container [provider] | 6 | 6 | 0 | 0 | 0 | 0.00%
11.3.2 Obtaining a contextual reference for a bean [bm_obtain_contextual_reference] | 3 | 3 | 0 | 0 | 0 | 0.00%
11.3.3 Obtaining an injectable reference [bm_obtain_injectable_reference] | 6 | 6 | 0 | 0 | 0 | 0.00%
11.3.4 Obtaining non-contextual instance [bm_obtain_unmanaged_instance] | 12 | 12 | 0 | 0 | 0 | 0.00%
11.3.5 Obtaining a CreationalContext [bm_obtain_creationalcontext] | 2 | 2 | 0 | 0 | 0 | 0.00%
11.3.6 Obtaining a Bean by type [bm_obtain_bean_by_type] | 7 | 7 | 0 | 0 | 0 | 0.00%
11.3.7 Obtaining a Bean by name [bm_obtain_bean_by_name] | 2 | 2 | 0 | 0 | 0 | 0.00%
11.3.8 Obtaining a passivation capable bean by identifier [bm_obtain_passivation_capable_bean] | 1 | 1 | 0 | 0 | 0 | 0.00%
11.3.9 Resolving an ambiguous dependency [bm_resolve_ambiguous_dep] | 4 | 4 | 0 | 0 | 0 | 0.00%
11.3.10 Validating an injection point [bm_validate_ip] | 1 | 1 | 0 | 0 | 0 | 0.00%
11.3.11 Firing an event [bm_fire_event] | 6 | 6 | 0 | 0 | 0 | 0.00%
11.3.12 Observer method resolution [bm_observer_method_resolution] | 5 | 5 | 0 | 0 | 0 | 0.00%
11.3.13 Decorator resolution [bm_decorator_resolution] | 5 | 5 | 0 | 0 | 0 | 0.00%
11.3.14 Interceptor resolution [bm_interceptor_resolution] | 4 | 4 | 0 | 0 | 0 | 0.00%
11.3.15 Determining if an annotation is a qualifier type, scope type, stereotype or interceptor binding type [bm_determining_annotation] | 7 | 7 | 0 | 0 | 0 | 0.00%
11.3.16 Determining the hash code and equivalence of qualifiers and interceptor bindings [bm_determining_hash] | 4 | 4 | 0 | 0 | 0 | 0.00%
11.3.17 Obtaining the active Context for a scope [bm_obtain_active_context] | 1 | 1 | 0 | 0 | 0 | 0.00%
11.3.18 Obtaining the ELResolver [bm_obtain_elresolver] | 1 | 1 | 0 | 0 | 0 | 0.00%
11.3.19 Obtaining an AnnotatedType for a class [bm_obtain_annotatedtype] | 1 | 1 | 0 | 0 | 0 | 0.00%
11.3.20 Obtaining an InjectionTarget for a class [bm_obtain_injectiontarget] | 4 | 4 | 0 | 0 | 0 | 0.00%
11.3.21 Obtaining a Producer for a field or method [bm_obtain_producer] | 4 | 4 | 0 | 0 | 0 | 0.00%
11.3.22 Obtaining an InjectionPoint [bm_obtain_injectionpoint] | 3 | 3 | 0 | 0 | 0 | 0.00%
11.3.23 Obtaining a BeanAttributes [bm_obtain_beanattributes] | 3 | 3 | 0 | 0 | 0 | 0.00%
11.3.24 Obtaining a Bean [bm_obtain_bean] | 2 | 2 | 0 | 0 | 0 | 0.00%
11.3.25 Obtaining the instance of an Extension [bm_obtain_extension] | 2 | 2 | 0 | 0 | 0 | 0.00%
11.3.26 Obtain an InterceptionFactory [bm_obtain_interception_factory] | 1 | 1 | 0 | 0 | 0 | 0.00%
11.3.27 Obtain an Instance [bm_obtain_instance] | 2 | 2 | 0 | 0 | 0 | 0.00%
11.4 Alternative metadata sources [alternative_metadata_sources] | 44 | 42 | 0 | 0 | 0 | 0.00%
11.4.1 AnnotatedTypeConfigurator SPI [annotated_type_configurator] | 15 | 10 | 0 | 0 | 0 | 0.00%
11.4.1.1 AnnotatedMethodConfigurator [annotated_method_configurator] | 6 | 6 | 0 | 0 | 0 | 0.00%
11.4.1.2 AnnotatedConstructorConfigurator [annotated_constructor_configurator] | 6 | 6 | 0 | 0 | 0 | 0.00%
11.4.1.3 AnnotatedParameterConfigurator [annotated_parameter_configurator] | 4 | 4 | 0 | 0 | 0 | 0.00%
11.4.1.4 AnnotatedFieldConfigurator [annotated_field_configurator] | 4 | 4 | 0 | 0 | 0 | 0.00%
11.5 Container lifecycle events [init_events] | 10 | 7 | 0 | 0 | 0 | 0.00%
11.5.1 BeforeBeanDiscovery event [before_bean_discovery] | 15 | 15 | 0 | 0 | 0 | 0.00%
11.5.2 AfterTypeDiscovery event [after_type_discovery] | 15 | 14 | 0 | 0 | 0 | 0.00%
11.5.3 AfterBeanDiscovery event [after_bean_discovery] | 18 | 17 | 0 | 0 | 0 | 0.00%
11.5.3.1 BeanConfigurator interface [bean_configurator] | 9 | 9 | 0 | 0 | 0 | 0.00%
11.5.3.2 ObserverMethodConfigurator interface [observer_method_configurator] | 13 | 13 | 0 | 0 | 0 | 0.00%
11.5.4 AfterDeploymentValidation event [after_deployment_validation] | 5 | 5 | 0 | 0 | 0 | 0.00%
11.5.5 BeforeShutdown event [before_shutdown] | 2 | 1 | 0 | 0 | 0 | 0.00%
11.5.6 ProcessAnnotatedType event [process_annotated_type] | 31 | 31 | 0 | 0 | 0 | 0.00%
11.5.7 ProcessInjectionPoint event [process_injection_point] | 10 | 10 | 0 | 0 | 0 | 0.00%
11.5.7.1 InjectionPointConfigurator interface [injection_point_configurator] | 5 | 5 | 0 | 0 | 0 | 0.00%
11.5.8 ProcessInjectionTarget event [process_injection_target] | 8 | 8 | 0 | 0 | 0 | 0.00%
11.5.9 ProcessBeanAttributes event [process_bean_attributes] | 22 | 22 | 0 | 0 | 0 | 0.00%
11.5.9.1 BeanAttributesConfigurator interface [bean_attributes_configurator] | 10 | 10 | 0 | 0 | 0 | 0.00%
11.5.10 ProcessBean event [process_bean] | 25 | 25 | 0 | 0 | 0 | 0.00%
11.5.11 ProcessProducer event [process_producer] | 17 | 17 | 0 | 0 | 0 | 0.00%
11.5.11.1 ProducerConfigurator interface [producer_configurator] | 2 | 2 | 0 | 0 | 0 | 0.00%
11.5.12 ProcessObserverMethod event [process_observer_method] | 13 | 13 | 0 | 0 | 0 | 0.00%
11.6 Configurators interfaces [configurators] | 7 | 0 | 0 | 0 | 0 |
11.7 The InterceptionFactory interface [interception_factory] | 9 | 8 | 0 | 0 | 0 | 0.00%
12 Packaging and deployment [packaging_deployment] | 5 | 0 | 0 | 0 | 0 |
12.1 Bean archives [bean_archive] | 16 | 7 | 0 | 0 | 0 | 0.00%
12.2 Application initialization lifecycle [initialization] | 10 | 9 | 0 | 0 | 0 | 0.00%
12.3 Application shutdown lifecycle [shutdown] | 2 | 2 | 0 | 0 | 0 | 0.00%
12.4 Type and Bean discovery [type_bean_discovery] | 1 | 0 | 0 | 0 | 0 |
12.4.1 Type discovery [type_discovery_steps] | 4 | 4 | 0 | 0 | 0 | 0.00%
12.4.2 Exclude filters [exclude_filters] | 8 | 8 | 0 | 0 | 0 | 0.00%
12.4.3 Trimmed bean archive [trimmed_bean_archive] | 1 | 1 | 0 | 0 | 0 | 0.00%
12.4.4 Bean discovery [bean_discovery_steps] | 18 | 13 | 0 | 0 | 0 | 0.00%
13 Bootstrapping a CDI container in Java SE [se_bootstrap] | 18 | 17 | 0 | 0 | 0 | 0.00%
13.1 SeContainerInitializer class [se_container_initializer] | 3 | 2 | 0 | 0 | 0 | 0.00%
13.2 SeContainer interface [se_container] | 7 | 6 | 0 | 0 | 0 | 0.00%
14 Scopes and contexts in Java SE [contexts_se] | 0 | 0 | 0 | 0 | 0 |
14.1 Context management for built-in scopes in Java SE [builtin_contexts_se] | 0 | 0 | 0 | 0 | 0 |
14.1.1 Application context lifecycle in Java SE [application_context_se] | 4 | 4 | 0 | 0 | 0 | 0.00%
15 Packaging and deployment in Java SE [packaging_deployment_se] | 0 | 0 | 0 | 0 | 0 |
15.1 Bean archive in Java SE [bean_archive_se] | 2 | 2 | 0 | 0 | 0 | 0.00%
16 Portable extensions in Java SE [spi_se] | 0 | 0 | 0 | 0 | 0 |
16.1 The `BeanManager` object in Java SE [beanmanager_se] | 0 | 0 | 0 | 0 | 0 |
16.1.1 Obtaining a reference to the CDI container in Java SE [provider_se] | 1 | 0 | 0 | 0 | 0 |
17 Extended Concepts for Jakarta EE [concepts_ee] | 0 | 0 | 0 | 0 | 0 |
17.1 Functionality provided by the container to the bean in Jakarta EE [capabilities_ee] | 0 | 0 | 0 | 0 | 0 |
17.2 Bean types for Jakarta EE component [bean_types_ee] | 2 | 2 | 0 | 0 | 0 | 0.00%
17.3 Scopes [scopes_ee] | 0 | 0 | 0 | 0 | 0 |
17.3.1 Built-in scope types in Jakarta EE [builtin_scopes_ee] | 1 | 0 | 0 | 0 | 0 |
17.4 Default bean discovery mode for Jakarta EE [default_bean_discovery_ee] | 5 | 5 | 0 | 0 | 0 | 0.00%
17.5 Bean names in Jakarta EE [names_ee] | 1 | 1 | 0 | 0 | 0 | 0.00%
17.5.1 Default bean names for EJB session beans [default_name_ee] | 1 | 0 | 0 | 0 | 0 |
18 Addition to programming model for Jakarta EE [implementation_ee] | 0 | 0 | 0 | 0 | 0 |
18.1 Managed beans in Jakarta EE [managed_beans_ee] | 0 | 0 | 0 | 0 | 0 |
18.1.1 Which Java classes are managed beans in Jakarta EE? [what_classes_are_beans_ee] | 2 | 2 | 0 | 0 | 0 | 0.00%
18.2 EJB Session beans [session_beans] | 11 | 8 | 0 | 0 | 0 | 0.00%
18.2.1 EJB remove methods of session beans [session_bean_ejb_remove_method] | 4 | 4 | 0 | 0 | 0 | 0.00%
18.2.2 Bean types of a session bean [session_bean_types] | 5 | 5 | 0 | 0 | 0 | 0.00%
18.2.3 Declaring a session bean [declaring_session_bean] | 6 | 6 | 0 | 0 | 0 | 0.00%
18.2.4 Specializing a session bean [specialize_session_bean] | 3 | 3 | 0 | 0 | 0 | 0.00%
18.2.5 Default bean name for a session bean [session_bean_name] | 1 | 1 | 0 | 0 | 0 | 0.00%
18.3 Producer methods on EJB session bean [producer_method_ee] | 2 | 2 | 0 | 0 | 0 | 0.00%
18.3.1 Declaring a producer method in an EJB session bean [declaring_producer_method_ee] | 2 | 2 | 0 | 0 | 0 | 0.00%
18.4 Producer field on EJB session bean [producer_field_ee] | 1 | 1 | 0 | 0 | 0 | 0.00%
18.4.1 Declaring a producer field in an EJB session bean [declaring_producer_field_ee] | 1 | 1 | 0 | 0 | 0 | 0.00%
18.5 Disposer methods on EJB session bean [disposer_method_ee] | 1 | 1 | 0 | 0 | 0 | 0.00%
18.5.1 Declaring a disposer method on an EJB session bean [declaring_disposer_method_ee] | 1 | 1 | 0 | 0 | 0 | 0.00%
18.6 Jakarta EE components [javaee_components] | 5 | 5 | 0 | 0 | 0 | 0.00%
18.7 Resources [resources] | 2 | 0 | 0 | 0 | 0 |
18.7.1 Declaring a resource [declaring_resource] | 10 | 8 | 0 | 0 | 0 | 0.00%
18.7.2 Bean types of a resource [resource_types] | 6 | 5 | 0 | 0 | 0 | 0.00%
18.8 Additional built-in beans [additional_builtin_beans] | 6 | 6 | 0 | 0 | 0 | 0.00%
18.9 Injected fields in Jakarta EE [injected_fields_ee] | 1 | 1 | 0 | 0 | 0 | 0.00%
18.10 Initializer methods in Jakarta EE [initializer_methods_ee] | 3 | 3 | 0 | 0 | 0 | 0.00%
18.11 @New qualified beans in Jakarta EE [new_ee] | 19 | 19 | 0 | 0 | 0 | 0.00%
18.12 Inheritance of type-level metadata in Jakarta EE [type_level_inheritance_ee] | 18 | 18 | 0 | 0 | 0 | 0.00%
18.13 Inheritance of member-level metadata in Jakarta EE [member_level_inheritance_ee] | 16 | 16 | 0 | 0 | 0 | 0.00%
18.14 Specialization in Jakarta EE [specialization_ee] | 0 | 0 | 0 | 0 | 0 |
18.14.1 Direct and indirect specialization in Jakarta EE [direct_and_indirect_specialization_ee] | 4 | 4 | 0 | 0 | 0 | 0.00%
19 Dependency injection, lookup and EL in Jakarta EE [injection_el_resolution_ee] | 0 | 0 | 0 | 0 | 0 |
19.1 Modularity in Jakarta EE [selection_ee] | 4 | 4 | 0 | 0 | 0 | 0.00%
19.1.1 Declaring selected alternatives for an application in Jakarta EE [declaring_selected_alternatives_application_ee] | 2 | 2 | 0 | 0 | 0 | 0.00%
19.1.2 Declaring selected alternatives for a bean archive in Jakarta EE [declaring_selected_alternatives_bean_archive_ee] | 2 | 1 | 0 | 0 | 0 | 0.00%
19.1.3 Unsatisfied and ambiguous dependencies in Jakarta EE [unsatisfied_and_ambig_dependencies_ee] | 2 | 2 | 0 | 0 | 0 | 0.00%
19.2 EL name resolution [name_resolution_ee] | 1 | 1 | 0 | 0 | 0 | 0.00%
19.2.1 Ambiguous EL names [ambig_names_ee] | 0 | 0 | 0 | 0 | 0 |
19.3 Dependency injection in Jakarta EE [injection_ee] | 10 | 9 | 0 | 0 | 0 | 0.00%
19.3.1 Injection using the bean constructor in Jakarta EE [instantiation_ee] | 3 | 3 | 0 | 0 | 0 | 0.00%
19.3.2 Injection of fields and initializer methods in Jakarta EE [fields_initializer_methods_ee] | 34 | 34 | 0 | 0 | 0 | 0.00%
19.3.3 Destruction of dependent objects in Jakarta EE [dependent_objects_destruction_ee] | 1 | 1 | 0 | 0 | 0 | 0.00%
19.3.4 Bean metadata in Jakarta EE [bean_metadata_ee] | 1 | 1 | 0 | 0 | 0 | 0.00%
20 Scopes and contexts in Jakarta EE [contexts_ee] | 0 | 0 | 0 | 0 | 0 |
20.1 Dependent pseudo-scope in Jakarta EE [dependent_context_ee] | 1 | 1 | 0 | 0 | 0 | 0.00%
20.1.1 Dependent objects in Jakarta EE [dependent_objects_ee] | 0 | 0 | 0 | 0 | 0 |
20.1.2 Destruction of objects with scope @Dependent in Jakarta EE [dependent_destruction_ee] | 2 | 2 | 0 | 0 | 0 | 0.00%
20.1.3 Dependent pseudo-scope and Unified EL [dependent_scope_el] | 2 | 1 | 0 | 0 | 0 | 0.00%
20.2 Passivation and passivating scopes in Jakarta EE [passivating_scope_ee] | 0 | 0 | 0 | 0 | 0 |
20.2.1 Passivation capable beans in Jakarta EE [passivation_capable_ee] | 3 | 2 | 0 | 0 | 0 | 0.00%
20.2.2 Passivation capable dependencies in java EE [passivation_capable_dependency_ee] | 8 | 8 | 0 | 0 | 0 | 0.00%
20.2.3 Validation of passivation capable beans and dependencies in Jakarta EE [passivation_validation_ee] | 10 | 10 | 0 | 0 | 0 | 0.00%
20.3 Context management for built-in scopes in Jakarta EE [builtin_contexts_ee] | 0 | 0 | 0 | 0 | 0 |
20.3.1 Request context lifecycle in Jakarta EE [request_context_ee] | 24 | 24 | 0 | 0 | 0 | 0.00%
20.3.2 Session context lifecycle in Jakarta EE [session_context_ee] | 11 | 11 | 0 | 0 | 0 | 0.00%
20.3.3 Application context lifecycle in Jakarta EE [application_context_ee] | 18 | 17 | 0 | 0 | 0 | 0.00%
20.3.4 Conversation context lifecycle in Jakarta EE [conversation_context_ee] | 30 | 27 | 0 | 0 | 0 | 0.00%
21 Lifecycle of contextual instances [lifecycle_ee] | 0 | 0 | 0 | 0 | 0 |
21.1 Container invocations and interception in Jakarta EE [biz_method_ee] | 8 | 7 | 0 | 0 | 0 | 0.00%
21.1.1 Lifecycle of EJB stateful session beans [stateful_lifecycle] | 3 | 2 | 0 | 0 | 0 | 0.00%
21.1.2 Lifecycle of EJB stateless and singleton session beans [stateless_lifecycle] | 3 | 2 | 0 | 0 | 0 | 0.00%
21.1.3 Lifecycle of resources [resource_lifecycle] | 20 | 19 | 0 | 0 | 0 | 0.00%
22 Decorators in Jakarta EE [decorators_ee] | 7 | 7 | 0 | 0 | 0 | 0.00%
22.1 Decorator beans in Jakarta EE [decorator_bean_ee] | 10 | 10 | 0 | 0 | 0 | 0.00%
23 Interceptor bindings in Jakarta EE [interceptors_ee] | 1 | 1 | 0 | 0 | 0 | 0.00%
23.1 Interceptor resolution in Jakarta EE [interceptor_resolution_ee] | 1 | 1 | 0 | 0 | 0 | 0.00%
24 Events in Jakarta EE [events_ee] | 0 | 0 | 0 | 0 | 0 |
24.1 Observer methods in EJB session beans [observer_methods_ee] | 1 | 1 | 0 | 0 | 0 | 0.00%
24.1.1 Declaring an observer method in an EJB [observes_ee] | 1 | 1 | 0 | 0 | 0 | 0.00%
24.1.2 Observer method invocation context in Jakarta EE [observer_method_invocation_context_ee] | 2 | 2 | 0 | 0 | 0 | 0.00%
25 Portable extensions in Jakarta EE [spi_ee] | 0 | 0 | 0 | 0 | 0 |
25.1 The Bean interface in Jakarta EE [bean_ee] | 0 | 0 | 0 | 0 | 0 |
25.1.1 The Interceptor interface in Jakarta EE [interceptor_ee] | 1 | 1 | 0 | 0 | 0 | 0.00%
25.2 InjectionTarget interface in Jakarta EE [injectiontarget_ee] | 3 | 3 | 0 | 0 | 0 | 0.00%
25.3 The BeanManager object in Jakarta EE [beanmanager_ee] | 0 | 0 | 0 | 0 | 0 |
25.3.1 Obtaining a reference to the CDI container in Jakarta EE [provider_ee] | 2 | 2 | 0 | 0 | 0 | 0.00%
25.3.2 Wrapping a Unified EL ExpressionFactory [bm_wrap_expressionfactory] | 2 | 2 | 0 | 0 | 0 | 0.00%
25.4 Alternative metadata sources and EJB [alternative_metadata_sources_ee] | 1 | 1 | 0 | 0 | 0 | 0.00%
25.5 Addition to Container lifecycle events in Jakarta EE [init_events_ee] | 0 | 0 | 0 | 0 | 0 |
25.5.1 ProcessInjectionPoint event and EJB [process_injection_point_ee] | 1 | 1 | 0 | 0 | 0 | 0.00%
25.5.2 ProcessInjectionTarget event and EJB [process_injection_target_ee] | 29 | 29 | 0 | 0 | 0 | 0.00%
25.5.3 ProcessBeanAttributes event and EJB [process_bean_attributes_ee] | 1 | 1 | 0 | 0 | 0 | 0.00%
25.5.4 ProcessBean event and EJB [process_bean_ee] | 9 | 9 | 0 | 0 | 0 | 0.00%
26 Packaging and deployment in Jakarta EE [packaging_deployment_ee] | 0 | 0 | 0 | 0 | 0 |
26.1 Bean archive with EJB Session Beans [bean_archive_ee] | 23 | 18 | 0 | 0 | 0 | 0.00%
26.2 Type and Bean discovery for EJB [type_bean_discovery_ee] | 9 | 9 | 0 | 0 | 0 | 0.00%
26.2.1 Bean discovery in Jakarta EE [bean_discovery_steps_ee] | 11 | 11 | 0 | 0 | 0 | 0.00%
26.2.2 Trimmed bean archive in Jakarta EE [trimmed_bean_archive_ee] | 1 | 1 | 0 | 0 | 0 | 0.00%
26.3 Integration with Unified EL [el] | 3 | 3 | 0 | 0 | 0 | 0.00%

### Coverage Detail

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

#### Section 2 - Concepts [concepts]

a)

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

Coverage

No tests exist for this assertion

b)

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

Coverage

No tests exist for this assertion

c)

A bean comprises of a scope.

Coverage

No tests exist for this assertion

e)

A bean comprises of an optional bean name.

Coverage

No tests exist for this assertion

f)

A bean comprises of a set of interceptor bindings.

Coverage

No tests exist for this assertion

g)

A bean comprises of a bean implementation.

Coverage

No tests exist for this assertion

h)

A bean may or may not be an alternative.

#### Section 2.2 - Bean types [bean_types]

a)

A bean may have multiple bean types.

Coverage

No tests exist for this assertion

l)

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

Coverage

No tests exist for this assertion

#### Section 2.2.1 - Legal bean types [legal_bean_types]

a)

A bean type may be an interface.

Coverage

No tests exist for this assertion

b)

A bean type may be a concrete class.

Coverage

No tests exist for this assertion

c)

A bean type may be an abstract class.

Coverage

No tests exist for this assertion

d)

A bean type may be declared final.

Coverage

No tests exist for this assertion

e)

A bean type may have final methods.

Coverage

No tests exist for this assertion

f)

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

Coverage

No tests exist for this assertion

g)

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

Coverage

No tests exist for this assertion

i)

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

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

k)

A bean type may be a raw type.

Coverage

No tests exist for this assertion

la)

A type variable is not a legal bean type.

Coverage

No tests exist for this assertion

lb)

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

Coverage

No tests exist for this assertion

An array type whose component type is not a legal bean type.

lc)

An array type whose component type is a type variable is not a legal bean type.

Coverage

No tests exist for this assertion

ld)

An array type whose component type is a parameterized type that contains a wildcard type parameter is not a legal bean type.

Coverage

No tests exist for this assertion

#### Section 2.2.2 - Restricting the bean types of a bean [restricting_bean_types]

The bean types of a bean may be restricted by annotating the bean class or producer method or field with the annotation @jakarta.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

No tests exist for this assertion

c)

Check producer method

Coverage

No tests exist for this assertion

d)

Check producer field

Coverage

No tests exist for this assertion

e)

Check generic managed bean

Coverage

No tests exist for this assertion

g)

Check generic producer method

Coverage

No tests exist for this assertion

h)

Check generic producer field

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

l)

Check producer method

Coverage

No tests exist for this assertion

m)

Check producer field

Coverage

No tests exist for this assertion

#### Section 2.2.3 - Typecasting between bean types [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

No tests exist for this assertion

#### Section 2.3.1 - Built-in qualifier types [builtin_qualifiers]

aa)

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

No tests exist for this assertion

ab)

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

Coverage

No tests exist for this assertion

b)

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

Coverage

No tests exist for this assertion

#### Section 2.3.2 - Defining new qualifier types [defining_qualifier_types]

aa)

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 @jakarta.inject.Qualifier meta-annotation.

Coverage

No tests exist for this assertion

d)

A qualifier type may define annotation members.

#### Section 2.3.3 - Declaring the qualifiers of a bean [declaring_bean_qualifiers]

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

No tests exist for this assertion

b)

Test by annotating a producer method.

Coverage

No tests exist for this assertion

c)

Test by annotating a producer field.

Coverage

No tests exist for this assertion

d)

Any bean may declare multiple qualifier types.

Coverage

No tests exist for this assertion

#### Section 2.3.4 - Specifying qualifiers of an injected field [injected_field_qualifiers]

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

No tests exist for this assertion

b)

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

Coverage

No tests exist for this assertion

#### Section 2.3.5 - Specifying qualifiers of a method or constructor parameter [method_constructor_parameter_qualifiers]

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

No tests exist for this assertion

b)

Test initializer method.

Coverage

No tests exist for this assertion

c)

Test disposer method.

Coverage

No tests exist for this assertion

ca)

Test observer method.

Coverage

No tests exist for this assertion

d)

Test bean constructor.

Coverage

No tests exist for this assertion

#### Section 2.3.6 - Repeating qualifiers [repeating_qualifiers]

a)

A repeated qualifier behaves just as any other qualifier does

Coverage

No tests exist for this assertion

#### Section 2.4 - Scopes [scopes]

a)

All beans have a scope.

Coverage

No tests exist for this assertion

b)

A scope type is represented by an annotation type.

c)

The set of scope types is extensible.

Coverage

No tests exist for this assertion

#### Section 2.4.1 - Built-in scope types [builtin_scopes]

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

a)

The container must provide an implementation of the @RequestScoped, @ApplicationScoped and @SessionScoped annotations defined in Section 6.7, “Context management for built-in scopes”.

Coverage

No tests exist for this assertion

ba)

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

Coverage

No tests exist for this assertion

ca)

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

Coverage

No tests exist for this assertion

e)

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

#### Section 2.4.2 - Defining new scope types [defining_new_scope_type]

aa)

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

Coverage

No tests exist for this assertion

ab)

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 @jakarta.inject.Scope or @jakarta.enterprise.context.NormalScope meta-annotation.

Coverage

No tests exist for this assertion

#### Section 2.4.3 - Declaring the bean scope [declaring_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

No tests exist for this assertion

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.

ba)

Test with a bean class.

Coverage

No tests exist for this assertion

bb)

Test with a producer method.

Coverage

No tests exist for this assertion

bc)

Test with a producer field.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 2.4.4 - Default scope [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

No tests exist for this assertion

b)

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

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

e)

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

Coverage

No tests exist for this assertion

#### Section 2.5 - Default bean discovery mode [default_bean_discovery]

If the bean discovery mode is annotated then:

a)

bean classes that don’t have bean defining annotation (as defined in Section 2.5.1, “Bean defining annotations”) are not discovered

Coverage

No tests exist for this assertion

b)

producer methods (as defined in Section 3.3, “Producer methods”) whose bean class does not have a bean defining annotation are not discovered

Coverage

No tests exist for this assertion

c)

producer fields (as defined in Section 3.4, “Producer fields”) whose bean class does not have a bean defining annotation are not discovered

Coverage

No tests exist for this assertion

d)

disposer methods (as defined in Section 3.5, “Disposer methods”) whose bean class does not have a bean defining annotation are not discovered

Coverage

No tests exist for this assertion

e)

observer methods (as defined in Section 10.4.2, “Declaring an observer method”) whose bean class does not have a bean defining annotation are not discovered

Coverage

No tests exist for this assertion

#### Section 2.5.1 - Bean defining annotations [bean_defining_annotations]

a)

A bean class may have a bean defining annotation, allowing it to be placed anywhere in an application, as defined in Section 12.1. A bean class with a bean defining annotation is said to be an implicit bean.

The set of bean defining annotations contains:

ba)

@ApplicationScoped, @SessionScoped, @ConversationScoped and @RequestScoped annotations

Coverage

No tests exist for this assertion

bb)

all other normal scope types

Coverage

No tests exist for this assertion

bc)

@Interceptor annotation

Coverage

No tests exist for this assertion

bd)

@Decorator annotation

Coverage

No tests exist for this assertion

be)

all stereotype annotations (i.e. annotations annotated with @Stereotype)

Coverage

No tests exist for this assertion

bf)

the @Dependent scope annotation

Coverage

No tests exist for this assertion

ca)

Note that to ensure compatibility with other JSR-330 implementations, all pseudo-scope annotations except @Dependent are not bean defining annotations.

Coverage

No tests exist for this assertion

cb)

However, a stereotype annotation including a pseudo-scope annotation is a bean defining annotation.

Coverage

No tests exist for this assertion

#### Section 2.6 - Bean names [names]

a)

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

Coverage

No tests exist for this assertion

#### Section 2.6.1 - Declaring the bean name [declaring_bean_name]

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

a)

Test with a bean class.

Coverage

No tests exist for this assertion

b)

Test with a producer method.

Coverage

No tests exist for this assertion

c)

Test with a producer field.

Coverage

No tests exist for this assertion

#### Section 2.6.2 - Default bean names [default_name]

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

No tests exist for this assertion

b)

Test with a producer method.

Coverage

No tests exist for this assertion

c)

Test with a producer field.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

fb)

Test with a producer method.

Coverage

No tests exist for this assertion

fc)

Test with a producer field.

Coverage

No tests exist for this assertion

#### Section 2.6.3 - Beans with no name [beans_with_no_name]

a)

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

Coverage

No tests exist for this assertion

b)

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

#### Section 2.7 - Alternatives [alternatives]

a)

An alternative is a bean that must be explicitly selected if it should be available for lookup, injection or EL resolution.

#### Section 2.7.1 - Declaring an alternative [declaring_alternative]

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

aa)

Test with a bean class.

Coverage

No tests exist for this assertion

ab)

Test with a producer method.

Coverage

No tests exist for this assertion

ac)

Test with a producer field.

Coverage

No tests exist for this assertion

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

ba)

Test with a bean.

Coverage

No tests exist for this assertion

bb)

Test with a producer method.

Coverage

No tests exist for this assertion

bc)

Test with a producer field.

Coverage

No tests exist for this assertion

c)

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

#### Section 2.8 - Stereotypes [stereotypes]

a)

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

Coverage

No tests exist for this assertion

aa)

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

Coverage

No tests exist for this assertion

A bean may declare zero, one or multiple stereotypes.

b)

A bean may declare zero stereotypes.

c)

Test with one stereotype.

Coverage

No tests exist for this assertion

d)

Test with multiple stereotypes.

Coverage

No tests exist for this assertion

#### Section 2.8.1 - Defining new stereotypes [defining_new_stereotype]

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)

@Retention(RUNTIME) - untestable.

b)

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

Coverage

No tests exist for this assertion

#### Section 2.8.1.1 - Declaring the default scope for a stereotype [stereotype_default_scope]

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

No tests exist for this assertion

ab)

Test that a stereotype with multiple scopes throws an exception.

Coverage

No tests exist for this assertion

#### Section 2.8.1.2 - Specifying interceptor bindings for a stereotype [specify_stereotype_interceptor_bindings]

aa)

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

Coverage

No tests exist for this assertion

a)

A stereotype may declare zero interceptor bindings.

Coverage

No tests exist for this assertion

b)

A stereotype may declare one interceptor bindings.

Coverage

No tests exist for this assertion

c)

A stereotype may declare multiple interceptor bindings.

Coverage

No tests exist for this assertion

#### Section 2.8.1.3 - Declaring a @Named stereotype [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

No tests exist for this assertion

ab)

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

Coverage

No tests exist for this assertion

ac)

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

Coverage

No tests exist for this assertion

b)

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.8.1.4 - Declaring an @Alternative stereotype [alternative_stereotype]

a)

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

Coverage

No tests exist for this assertion

#### Section 2.8.1.5 - Stereotypes with additional stereotypes [stereotypes_with_additional_stereotypes]

a)

A stereotype may declare other stereotypes.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

c)

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

#### Section 2.8.2 - Declaring the stereotypes for a bean [declaring_stereotypes]

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

a)

Test with a bean class.

Coverage

No tests exist for this assertion

b)

Test with a producer method.

Coverage

No tests exist for this assertion

c)

Test with a producer field.

Coverage

No tests exist for this assertion

db)

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

Coverage

No tests exist for this assertion

e)

Multiple stereotypes may be applied to the same bean.

Coverage

No tests exist for this assertion

#### Section 2.8.3 - Built-in stereotypes [builtin_stereotypes]

aa)

The built-in stereotype @jakarta.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.9 - Problems detected automatically by the container [exceptions]

a)

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

No tests exist for this assertion

ba)

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

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

ca)

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

Coverage

No tests exist for this assertion

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 [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

No tests exist for this assertion

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

No tests exist for this assertion

fb)

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

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 3.1.1 - Which Java classes are managed beans? [what_classes_are_beans]

b)

A Java class is not a managed bean if it is an inner class.

Coverage

No tests exist for this assertion

ba)

A Java class that is a static nested class can be a managed bean.

Coverage

No tests exist for this assertion

ca)

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

Coverage

No tests exist for this assertion

cb)

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

Coverage

No tests exist for this assertion

g)

A Java class is not a managed bean if it implements jakarta.enterprise.inject.spi.Extension.

Coverage

No tests exist for this assertion

h)

A Java class is not a managed bean if it is annotated @Vetoed or placed in a package annotated @Vetoed.

Coverage

No tests exist for this assertion

p)

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

Coverage

No tests exist for this assertion

q)

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

Coverage

No tests exist for this assertion

r)

If packages annotated @Vetoed are split across classpath entries, non-portable behavior results. An application can prevent packages being split across jars by sealing the package as defined by the Extension Mechanism Architecture.

#### Section 3.1.2 - Bean types of a managed bean [managed_bean_types]

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

No tests exist for this assertion

b)

The resulting set of bean types for a managed bean consists only of legal bean types, all other types are removed from the set of bean types.

Coverage

No tests exist for this assertion

#### Section 3.1.3 - Declaring a managed bean [declaring_managed_bean]

a)

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

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

bb)

Test a bean with a name.

Coverage

No tests exist for this assertion

bd)

Test a bean with a stereotype.

Coverage

No tests exist for this assertion

be)

Test a bean with a qualifier.

Coverage

No tests exist for this assertion

c)

A managed bean may extend another managed bean.

Coverage

No tests exist for this assertion

#### Section 3.1.4 - Specializing a managed bean [specialize_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

No tests exist for this assertion

ab)

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

Coverage

No tests exist for this assertion

ac)

Test a specialized bean extending a managed bean.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

db)

Test a specializing bean extending nothing.

Coverage

No tests exist for this assertion

dd)

Test a specializing bean implementing an interface and extending nothing.

Coverage

No tests exist for this assertion

#### Section 3.1.5 - Default bean name for a managed bean [managed_bean_name]

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

No tests exist for this assertion

#### Section 3.2 - Producer methods [producer_method]

aa)

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

Coverage

No tests exist for this assertion

b)

A producer method may be static.

Coverage

No tests exist for this assertion

c)

A producer method may be non-static.

Coverage

No tests exist for this assertion

e)

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

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

hb)

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

Coverage

No tests exist for this assertion

iaa)

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

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

ic)

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

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

k)

A bean may declare multiple producer methods.

Coverage

No tests exist for this assertion

#### Section 3.2.1 - Bean types of a producer method [producer_method_types]

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

No tests exist for this assertion

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

No tests exist for this assertion

bb)

Check array return type

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

d)

The resulting set of bean types for a producer method consists only of legal bean types, all other types are removed from the set of bean types.

Coverage

No tests exist for this assertion

#### Section 3.2.2 - Declaring a producer method [declaring_producer_method]

a)

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

Coverage

No tests exist for this assertion

ba)

A producer method may specify a scope.

Coverage

No tests exist for this assertion

bb)

A producer method may specify a name.

Coverage

No tests exist for this assertion

bd)

A producer method may specify stereotypes.

Coverage

No tests exist for this assertion

be)

A producer method may specify qualifiers.

Coverage

No tests exist for this assertion

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

ca)

Test with a producer method annotated @Inject.

Coverage

No tests exist for this assertion

da)

Test with a producer method annotated @Disposes.

Coverage

No tests exist for this assertion

ea)

Test with a producer method annotated @Observes.

Coverage

No tests exist for this assertion

fa)

Test with a producer method annotated @ObservesAsync.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

h)

A producer method may have any number of parameters.

Coverage

No tests exist for this assertion

i)

All producer method parameters are injection points.

Coverage

No tests exist for this assertion

#### Section 3.2.3 - Specializing a producer method [specialize_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

No tests exist for this assertion

ba)

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

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 3.2.4 - Default bean name for a producer method [producer_method_name]

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

No tests exist for this assertion

b)

Test default name is the JavaBeans property name.

Coverage

No tests exist for this assertion

#### Section 3.3 - Producer fields [producer_field]

a)

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

Coverage

No tests exist for this assertion

b)

A producer field may be static.

Coverage

No tests exist for this assertion

c)

A producer field may be non-static.

Coverage

No tests exist for this assertion

d)

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

Coverage

No tests exist for this assertion

e)

If a producer field 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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

gc)

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

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

ha)

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

Coverage

No tests exist for this assertion

hb)

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

Coverage

No tests exist for this assertion

i)

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

No tests exist for this assertion

#### Section 3.3.1 - Bean types of a producer field [producer_field_types]

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

No tests exist for this assertion

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

No tests exist for this assertion

bb)

Check array type

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

d)

The resulting set of bean types for a producer field consists only of legal bean types, all other types are removed from the set of bean types.

Coverage

No tests exist for this assertion

#### Section 3.3.2 - Declaring a producer field [declaring_producer_field]

a)

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

Coverage

No tests exist for this assertion

b)

A producer field may specify a scope.

Coverage

No tests exist for this assertion

c)

A producer field may specify a name.

Coverage

No tests exist for this assertion

e)

A producer field may specify stereotypes.

Coverage

No tests exist for this assertion

f)

A producer field may specify qualifiers.

Coverage

No tests exist for this assertion

g)

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

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 3.3.3 - Default bean name for a producer field [producer_field_name]

a)

The default name for a producer field is the field name

Coverage

No tests exist for this assertion

#### Section 3.4 - Disposer methods [disposer_method]

aa)

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

Coverage

No tests exist for this assertion

b)

A disposer method may be static.

Coverage

No tests exist for this assertion

c)

A disposer method may be non-static.

Coverage

No tests exist for this assertion

e)

A bean may declare multiple disposer methods.

Coverage

No tests exist for this assertion

#### Section 3.4.1 - Disposed parameter of a disposer method [disposer_method_disposed_parameter]

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

No tests exist for this assertion

ba)

When searching for disposer methods for a producer method or producer field the container considers the type and qualifiers of the disposed parameter. If 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

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 3.4.2 - Declaring a disposer method [declaring_disposer_method]

a)

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

Coverage

No tests exist for this assertion

ba)

Qualifiers may be declared by annotating the disposed parameter.

Coverage

No tests exist for this assertion

bb)

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

Coverage

No tests exist for this assertion

ca)

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

Coverage

No tests exist for this assertion

da)

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

Coverage

No tests exist for this assertion

ea)

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

Coverage

No tests exist for this assertion

fa)

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

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 3.4.3 - Disposer method resolution [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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 3.5 - Bean constructors [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

No tests exist for this assertion

#### Section 3.5.1 - Declaring a bean constructor [declaring_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

No tests exist for this assertion

ba)

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

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

da)

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

Coverage

No tests exist for this assertion

ea)

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

Coverage

No tests exist for this assertion

fa)

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

Coverage

No tests exist for this assertion

f)

A bean constructor may have any number of parameters.

Coverage

No tests exist for this assertion

g)

All parameters of a bean constructor are injection points.

Coverage

No tests exist for this assertion

#### Section 3.6 - Injected fields [injected_fields]

An injected field is a non-static, non-final field of a bean class or of any other classes supporting injection.

a)

Test a bean class.

Coverage

No tests exist for this assertion

#### Section 3.6.1 - Declaring an injected field [declaring_injected_field]

aa)

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

Coverage

No tests exist for this assertion

b)

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

Coverage

No tests exist for this assertion

#### Section 3.7 - Initializer methods [initializer_methods]

An initializer method is a default-access, public, protected or private, non-abstract, non-static, non-generic method of a bean class or of any other classes supporting injection.

a)

Test a bean-class.

Coverage

No tests exist for this assertion

f)

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

Coverage

No tests exist for this assertion

g)

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

Coverage

No tests exist for this assertion

h)

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

#### Section 3.7.1 - Declaring an initializer method [declaring_initializer]

a)

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

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

ba)

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

Coverage

No tests exist for this assertion

ca)

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

Coverage

No tests exist for this assertion

da)

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

Coverage

No tests exist for this assertion

ea)

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

Coverage

No tests exist for this assertion

e)

An initializer method may have any number of parameters.

Coverage

No tests exist for this assertion

f)

All initializer method parameters are injection points.

Coverage

No tests exist for this assertion

#### Section 3.8 - The default qualifier at injection points [injection_point_default_qualifier]

a)

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

Coverage

No tests exist for this assertion

#### Section 3.9 - The qualifier @Named at injection points [named_at_injection_point]

a)

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

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 3.10 - @New qualified beans [new]

d)

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

Coverage

No tests exist for this assertion

e)

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

Coverage

No tests exist for this assertion

f)

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

Coverage

No tests exist for this assertion

g)

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

Coverage

No tests exist for this assertion

h)

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

Coverage

No tests exist for this assertion

i)

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

Coverage

No tests exist for this assertion

p)

This second bean has scope @Dependent.

Coverage

No tests exist for this assertion

r)

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

Coverage

No tests exist for this assertion

s)

This second bean has no bean name.

Coverage

No tests exist for this assertion

t)

This second bean has no stereotypes.

Coverage

No tests exist for this assertion

u)

This second bean has no observer methods.

Coverage

No tests exist for this assertion

v)

This second bean has no producer methods.

Coverage

No tests exist for this assertion

w)

This second bean has no producer fields.

Coverage

No tests exist for this assertion

x)

This second bean has no disposer methods.

Coverage

No tests exist for this assertion

xb)

This second bean is not an alternative.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 3.11 - Unproxyable bean types [unproxyable]

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

No tests exist for this assertion

baa)

Test a class which is declared final.

Coverage

No tests exist for this assertion

bba)

Test a class that has non-static, final method with public visibility.

Coverage

No tests exist for this assertion

bbb)

Test a class that has non-static, final method with public visibility declared on a superclass.

Coverage

No tests exist for this assertion

bca)

Test with a class that has static final method with public visibility.

Coverage

No tests exist for this assertion

bda)

Test a class that has final method with private visibility.

Coverage

No tests exist for this assertion

ca)

Test primitive type.

Coverage

No tests exist for this assertion

da)

Test array type.

Coverage

No tests exist for this assertion

A bean type must be proxyable if an injection point resolves to a bean:

ea)

That has an associated decorator.

Coverage

No tests exist for this assertion

eb)

That has a bound interceptor.

Coverage

No tests exist for this assertion

#### Section 4.1 - Inheritance of type-level metadata [type_level_inheritance]

Suppose a class X is extended directly or indirectly by the bean class of a managed 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

No tests exist for this assertion

aaa)

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

Coverage

No tests exist for this assertion

ab)

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

Coverage

No tests exist for this assertion

aba)

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

Coverage

No tests exist for this assertion

ad)

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

Coverage

No tests exist for this assertion

ada)

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

Coverage

No tests exist for this assertion

ag)

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

Coverage

No tests exist for this assertion

aga)

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

Coverage

No tests exist for this assertion

ah)

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

Coverage

No tests exist for this assertion

aha)

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

Coverage

No tests exist for this assertion

aj)

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

Coverage

No tests exist for this assertion

aja)

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

Coverage

No tests exist for this assertion

Suppose a class X is extended directly or indirectly by the bean class of a managed 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

No tests exist for this assertion

baa)

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

Coverage

No tests exist for this assertion

bc)

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

Coverage

No tests exist for this assertion

bca)

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

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

i)

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

j)

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

k)

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

m)

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

#### Section 4.2 - Inheritance of member-level metadata [member_level_inheritance]

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

aa)

Check managed bean X directly extends managed bean Y

Coverage

No tests exist for this assertion

ac)

Check managed bean X indirectly extends managed bean Y

Coverage

No tests exist for this assertion

Suppose a class X is extended directly or indirectly by the bean class of a managed 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

No tests exist for this assertion

bac)

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

Coverage

No tests exist for this assertion

bba)

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

Coverage

No tests exist for this assertion

bbc)

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

Coverage

No tests exist for this assertion

dc)

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

Coverage

No tests exist for this assertion

di)

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

Coverage

No tests exist for this assertion

dm)

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

Coverage

No tests exist for this assertion

do)

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

Coverage

No tests exist for this assertion

Suppose a class X is extended directly or indirectly by the bean class of a managed bean. 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

No tests exist for this assertion

kc)

Check managed bean X indirectly extends managed bean Y

Coverage

No tests exist for this assertion

Suppose a class X is extended directly or indirectly by the bean class of a managed 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

No tests exist for this assertion

db)

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

Coverage

No tests exist for this assertion

dg)

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

Coverage

No tests exist for this assertion

dh)

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

Coverage

No tests exist for this assertion

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)

Check managed bean X directly extends managed bean Y

Coverage

No tests exist for this assertion

ec)

Check managed bean X indirectly extends managed bean Y

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

g)

check observer method

Coverage

No tests exist for this assertion

#### Section 4.3 - Specialization [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

No tests exist for this assertion

cb)

Producer method on specialized bean is not called.

Coverage

No tests exist for this assertion

cc)

Observer method on specialized bean is not called.

Coverage

No tests exist for this assertion

cd)

Producer field on specialized bean is not used.

Coverage

No tests exist for this assertion

#### Section 4.3.1 - Direct and indirect specialization [direct_and_indirect_specialization]

ia)

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

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

j)

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

Coverage

No tests exist for this assertion

k)

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

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

lb)

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

Coverage

No tests exist for this assertion

n)

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

#### Section 5 - Dependency injection and lookup [injection_and_resolution]

b)

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

No tests exist for this assertion

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 [selection]

A bean packaged in a certain module is available for injection, lookup and name resolution to classes packaged in some other module if the bean class of the bean is required to be accessible to the other module by the class accessibility requirements of the module architecture.

aa)

Test with injection.

Coverage

No tests exist for this assertion

ab)

Test with lookup.

Coverage

No tests exist for this assertion

ac)

Test with name resolution.

Coverage

No tests exist for this assertion

d)

An alternative is never available for injection, lookup or name resolution in a module unless the module is a bean archive and the alternative is explicitly selected for the bean archive or the application..

e)

Nor is an alternative available for injection, lookup or name 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 name resolution.

Coverage

No tests exist for this assertion

#### Section 5.1.1 - Declaring selected alternatives [declaring_selected_alternatives]

a)

This specification defines two methods of selecting alternatives. From Contexts and Dependency Injection 1.1 onwards the @Priority annotation allows an alternative to be selected for an entire application. Contexts and Dependency Injection 1.0 allowed only for an alternative to be selected for a bean archive.

#### Section 5.1.1.1 - Declaring selected alternatives for an application [declaring_selected_alternatives_application]

An alternative may be given a priority for the application by placing the @Priority annotation on the bean class of a managed bean.

aa)

Test @Priority on the bean class of a managed bean.

Coverage

No tests exist for this assertion

An alternative may be given a priority for the application by placing the @Priority annotation on the bean class that declares the producer method, field or resource.

ba)

Test @Priority on the bean class of a producer method.

Coverage

No tests exist for this assertion

bb)

Test @Priority on the bean class of a producer field.

Coverage

No tests exist for this assertion

bc)

Test @Priority on the resource.

Coverage

No tests exist for this assertion

#### Section 5.1.1.2 - Declaring selected alternatives for a bean archive [declaring_selected_alternatives_bean_archive]

a)

An alternative may be explicitly declared using the <alternatives> element of the beans.xml file of the bean archive. The <alternative> element contains a list of bean classes and stereotypes.

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

ba)

Test selected managed bean.

Coverage

No tests exist for this assertion

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.

ca)

Test selected producer method.

Coverage

No tests exist for this assertion

cb)

Test selected producer field.

Coverage

No tests exist for this assertion

cc)

Test selected resource.

Coverage

No tests exist for this assertion

d)

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

Coverage

No tests exist for this assertion

e)

For each child <class> element the container verifies that either a class with the specified name exists and is annotated with @Alternative or an @Alternative stereotype, or a class with the specified name exists and declares a field or method annotated with @Produces and, at the same time, annotated with @Alternative or an @Alternative stereotype, or an alternative bean whose bean class has the specified name exists. Otherwise, the container automatically detects the problem and treats it as a deployment problem.

Coverage

No tests exist for this assertion

f)

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

No tests exist for this assertion

g)

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

No tests exist for this assertion

h)

For a custom implementation of the Bean interface defined in Section "bean", 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

No tests exist for this assertion

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

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

Coverage

No tests exist for this assertion

#### Section 5.1.2 - Enabled and disabled beans [enablement]

a)

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 not an alternative, or it is a selected alternative of at least one bean archive or the application. Otherwise, the bean is said to be disabled.

#### Section 5.1.3 - Inconsistent specialization [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

No tests exist for this assertion

#### Section 5.1.4 - Inter-module injection [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

No tests exist for this assertion

b)

Check an interceptor can not be injected

Coverage

No tests exist for this assertion

c)

Check an enabled managed bean can be injected

Coverage

No tests exist for this assertion

e)

Check an enabled producer field can be injected

Coverage

No tests exist for this assertion

f)

Check an enabled producer method can be injected

Coverage

No tests exist for this assertion

g)

Check producer method of a disabled bean is not injectable

Coverage

No tests exist for this assertion

h)

Check producer field of a disabled bean is not injectable

Coverage

No tests exist for this assertion

i)

Check a disabled managed bean is not injectable

Coverage

No tests exist for this assertion

l)

Check a specialized managed bean is not injectable

Coverage

No tests exist for this assertion

m)

Check a specialized producer field is not injectable

n)

Check a specialized producer method is not injectable

Coverage

No tests exist for this assertion

o)

Check a selected alternative being managed bean is injected

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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 [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

No tests exist for this assertion

j)

Test with an array type.

Coverage

No tests exist for this assertion

ka)

Test with a parameterized type.

Coverage

No tests exist for this assertion

kb)

Test with a raw type.

Coverage

No tests exist for this assertion

kc)

Test with a @Named bean.

Coverage

No tests exist for this assertion

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 @jakarta.enterprise.util.NonBinding.

la)

Test with beans with required qualifiers.

Coverage

No tests exist for this assertion

lb)

Test with beans without required qualifiers.

Coverage

No tests exist for this assertion

lc)

Test with matching beans with matching qualifier with same type.

Coverage

No tests exist for this assertion

ld)

Test with matching beans with matching qualifier with same annotation member value for each member which is not annotated @jakarta.enterprise.util.NonBinding.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

nb)

Test getQualifiers() determines qualifiers.

Coverage

No tests exist for this assertion

#### Section 5.2.2 - Unsatisfied and ambiguous dependencies [unsatisfied_and_ambig_dependencies]

When an ambiguous dependency exists, the container attempts to resolve the ambiguity. The container eliminates all eligible beans that are not alternatives selected for the bean archive or selected for the application, except for producer methods and fields of beans that are alternatives.

ca)

If there is exactly one bean remaining, the container will select this bean, and the ambiguous dependency is called resolvable.

Coverage

No tests exist for this assertion

cb)

If all the beans left are alternatives with a priority, then the container will determine the highest priority value, and eliminate all beans, except for producer methods and fields of beans that are alternatives with the highest priority value. If there is exactly one bean remaining, the container will select this bean, and the ambiguous dependency is called resolvable.

Coverage

No tests exist for this assertion

The container must validate all injection points of all enabled beans, all observer methods and all disposer methods 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

No tests exist for this assertion

ab)

Test unsatisfied dependency for observer method.

Coverage

No tests exist for this assertion

ac)

Test unsatisfied dependency for disposer method.

Coverage

No tests exist for this assertion

ae)

Test ambiguous dependency for enabled bean.

Coverage

No tests exist for this assertion

af)

Test ambiguous dependency for observer method.

Coverage

No tests exist for this assertion

ag)

Test ambiguous dependency for disposer method.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 5.2.3 - Legal injection point types [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

No tests exist for this assertion

b)

The required type of an injection point may contain a wildcard type parameter.

Coverage

No tests exist for this assertion

c)

If an injection point type is a type variable, the container automatically detects the problem and treats it as a definition error.

Coverage

No tests exist for this assertion

#### Section 5.2.4 - Assignability of raw and parameterized types [assignable_parameters]

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

No tests exist for this assertion

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

No tests exist for this assertion

bb)

Check the required type parameter and the bean type parameter are actual types with identical raw type for nested type parameters

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

Coverage

No tests exist for this assertion

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

Coverage

No tests exist for this assertion

dc)

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 lower bound of the wildcard

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

g)

A raw bean type is considered assignable to a parameterized required type if the raw types are identical and all type parameters of the required type are either unbounded type variables or java.lang.Object.

Coverage

No tests exist for this assertion

#### Section 5.2.5 - Primitive types and null values [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

No tests exist for this assertion

ab)

Test unboxing.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 5.2.6 - Qualifier annotations with members [qualifier_annotation_members]

a)

Qualifier types may have annotation members.

b)

An annotation member may be excluded from consideration using the @NonBinding annotation.

Coverage

No tests exist for this assertion

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 [multiple_qualifiers]

a)

A bean class may declare multiple qualifiers.

Coverage

No tests exist for this assertion

b)

A producer method may declare multiple qualifiers.

Coverage

No tests exist for this assertion

c)

A producer field may declare multiple qualifiers.

Coverage

No tests exist for this assertion

d)

A bean must declare all of the qualifiers that are specified at the injection point to be considered a candidate for injection.

Coverage

No tests exist for this assertion

#### Section 5.3 - EL name resolution [name_resolution]

d)

An name resolves to a bean if the bean has the given bean name, and the bean is available for injection in the module where the name resolution is requested.

Coverage

No tests exist for this assertion

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

Coverage

No tests exist for this assertion

#### Section 5.3.1 - Ambiguous EL names [ambig_names]

An ambiguous name exists when a name resolves to multiple beans. When an ambiguous name exists, the container attempts to resolve the ambiguity. The container eliminates all eligible beans that are not alternatives selected for the bean archive or selected for the application, except for producer methods and fields of beans that are alternatives.

ca)

If there is exactly one bean remaining, the container will select this bean, and the ambiguous dependency is called resolvable.

Coverage

No tests exist for this assertion

cb)

If all the beans left are alternatives with a priority, then the container will determine the highest priority value, and eliminate all beans, except for producer methods and fields of beans that are alternatives with the highest priority value. If there is exactly one bean remaining, the container will select this bean, and the ambiguous dependency is called resolvable.

Coverage

No tests exist for this assertion

All unresolvable ambiguous names are detected by the container when the application is initialized. Suppose two beans are both available for injection in a certain module, and either

da)

Test two beans have the same bean name and the name is not resolvable.

Coverage

No tests exist for this assertion

db)

Test the bean name of one bean is of the form x.y , where y is a valid bean name, and x is the bean name of the other bean.

Coverage

No tests exist for this assertion

#### Section 5.4 - Client proxies [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

No tests exist for this assertion

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)

Client proxies are serializable

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

e)

Client proxies may be shared between multiple injection points.

#### Section 5.4.1 - Client proxy invocation [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

No tests exist for this assertion

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

No tests exist for this assertion

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 [injection]

b)

The container is required to perform dependency injection whenever it creates a contextual instance of a managed bean.

Coverage

No tests exist for this assertion

d)

The container is required to perform dependency injection whenever it instantiates non-contextual instances of managed beans.

Coverage

No tests exist for this assertion

g)

The container interacts with instances of beans or objects 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 [instantiation]

When the container instantiates a managed 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

No tests exist for this assertion

ba)

Test constructor with no parameters is used for a managed bean

Coverage

No tests exist for this assertion

#### Section 5.5.2 - Injection of fields and initializer methods [fields_initializer_methods]

When the container creates a new instance of a managed bean 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.

ac)

Test managed bean fields injected

Coverage

No tests exist for this assertion

ad)

Test managed bean initializer methods called

Coverage

No tests exist for this assertion

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. Any @PostConstruct callback declared by a class X in the type hierarchy of the bean is called after all initializer methods 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.

bg)

Test managed bean initializer methods called after injected field of X

Coverage

No tests exist for this assertion

bh)

Test managed bean initializer methods called after injected field of superclass of X

Coverage

No tests exist for this assertion

bk)

Test managed bean @PostConstruct called after initializer of X

Coverage

No tests exist for this assertion

bl)

Test managed bean @PostConstruct called after initializer of superclass of X

Coverage

No tests exist for this assertion

#### Section 5.5.3 - Destruction of dependent objects [dependent_objects_destruction]

a)

When the container destroys an instance of a bean, the container destroys all dependent objects, as defined in Section 6.4.2, "Destruction of objects with scope @Dependent", after the @PreDestroy callback completes.

Coverage

No tests exist for this assertion

#### Section 5.5.4 - Invocation of producer or disposer methods [producer_or_disposer_methods_invocation]

a)

When the container calls a producer method, if the method is static, the container must invoke the method.

Coverage

No tests exist for this assertion

b)

When the container calls a disposer method, if the method is static, the container must invoke the method.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

e)

The container passes an injectable reference to each injected method parameter.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 5.5.5 - Access to producer field values [producer_fields_access]

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

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 5.5.6 - Invocation of observer methods [observers_method_invocation]

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

No tests exist for this assertion

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

No tests exist for this assertion

c)

The container must pass the event object to the event parameter and an injectable instance to each injected method parameter.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 5.5.7 - Injection point metadata [injection_point]

aa)

The getBean() method returns the Bean object representing the bean that defines the injection point.

Coverage

No tests exist for this assertion

aaa)

If the injection point does not belong to a bean, getBean() returns a null value.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

ba)

The getType() method returns the required type of the injection point.

Coverage

No tests exist for this assertion

baa)

If the injection point represents a dynamically obtained instance, the getType() method returns the required type (as defined by Instance.select()).

Coverage

No tests exist for this assertion

bc)

The getQualifiers() method returns the required qualifiers of the injection point.

Coverage

No tests exist for this assertion

bca)

If the injection point represents a dynamically obtained instance, the getQualifiers() method returns required qualifiers of the injection point including any additional required qualifers (as defined by Instance.select()).

Coverage

No tests exist for this assertion

ca)

The getMember() method returns the Field object in the case of field injection.

Coverage

No tests exist for this assertion

caa)

If the injection point represents a dynamically obtained instance, the getMember() method returns the Field object representing the field that defines the Instance injection point in the case of field injection.

Coverage

No tests exist for this assertion

cb)

The getMember() method returns the Method object in the case of method parameter injection.

Coverage

No tests exist for this assertion

cba)

If the injection point represents a dynamically obtained instance, the getMember() method returns the Method object representing the method that defines the Instance injection point in the case of method parameter injection.

Coverage

No tests exist for this assertion

cc)

The getMember() method returns the Constructor object in the case of constructor parameter injection.

Coverage

No tests exist for this assertion

cca)

If the injection point represents a dynamically obtained instance, the getMember() method returns the Constructor object representing the constructor that defines the Instance injection point in the case of constructor parameter injection.

Coverage

No tests exist for this assertion

daa)

The getAnnotated() method returns an instance of jakarta.enterprise.inject.spi.AnnotatedField or jakarta.enterprise.inject.spi.AnnotatedParameter, depending upon whether the injection point is an injected field or a constructor/method parameter.

Coverage

No tests exist for this assertion

dab)

If the injection point represents a dynamically obtained instance, then the getAnnotated() method returns an instance of jakarta.enterprise.inject.spi.AnnotatedField or jakarta.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

No tests exist for this assertion

dbb)

If the injection point represents a dynamically obtained instance then isDelegate() returns false.

Coverage

No tests exist for this assertion

dca)

The isTransient() method returns true if the injection point is a transient field, and false otherwise.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

eb)

The built-in implementation must be a passivation capable dependency, as defined in Section 6.6.2, "Passivation capable dependencies".

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

g)

If a disposer method has an injection point of type InjectionPoint and qualifier @Default, the container automatically detects the problem and treats it as a definition error.

Coverage

No tests exist for this assertion

h)

If a 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

No tests exist for this assertion

#### Section 5.5.8 - Bean metadata [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

No tests exist for this assertion

b)

Bean with scope @Dependent, qualifier @Default and type Interceptor can be injected into any interceptor instance.

Coverage

No tests exist for this assertion

c)

Bean with scope @Dependent, qualifier @Default and type Decorator which can be injected into any decorator instance.

Coverage

No tests exist for this assertion

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 @Intercepted and type Bean which can be injected into any interceptor instance.

Coverage

No tests exist for this assertion

e)

Bean with scope @Dependent, qualifier @Decorated and type Bean can be injected into any decorator instance.

Coverage

No tests exist for this assertion

f)

These beans are passivation capable dependencies, as defined in Section 6.6.2, "Passivation capable dependencies".

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

r)

If a Bean instance with qualifier @Intercepted 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

No tests exist for this assertion

s)

If a Bean instance with qualifier @Decorated 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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

p)

If the injection point is a disposer method parameter then no Bean instance can be injected, the container automatically detects the problem and treats it as a definition error.

Coverage

No tests exist for this assertion

#### Section 5.6 - Programmatic lookup [programmatic_lookup]

aa)

An instance of the jakarta.enterprise.inject.Instance interface may be injected.

Coverage

No tests exist for this assertion

ba)

The method jakarta.enterprise.inject.Instance.get() returns a contextual reference.

Coverage

No tests exist for this assertion

ca)

Any combination of qualifiers may be specified at the injection point.

Coverage

No tests exist for this assertion

da)

The @Any qualifier may be used to allow the application to specify qualifiers dynamically.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 5.6.1 - The Instance interface [dynamic_lookup]

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

bb)

Rules specified at "The default qualifier at injection points" are applied before performing typesafe resolution.

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

No tests exist for this assertion

da)

If two instances of the same non repeating qualifier type are passed to select(), an IllegalArgumentException is thrown.

Coverage

No tests exist for this assertion

e)

If an instance of an annotation that is not a qualifier type is passed to select(), an IllegalArgumentException is thrown.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

fba)

If typesafe resolution results in an unsatisfied dependency, throw an UnsatisfiedResolutionException.

Coverage

No tests exist for this assertion

fbb)

If typesafe resolution results in an unresolvable ambiguous dependency, throw an AmbiguousResolutionException.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

ia)

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

No tests exist for this assertion

ib)

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

No tests exist for this assertion

ja)

The stream() 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.1, "Performing typesafe resolution", resolving ambiguities according to Section 5.2.2 "Unsatisfied and ambiguous dependencies".

Coverage

No tests exist for this assertion

jb)

The stream() method must return a Stream, that can stream 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

No tests exist for this assertion

The methods isUnsatisfied(), isAmbiguous() and isResolvable() must:

la)

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 Performing typesafe resolution, resolving ambiguities according to Unsatisfied and ambiguous dependencies.

Coverage

No tests exist for this assertion

l)

The method isUnsatisfied() returns true if there is no bean found, or false otherwise.

Coverage

No tests exist for this assertion

m)

The method isAmbiguous() returns true if there is more than one bean found, or false otherwise.

Coverage

No tests exist for this assertion

ma)

The method isResolvable() returns true if there is exactly one bean found, or false otherwise.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

o)

Test client proxy passed to destroy().

Coverage

No tests exist for this assertion

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 [builtin_instance]

a)

The container must provide a built-in bean that is eligible for injection to any injection point with required type Instance <X> or Provider<>, for any legal bean type X.

b)

The container must provide a built-in bean that has any qualifiers.

d)

The container must provide a built-in bean with scope @Dependent.

Coverage

No tests exist for this assertion

e)

The container must provide a built-in bean with no bean name.

Coverage

No tests exist for this assertion

f)

The container must provide a built-in bean with an implementation provided automatically by the container.

Coverage

No tests exist for this assertion

g)

The built-in implementation must be a passivation capable dependency, as defined in Section 6.6.2, "Passivation capable dependencies".

Coverage

No tests exist for this assertion

#### Section 5.6.3 - Using AnnotationLiteral and TypeLiteral [annotationliteral_typeliteral]

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

Test jakarta.enterprise.util.AnnotationLiteral when using Instance.select() to specify qualifiers.

Coverage

No tests exist for this assertion

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

Test jakarta.enterprise.util.TypeLiteral when specifying a parameterized type with actual type parameters when calling Instance.select().

Coverage

No tests exist for this assertion

#### Section 6.1 - The Contextual interface [contextual]

aa)

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

No tests exist for this assertion

ab)

If an exception occurs while destroying an instance, the exception must be caught by the destroy() method.

Coverage

No tests exist for this assertion

ac)

If the application invokes a contextual instance after it has been destroyed, the behavior is undefined.

a)

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 [creational_context]

ca)

The interface jakarta.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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

h)

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)

Contextual.destroy() should call release() to allow the container to destroy dependent objects of the contextual instance.

#### Section 6.2 - The Context interface [context]

aa)

The jakarta.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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

m)

If the context object is inactive, the get() method must throw a ContextNotActiveException.

Coverage

No tests exist for this assertion

na)

The get() method may not return a null value unless no CreationalContext is given, or Contextual.create() returns a null value.

Coverage

No tests exist for this assertion

nb)

The get() method may not return a null value unless no CreationalContext is given, or Contextual.create() returns a null value.

Coverage

No tests exist for this assertion

o)

The get() method may not create a new instance of the given contextual type unless a CreationalContext is given.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

t)

The destroy() method destroys an existing contextual instance, removing it from the context instance.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

q)

A destroyed instance must not subsequently be returned by the get() method.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 6.3 - Normal scopes and pseudo-scopes [normal_scope]

a)

There may be no more than one mapped instance of a context object per contextual type per thread

b)

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

No tests exist for this assertion

d)

When a context is destroyed, all mapped instances belonging to that context are destroyed by passing them to the Contextual.destroy() method.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

ea)

All normal scopes must be explicitly declared @NormalScope, to indicate to the container that a client proxy is required.

fa)

All pseudo-scopes must be explicitly declared @Scope, to indicate to the container that no client proxy is required.

g)

All scopes defined by this specification, except for the @Dependent pseudo-scope, are normal scopes

#### Section 6.4 - Dependent pseudo-scope [dependent_context]

a)

When a bean is declared to have @Dependent scope, no injected instance of the bean is ever shared between multiple injection points.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

db)

Test with a producer field.

Coverage

No tests exist for this assertion

dc)

Test with a disposer method.

Coverage

No tests exist for this assertion

dd)

Test with an observer method.

Coverage

No tests exist for this assertion

dg)

When a bean is 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

No tests exist for this assertion

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

No tests exist for this assertion

f)

Every invocation of the get() operation of the Context object for the @Dependent scope with no CreationalContext returns a null value.

Coverage

No tests exist for this assertion

g)

The @Dependent scope is always active.

Coverage

No tests exist for this assertion

#### Section 6.4.1 - Dependent objects [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

No tests exist for this assertion

ab)

Test with a @Dependent-scoped decorator.

Coverage

No tests exist for this assertion

An instance of a bean with scope @Dependent injected into a field, bean constructor or initializer method is a dependent object of the bean into which it was injected.

ga)

Test with @Dependent-scoped bean injected into field.

Coverage

No tests exist for this assertion

gb)

Test with @Dependent-scoped bean injected into bean constructor.

Coverage

No tests exist for this assertion

gc)

Test with @Dependent-scoped bean injected into initializer method.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 6.4.2 - Destruction of objects with scope @Dependent [dependent_destruction]

The container must ensure that all dependent objects of a non-contextual instance of a bean are destroyed when the instance is destroyed by the container.

aaaa)

Test with a managed bean.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

ccd)

Check observer method.

Coverage

No tests exist for this assertion

The container must ensure that all @Dependent scoped contextual instances injected into method or constructor parameters that are annotated with @TransientReference are destroyed when the invocation completes.

fa)

Test producer method parameter.

Coverage

No tests exist for this assertion

fb)

Test initializer method parameter.

Coverage

No tests exist for this assertion

fc)

Test bean constructor parameter.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

dde)

Check producer field.

Coverage

No tests exist for this assertion

ddf)

Check disposer method.

Coverage

No tests exist for this assertion

ddg)

Check observer method.

Coverage

No tests exist for this assertion

e)

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.5.1 - The active context object for a scope [active_context]

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

No tests exist for this assertion

b)

If more than one active context object exists for the given scope type, the container must throw an IllegalStateException.

Coverage

No tests exist for this assertion

#### Section 6.5.2 - Activating Built In Contexts [activating_builtin_contexts]

a)

Certain built in contexts support the ability to be activated and deactivated. This allows developers to control built-in contexts in ways that they could also manage custom built contexts. When activating and deactivating built in contexts, it is important to realize that they can only be activated if not already active within a given thread.

#### Section 6.5.2.1 - 6.5.2.1. Activating a Request Context [activating_request_context]

a)

Request contexts can be managed either programmatically or via interceptor.

Coverage

No tests exist for this assertion

b)

To programmatically manage request contexts, the container provides a built in bean that is @Dependent scoped and of type RequestContextController that allows you to activate and deactivate a request context on the current thread. The object should be considered stateful, invoking the same instance on different threads may not work properly, non-portable behavior may occur.

Coverage

No tests exist for this assertion

c)

When the activate() method is called, if the request context is not already active on the current thread then it will be activated and the method returns true. Otherwise, the method returns false.

Coverage

No tests exist for this assertion

When the deactivate() method is called,

da)

if this controller started the request context then the request context is stopped

Coverage

No tests exist for this assertion

db)

The method does nothing if this controller did not activate the context and the context is active.

Coverage

No tests exist for this assertion

dc)

This method throws a ContextNotActiveException if there is no request context active.

Coverage

No tests exist for this assertion

e)

If within the same thread the activate() and deactivate() methods are invoked repeatedly, the instances between the activations are not the same instances, each request context should be assumed to be new.

Coverage

No tests exist for this assertion

f)

To automatically start a request context via interceptor binding, the container provides an interceptor @ActivateRequestContext which will activate a request context if not already active prior to the method’s invocation, and deactivate it upon method completion, with the same rules as in RequestContextController.

Coverage

No tests exist for this assertion

g)

When the requestContext is managed via interceptor binding, the interceptor is automatically registered with a priority of PLATFORM_BEFORE + 100

Coverage

No tests exist for this assertion

#### Section 6.5.3 - Contextual instance of a bean [contextual_instance]

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

No tests exist for this assertion

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

No tests exist for this assertion

c)

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

No tests exist for this assertion

#### Section 6.5.4 - Contextual reference for a bean [contextual_reference]

aa)

Contextual references must be obtained with a given CreationalContext, allowing any instance of scope @Dependent that is created to be later destroyed.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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.

da)

Test an injected dependent object.

Coverage

No tests exist for this assertion

db)

Test a non-injected dependent object.

Coverage

No tests exist for this assertion

#### Section 6.5.5 - Contextual reference validity [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

No tests exist for this assertion

b)

Any reference to a bean with a normal scope is invalid after CDI container shutdown. Maintaining such reference and attempting to use it after container shutdown results in an IllegalStateException.

Coverage

No tests exist for this assertion

c)

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.6 - Injectable references [injectable_reference]

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

No tests exist for this assertion

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.7 - Injectable reference validity [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)

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 [passivating_scope]

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

Test that passivation occurs.

Coverage

No tests exist for this assertion

#### Section 6.6.1 - Passivation capable beans [passivation_capable]

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

No tests exist for this assertion

bb)

Tests with a serializable interceptor.

Coverage

No tests exist for this assertion

bc)

Tests with a serializable decorator.

Coverage

No tests exist for this assertion

c)

A producer method is passivation capable if and only if it never returns a value which is not passivation capable at runtime.

d)

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.

ca)

Test that a producer method with a serializable return type is passivation capable.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

da)

Test that a producer field with a serializable type is passivation capable.

Coverage

No tests exist for this assertion

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)

The getId() method of the PassivationCapable implementation must return a value that uniquely identifies the instance of Bean or Contextual.

h)

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 injection points [passivation_capable_injection_points]

a)

An injection point of a bean is passivation capable if the injection point is a transient field.

Coverage

No tests exist for this assertion

b)

An injection point of a bean is passivation capable if the injection point is a non-transient field which resolves to a bean that is a passivation capable dependency.

Coverage

No tests exist for this assertion

c)

An injection point of a bean is passivation capable if the injection point is a bean constructor parameter which is annotated with @TransientReference.

Coverage

No tests exist for this assertion

d)

An injection point of a bean is passivation capable if the injection point is a bean constructor parameter which resolves to a bean that is a passivation capable dependency.

Coverage

No tests exist for this assertion

e)

An injection point of a bean is passivation capable if the injection point is a method parameter which is annotated with @TransientReference.

Coverage

No tests exist for this assertion

f)

An injection point of a bean is passivation capable if the injection point is a method parameter which resolves to a bean that is a passivation capable dependency.

Coverage

No tests exist for this assertion

#### Section 6.6.3 - Passivation capable dependencies [passivation_capable_dependency]

b)

The container must guarantee that all beans with normal scope are passivation capable dependencies.

Coverage

No tests exist for this assertion

c)

The container must guarantee that all passivation capable beans with scope @Dependent are passivation capable dependencies.

Coverage

No tests exist for this assertion

The container must guarantee that the built-in beans of type Instance, Event, InjectionPoint and BeanManager are passivation capable dependencies.

ea)

Test built-in Instance.

Coverage

No tests exist for this assertion

eb)

Test built-in Event.

Coverage

No tests exist for this assertion

ec)

Test built-in InjectionPoint.

Coverage

No tests exist for this assertion

ed)

Test built-in BeanManager.

Coverage

No tests exist for this assertion

fa)

A custom implementation of Bean is a passivation capable dependency if it implements PassivationCapable.

Coverage

No tests exist for this assertion

#### Section 6.6.4 - Passivating scopes [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

No tests exist for this assertion

b)

Test that an implementation of Contextual passed to the context object for the scope is passivation capable.

b)

Passivating scopes must be explicitly declared @NormalScope(passivating=true).

#### Section 6.6.5 - Validation of passivation capable beans and dependencies [passivation_validation]

If a managed bean which declares a passivating scope, or a built-in bean is not passivation capable then the container automatically detects the problem and treats it as a deployment problem.

a)

Test managed bean.

Coverage

No tests exist for this assertion

If a managed bean which declares a passivating scope, or a built-in bean has has an injection point that is not passivation capable, then the container automatically detects the problem and treats it as a deployment problem.

aa)

Test non-transient injected field.

Coverage

No tests exist for this assertion

ab)

Test transient injected field.

Coverage

No tests exist for this assertion

ac)

Test bean constructor parameter which is not annotated with @TransientReference.

Coverage

No tests exist for this assertion

ad)

Test bean constructor parameter which is annotated with @TransientReference.

Coverage

No tests exist for this assertion

ae)

Test initializer method parameter which is not annotated with @TransientReference.

Coverage

No tests exist for this assertion

af)

Test initializer method parameter which is annotated with @TransientReference.

Coverage

No tests exist for this assertion

ag)

If a managed bean which declares a passivating scope, or a built-in bean has a non-transient injected field, bean constructor parameter or initializer method parameter that resolves to a bean that is not a dependent scoped bean and that is not a passivation capable dependency then the container automatically detects the problem and treats it as a deployment problem.

If a managed bean which declares a passivating scope, or a built-in 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.

aac)

Test interceptor with a non-transient injected field that does not resolve to a passivation capable dependency.

Coverage

No tests exist for this assertion

aaf)

Test decorator with a non-transient injected field that does not resolve to a passivation capable dependency.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

fbb)

Test for a runtime exception with a producer field.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

gb)

Test calling InjectionPoint.isTransient().

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

hc)

Test a bean with interceptor which is not a passivation capable dependency.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 6.7 - Context management for built-in scopes [builtin_contexts]

a)

A portable extension may define a custom context object for any or all of the built-in scopes. For example, a remoting framework might provide a request context object for the built-in request scope.

Coverage

No tests exist for this assertion

b)

The context associated with a built-in normal scope propagates across local, synchronous Java method calls. The context does not propagate across remote method invocations or to asynchronous processes.

Coverage

No tests exist for this assertion

Portable extensions are encouraged to synchronously fire (where X is the scope type associated with the context.):

ea)

an event with qualifier @Initialized(X.class) when a custom context is initialized, i.e. ready for use,

eb)

an event with qualifier @BeforeDestroyed(X.class) when a custom context is about to be destroyed, i.e. before the actual destruction,

ec)

an event with qualifier @Destroyed(X.class) when a custom context is destroyed, i.e. after the actual destruction,

#### Section 6.7.1 - Request context lifecycle [request_context]

a)

An event with qualifier @Initialized(RequestScoped.class) is synchronously fired when the request context is initialized.

Coverage

No tests exist for this assertion

b)

An event with qualifier @BeforeDestroyed(RequestScoped.class) is synchronously fired when the request context is about to be destroyed, i.e. before the actual destruction.

Coverage

No tests exist for this assertion

c)

An event with qualifier @Destroyed(RequestScoped.class) is synchronously fired when the request context is destroyed, i.e. after the actual destruction.

Coverage

No tests exist for this assertion

The request context is active:

da)

during notification of an asynchronous observer method

Coverage

No tests exist for this assertion

db)

during @PostConstruct callback of any bean.

Coverage

No tests exist for this assertion

The request context is destroyed:

ea)

after the invocation of an asynchronous observer method completes

Coverage

No tests exist for this assertion

eb)

after the @PostConstruct callback completes, if it did not already exist when the @PostConstruct callback occurred

Coverage

No tests exist for this assertion

#### Section 6.7.3 - Application context lifecycle [application_context]

a)

An event with qualifier @Initialized(ApplicationScoped.class) is synchronously fired when the application context is initialized.

Coverage

No tests exist for this assertion

b)

An event with qualifier @BeforeDestroyed(ApplicationScoped.class) is synchronously fired when the application context is about to be destroyed, i.e. before the actual destruction.

Coverage

No tests exist for this assertion

c)

An event with qualifier @Destroyed(ApplicationScoped.class) is synchronously fired when the application context is destroyed, i.e. after the actual destruction.

Coverage

No tests exist for this assertion

#### Section 6.7.5 - The Conversation interface [conversation]

The container provides a built-in bean with bean type Conversation, scope @RequestScoped, and qualifier @Default, named jakarta.enterprise.context.conversation.

iaa)

Test the bean type is correct.

Coverage

No tests exist for this assertion

ib)

Test the scope is correct.

Coverage

No tests exist for this assertion

id)

Test the qualifier is correct.

Coverage

No tests exist for this assertion

ie)

Test the bean name is correct.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

k)

end() marks the current long-running conversation transient.

Coverage

No tests exist for this assertion

l)

getId() returns the identifier of the current long-running conversation, or a null value if the current conversation is transient.

Coverage

No tests exist for this assertion

m)

getTimeout() returns the timeout, in milliseconds, of the current conversation.

Coverage

No tests exist for this assertion

n)

setTimeout() sets the timeout of the current conversation.

Coverage

No tests exist for this assertion

o)

isTransient() returns true if the conversation is marked transient, or false if it is marked long-running.

Coverage

No tests exist for this assertion

p)

If any method of Conversation is called when the conversation scope is not active, a ContextNotActiveException is thrown.

Coverage

No tests exist for this assertion

q)

If end() is called, and the current conversation is marked transient, an IllegalStateException is thrown.

Coverage

No tests exist for this assertion

r)

If begin() is called, and the current conversation is already marked long-running, an IllegalStateException is thrown.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 7.2 - Container invocations and interception [biz_method]

aa)

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", the invocation is treated as a business method invocation.

Coverage

No tests exist for this assertion

ab)

When the application invokes a method of a bean via a non-contextual reference to the bean, if the instance was created by the container, the invocation is treated as a business method invocation.

Coverage

No tests exist for this assertion

ac)

When the application invokes a method of a bean via a non-contextual reference to the bean, if the instance was enhanced with the InterceptionFactory interface as defined in `Apply interceptor programmatically`, the invocation is treated as a business method invocation.

Coverage

No tests exist for this assertion

ad)

Invocations of initializer methods by the container are not business method invocations.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

ib)

Verify producer methods are decorated

Coverage

No tests exist for this assertion

ic)

Verify disposer methods are intercepted

Coverage

No tests exist for this assertion

id)

Verify disposer methods are decorated

Coverage

No tests exist for this assertion

ie)

Verify observer methods are intercepted

Coverage

No tests exist for this assertion

if)

Verify observer methods are decorated

Coverage

No tests exist for this assertion

j)

Invocation of lifecycle callbacks by the container are not business method invocations, but are intercepted by interceptors for lifecycle callbacks.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

kb)

Verify decorators callbacks are not decorated

Coverage

No tests exist for this assertion

kc)

Verify interceptor callbacks are not intercepted

Coverage

No tests exist for this assertion

kd)

Verify interceptor callbacks are not decorated

Coverage

No tests exist for this assertion

m)

Invocations of methods declared by java.lang.Object are not business method invocations.

Coverage

No tests exist for this assertion

If, and only if, the invocation is a business method invocation it passes through method interceptors and decorators.

a)

Verify that a managed bean's business methods are intercepted

Coverage

No tests exist for this assertion

b)

Verify that a managed bean's business methods are decorated

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 7.3.1 - Lifecycle of managed beans [managed_bean_lifecycle]

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

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 7.3.2 - Lifecycle of producer methods [producer_method_lifecycle]

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

r)

Finally, the container destroys dependent objects, as defined in Section 5.5.3, "Destruction of dependent objects".

Coverage

No tests exist for this assertion

#### Section 7.3.3 - Lifecycle of producer fields [producer_field_lifecycle]

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 8 - Decorators [decorators]

a)

Decorators may be associated with any managed bean that is not itself an interceptor or decorator, with any EJB session bean or with any built-in bean other than the built-in bean with type BeanManager and qualifier @Default.

b)

Decorators are not applied to the return value of a producer method or the current value of a producer field.

Coverage

No tests exist for this assertion

c)

A decorator instance is a dependent object of the object it decorates.

Coverage

No tests exist for this assertion

#### Section 8.1 - Decorator beans [decorator_bean]

a)

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

No tests exist for this assertion

c)

The decorator bean class and its superclasses are not decorated types of the decorator.

Coverage

No tests exist for this assertion

d)

The decorator class may be abstract.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

f)

If a decorator declares any scope other than @Dependent, the container automatically detects the problem and treats it as a definition error.

Coverage

No tests exist for this assertion

#### Section 8.1.1 - Declaring a decorator [decorator_annotation]

a)

A decorator is declared by annotating the bean class with the @jakarta.decorator.Decorator stereotype.

Coverage

No tests exist for this assertion

#### Section 8.1.2 - Decorator delegate injection points [delegate_attribute]

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 @jakarta.decorator.Delegate.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

cb)

Test a decorator without a delegate injection point.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

cd)

Check an initializer method parameter is ok

Coverage

No tests exist for this assertion

ce)

Check a bean constructor method parameter is ok

Coverage

No tests exist for this assertion

cf)

Check that a producer method parameter is not ok

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

g)

If a decorator invokes the delegate object at any other time, the invoked method throws an IllegalStateException.

Coverage

No tests exist for this assertion

#### Section 8.1.3 - Decorated types of a decorator [decorated_types]

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

No tests exist for this assertion

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

No tests exist for this assertion

b)

A decorator is not required to implement the delegate type.

Coverage

No tests exist for this assertion

c)

A decorator may be an abstract Java class, and is not required to implement every method of every decorated type.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 8.2 - Decorator enablement and ordering [enabled_decorators]

a)

This specification defines two methods of enabling and ordering decorators. From Contexts and Dependency Injection 1.1 onwards the @Priority annotation allows a decorator to be enabled and ordered for an entire application. Contexts and Dependency Injection 1.0 allowed only for a decorator to be enabled and ordered for a bean archive.

b)

Decorators are called after interceptors.

Coverage

No tests exist for this assertion

c)

Decorators enabled using @Priority are called before decorators enabled using beans.xml.

Coverage

No tests exist for this assertion

d)

If a decorator is enabled for the application and for the bean archive, then the enablement from the bean archive is ignored by the container. The decorator will only be executed once based on the @Priority annotation’s invocation chain.

Coverage

No tests exist for this assertion

#### Section 8.2.1 - Decorator enablement and ordering for an application [enabled_decorators_priority]

a)

A decorator may be enabled for the entire application by applying the @Priority annotation, along with a priority value, on the decorator class.

Coverage

No tests exist for this assertion

b)

Decorators with the smaller priority values are called first.

Coverage

No tests exist for this assertion

c)

The order of more than one decorator with the same priority is undefined.

d)

The priority value ranges defined in the Java Interceptors specification section 5.5 should be used when defining decorator priorities.

#### Section 8.2.2 - Decorator enablement and ordering for a bean archive [enabled_decorators_bean_archive]

a)

A decorator may be explicitly enabled by listing its bean class under the <decorators> element of the beans.xml file of the bean archive.

Coverage

No tests exist for this assertion

b)

The order of the decorator declarations determines the decorator ordering. Decorators which occur earlier in the list are called first.

Coverage

No tests exist for this assertion

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.

ca)

Test with a nonexistent class name.

Coverage

No tests exist for this assertion

cb)

Test with a non-decorator class.

Coverage

No tests exist for this assertion

d)

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

No tests exist for this assertion

#### Section 8.3 - Decorator resolution [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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 8.3.1 - Assignability of raw and parameterized types for delegate injection points [delegate_assignable_parameters]

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

No tests exist for this assertion

ab)

Check all type parameters are Object

Coverage

No tests exist for this assertion

ac)

Check mix

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

d)

Check nested identical type parameters

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 8.4 - Decorator invocation [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

No tests exist for this assertion

aca)

Test injected Event

Coverage

No tests exist for this assertion

acb)

Test injected Instance

Coverage

No tests exist for this assertion

ach)

Test injected Conversation

Coverage

No tests exist for this assertion

b)

If no such decorator exists, the container invokes the business method of the intercepted instance.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

e)

If no such decorator exists, the container invokes the business method of the intercepted instance.

Coverage

No tests exist for this assertion

f)

Otherwise, the container calls the method of the decorator.

Coverage

No tests exist for this assertion

#### Section 9.1.1 - Interceptor bindings for stereotypes [stereotype_interceptor_bindings]

a)

Interceptor bindings may be applied to a stereotype by annotating the stereotype annotation.

Coverage

No tests exist for this assertion

b)

An interceptor binding declared by a stereotype is inherited by any bean that declares that stereotype.

Coverage

No tests exist for this assertion

c)

If a stereotype declares interceptor bindings, it must be defined as @Target(TYPE).

#### Section 9.3 - Binding an interceptor to a bean [binding_interceptor_to_bean]

a)

Interceptor bindings may be used to associate interceptors with any managed bean that is not a decorator.

Coverage

No tests exist for this assertion

b)

The set of interceptor bindings for a method are those declared at class level includes those declared on stereotypes. An interceptor binding declared on a bean class replaces an interceptor binding of the same type declared by a stereotype that is applied to the bean class.

Coverage

No tests exist for this assertion

c)

Since CDI 2.0 it is possible to apply interceptors programmatically to the return value of a producer method, with the InterceptionFactory interface as defined in `Apply interceptor programmatically`.

Coverage

No tests exist for this assertion

d)

If a managed bean has a class-level or method-level interceptor binding, the managed bean must be a proxyable bean type, as defined in Section "unproxyable".

Coverage

No tests exist for this assertion

#### Section 9.4 - Interceptor enablement and ordering [enabled_interceptors]

a)

This specification extends the Java Interceptors specification and defines support for enabling interceptors only for a bean archive, as defined by Contexts and Dependency Injection 1.0, and the ability to override the interceptor order using the portable extension SPI, defined in Section "atd".

b)

An interceptor may be explicitly enabled for a bean archive by listing its class under the <interceptors> element of the beans.xml file of the bean archive.

Coverage

No tests exist for this assertion

c)

The order of the interceptor declarations determines the interceptor ordering. Interceptors which occur earlier in the list are called first.

Coverage

No tests exist for this assertion

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.

da)

Test with a non-existant class.

Coverage

No tests exist for this assertion

db)

Test with a class that isn't an interceptor.

Coverage

No tests exist for this assertion

e)

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

No tests exist for this assertion

f)

Interceptors enabled using @Priority are called before interceptors enabled using beans.xml.

Coverage

No tests exist for this assertion

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

Interceptors declared using interceptor bindings are called after interceptors declared using the Interceptors annotation (or using the corresponding element of a deployment descriptor).

Coverage

No tests exist for this assertion

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

Interceptors declared using interceptor bindings are called before any around-invoke, around-timeout, or lifecycle event callback methods declared on the target class or any superclass of the target class.

Coverage

No tests exist for this assertion

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

By default, a bean archive has no enabled interceptors.

Coverage

No tests exist for this assertion

j)

If an interceptor declares any scope other than @Dependent, the container automatically detects the problem and treats it as a definition error.

Coverage

No tests exist for this assertion

k)

If an interceptor is enabled for the application and for the bean archive, then the enablement from the bean archive is ignored by the container. The interceptor will only be executed once based on the @Priority annotation’s invocation chain.

Coverage

No tests exist for this assertion

#### Section 9.5 - Interceptor resolution [interceptor_resolution]

a)

This specification extends the Java Interceptors specification and defines the effect of applying @Nonbinding to an interceptor binding member, and how the interceptor bindings of a custom implementation of the Interceptor interface are determined.

b)

If any interceptor binding has a member annotated @jakarta.enterprise.util.Nonbinding, the member is ignored when performing interceptor resolution, and the method does not need to have the same annotation member value.

Coverage

No tests exist for this assertion

For a custom implementation of the Interceptor interface defined in Section "interceptor", 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 or business method.

ca)

Check for @PostConstruct

Coverage

No tests exist for this assertion

cb)

Check for @PreDestroy

Coverage

No tests exist for this assertion

cc)

Check for @PostActivate

Coverage

No tests exist for this assertion

cd)

Check for @PrePassivate

Coverage

No tests exist for this assertion

ce)

Check for @AroundInvoke

Coverage

No tests exist for this assertion

cf)

Check for @AroundTimeout

Coverage

No tests exist for this assertion

#### Section 10.1 - Event types and qualifier types [event_types_and_qualifier_types]

aa)

An event object is an instance of a concrete Java class with no unresolvable type variables.

Coverage

No tests exist for this assertion

c)

The event types of the event include all superclasses and interfaces of the runtime class of the event object.

Coverage

No tests exist for this assertion

cb)

An event type may not contain an unresolvable type variable.

d)

An event qualifier type is a Java annotation defined as @Target({FIELD, PARAMETER}) or @Target({METHOD, FIELD, PARAMETER, TYPE})

Coverage

No tests exist for this assertion

g)

All event qualifier types must specify the @jakarta.inject.Qualifier meta-annotation

Coverage

No tests exist for this assertion

i)

Every event has the qualifier @jakarta.enterprise.inject.Any, even if it does not explicitly declare this qualifier.

Coverage

No tests exist for this assertion

j)

Any Java type may be an observed event type.

Coverage

No tests exist for this assertion

#### Section 10.2 - Firing events [firing_events]

a)

Beans fire events via an instance of the jakarta.enterprise.event.Event interface, which may be injected.

Coverage

No tests exist for this assertion

c)

Any combination of qualifiers may be specified at the injection point.

Coverage

No tests exist for this assertion

d)

Or, the @Any qualifier may be used, allowing the application to specify qualifiers dynamically.

Coverage

No tests exist for this assertion

#### Section 10.2.1 - Firing events synchronously [firing_events_synchronously]

b)

The method fire() accepts an event object.

Coverage

No tests exist for this assertion

e)

Event fired with the fire() method is fired synchronously. All the resolved synchronous observers are called in the thread in which fire() was called.

Coverage

No tests exist for this assertion

f)

A synchronous observer notification blocks the calling thread until it completes.

Coverage

No tests exist for this assertion

#### Section 10.2.2 - Firing events asynchronously [firing_events_asynchronously]

a)

Event fired with the fireAsync() method is fired asynchronously. All the resolved asynchronous observers are called in one or more different threads.

Coverage

No tests exist for this assertion

#### Section 10.2.3 - The Event interface [event]

ca)

The Event interface provides a method for firing events with a specified combination of type and qualifiers.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

eab)

If the specified type contains a type variable, an IllegalArgumentException is thrown.

Coverage

No tests exist for this assertion

eba)

If two instances of the same non repeating qualifier type are passed to select(), an IllegalArgumentException is thrown.

Coverage

No tests exist for this assertion

ec)

If an instance of an annotation that is not a qualifier type is passed to select(), an IllegalArgumentException is thrown.

Coverage

No tests exist for this assertion

eda)

The method fire() and fireAsync() fire an event with the specified qualifiers and notifies observers, as defined by Section 10.5, "Observer notification".

Coverage

No tests exist for this assertion

edb)

If the container is unable to resolve the parameterized type of the event object, it uses the specified type to infer the parameterized type of the event types.

Coverage

No tests exist for this assertion

ee)

The method fireAsync() may be called with a NotificationOptions object to configure the observer methods notification, e.g. to specify an Executor object to be used for asynchronous delivery.

Coverage

No tests exist for this assertion

The following elements are container specific:

efa)

the default Executor used by the container when fireAsync() is called without specifying an Executor,

efb)

the CompletionStage returned by fireAsync methods,

efc)

all dependent stages of this initial CompletionStage.

f)

If the runtime type of the event object contains an unresolvable type variable, an IllegalArgumentException is thrown.

Coverage

No tests exist for this assertion

g)

If the runtime type of the event object is assignable to the type of a container lifecycle event, IllegalArgumentException is thrown.

Coverage

No tests exist for this assertion

#### Section 10.2.4 - The built-in Event [builtin_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

No tests exist for this assertion

b)

The container must provide a built-in bean with every event qualifier type in its set of qualifier types.

Coverage

No tests exist for this assertion

d)

The container must provide a built-in bean with scope @Dependent.

Coverage

No tests exist for this assertion

e)

The container must provide a built-in bean with no bean name.

Coverage

No tests exist for this assertion

f)

The container must provide a built-in bean with an implementation provided automatically by the container.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

g)

The built-in implementation must be a passivation capable dependency, as defined in Section 6.6.2, "Passivation capable dependencies".

Coverage

No tests exist for this assertion

#### Section 10.3 - Observer resolution [observer_resolution]

a)

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)

Observer resolution usually occurs at runtime.

An event is delivered to an observer method if the observer method belongs to an enabled bean, an event type 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 @jakarta.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, an event type is assignable to the observed event type and has a subset of the event qualifiers.

Coverage

No tests exist for this assertion

d)

Check an event is not delivered if the observer method belongs to an disabled bean.

Coverage

No tests exist for this assertion

e)

Check an event is delivered if the observer method if the event is fired synchronously and the observer is defined with @Observes

Coverage

No tests exist for this assertion

f)

Check an event is delivered if the observer method if the event is fired asynchronously and the observer is defined with @ObservesAsync .

Coverage

No tests exist for this assertion

j)

If the runtime type of the event object contains an unresolvable type variable, the container must throw an IllegalArgumentException.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 10.3.1 - Assignability of type variables, raw and parameterized types [observers_assignability]

a)

An event type is considered assignable to a type variable if the event type is assignable to the upper bound, if any.

Coverage

No tests exist for this assertion

b)

A parameterized event type is considered assignable to a raw observed event type if the raw types are identical.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

d)

Check the event type parameter and the observed event type parameter are actual types with identical raw type for nested type parameters.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 10.3.2 - Event qualifier types with members [event_qualifier_types_with_members]

a)

The qualifier type for an Event qualifier may have annotation members.

Coverage

No tests exist for this assertion

b)

The container uses equals() to compare event qualifier type member values.

#### Section 10.3.3 - Multiple event qualifiers [multiple_event_qualifiers]

a)

An event parameter may have multiple qualifiers.

Coverage

No tests exist for this assertion

b)

An observer method will only be notified if all the observed event qualifiers are specified when the event is fired.

Coverage

No tests exist for this assertion

#### Section 10.4 - Observer methods [observer_methods]

aa)

An observer method allows the application to receive and respond to event notifications.

ab)

An observer method is a non-abstract method of a managed bean class (or of an extension, as defined in Section 11.5, "Container lifecycle events").

Coverage

No tests exist for this assertion

c)

An observer method may be either static or non-static.

Coverage

No tests exist for this assertion

e)

There may be arbitrarily many observer methods with the same event parameter type and qualifiers.

Coverage

No tests exist for this assertion

f)

A bean (or extension) may declare multiple observer methods.

Coverage

No tests exist for this assertion

#### Section 10.4.1 - Event parameter of an observer method [observer_method_event_parameter]

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

No tests exist for this assertion

b)

If the event parameter does not explicitly declare any qualifier, the observer method observes events with no qualifier.

Coverage

No tests exist for this assertion

The event parameter type may contain a type variable or wildcard.

ca)

Test with a type variable.

Coverage

No tests exist for this assertion

cb)

Test with a wildcard.

Coverage

No tests exist for this assertion

The event parameter may be an array type whose component type contains a type variable or a wildcard.

da)

Test with a type variable.

Coverage

No tests exist for this assertion

db)

Test with a wildcard.

Coverage

No tests exist for this assertion

e)

Modifications made to the event parameter in an observer method are propagated to following observers.

Coverage

No tests exist for this assertion

#### Section 10.4.2 - Declaring an observer method [observes]

a)

An observer method may be declared by annotating a parameter @jakarta.enterprise.event.Observes or @jakarta.enterprise.event.ObservesAsync 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

No tests exist for this assertion

ab)

If @Observes is used the observer method is a synchronous observer method.

Coverage

No tests exist for this assertion

ac)

If @ObservesAsync is used the observer method is an asynchronous observer method.

Coverage

No tests exist for this assertion

b)

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

Coverage

No tests exist for this assertion

ba)

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

Coverage

No tests exist for this assertion

c)

Observed event qualifiers may be declared by annotating the event parameter.

Coverage

No tests exist for this assertion

d)

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

Coverage

No tests exist for this assertion

e)

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

Coverage

No tests exist for this assertion

f)

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

Coverage

No tests exist for this assertion

h)

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

Coverage

No tests exist for this assertion

i)

In addition to the event parameter, observer methods may declare additional parameters, which may declare qualifiers. These additional parameters are injection points.

Coverage

No tests exist for this assertion

#### Section 10.4.3 - The EventMetadata interface [event_metadata]

The interface jakarta.enterprise.inject.spi.EventMetadata provides access to metadata about an observed event.

a)

getQualifiers() returns the set of qualifiers with which the event was fired.

Coverage

No tests exist for this assertion

b)

getInjectionPoint() returns the InjectionPoint from which this event payload was fired, or null if it was fired from BeanManager.fireEvent().

Coverage

No tests exist for this assertion

c)

getType() returns the type representing runtime class of the event object with type variables resolved.

Coverage

No tests exist for this assertion

e)

The container must provide a bean with scope @Dependent, bean type EventMetadata and qualifier @Default, allowing observer methods to obtain information about the events they observe.

Coverage

No tests exist for this assertion

f)

If an injection point of type EventMetadata and qualifier @Default which is not a parameter of an observer method exists, the container automatically detects the problem and treats it as a definition error.

Coverage

No tests exist for this assertion

#### Section 10.4.4 - Conditional observer methods [conditional_observer_methods]

a)

A conditional observer method may be declared by specifying receive=IF_EXISTS.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

c)

The enumeration jakarta.enterprise.event.Reception identifies the possible values of receive.

Coverage

No tests exist for this assertion

#### Section 10.4.5 - Transactional observer methods [transactional_observer_methods]

a)

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

No tests exist for this assertion

aa)

If the transaction is in progress, but jakarta.transaction.Synchronization callback cannot be registered due to the transaction being already marked for rollback or in state where jakarta.transaction.Synchronization callbacks cannot be registered, the before completion, after completion and after failure observer methods are notified at the same time as other observers, but after success observer methods get skipped.

Coverage

No tests exist for this assertion

b)

A before completion observer method is called during the before completion phase of the transaction

Coverage

No tests exist for this assertion

c)

An after completion observer method is called during the after completion phase of the transaction

Coverage

No tests exist for this assertion

d)

An after success observer method is called during the after completion phase of the transaction, only when the transaction completes successfully

Coverage

No tests exist for this assertion

e)

An after failure observer method is called during the after completion phase of the transaction, only when the transaction fails

Coverage

No tests exist for this assertion

f)

The enumeration jakarta.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

No tests exist for this assertion

#### Section 10.5 - Observer notification [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 and honor the priority of observer methods as defined in Section 10.6.2, “Observer ordering”.

Coverage

No tests exist for this assertion

ba)

The container calls observer methods as defined in Section 5.5.6, "Invocation of observer methods".

b)

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

No tests exist for this assertion

bca)

If 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

No tests exist for this assertion

bda)

Any observer method called before completion of a transaction may call setRollbackOnly() to force a transaction rollback.

Coverage

No tests exist for this assertion

bdb)

An observer method may not directly initiate, commit or rollback JTA transactions.

Observers may throw exceptions:

ca)

If an observer method is a transactional observer method, any exception is caught and logged by the container.

cb)

If the observer method is asynchronous, the exception aborts processing of the observer but not of the event.

Coverage

No tests exist for this assertion

cd)

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

No tests exist for this assertion

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() which accepts jakarta.enterprise.inject.spi.EventContext to invoke the method.

fa)

Check getTransactionPhase() is called.

Coverage

No tests exist for this assertion

fb)

Check notify() is called.

Coverage

No tests exist for this assertion

#### Section 10.5.1 - Handling multiple exceptions thrown during an asynchronous event [async_exception]

a)

If an event is asynchronous, and an exception is thrown by any of its notified observers, the CompletionStage returned by fireAsync will complete exceptionally with java.util.concurrent.CompletionException exception.

Coverage

No tests exist for this assertion

b)

java.util.concurrent.CompletionException contains all exceptions thrown by observers as suppressed exceptions. They can be accessed as an array of throwable with the getSuppressed method.

Coverage

No tests exist for this assertion

#### Section 10.5.2 - Observer ordering [observer_ordering]

Before the actual observer notification, the container determines an order in which the observer methods for a certain event are invoked. The priority of an observer method may be declared using the @Priority annotation

a)

If no @Priority annotation is specified, the default priority APPLICATION + 500 is assumed

Coverage

No tests exist for this assertion

b)

Observers with smaller priority values are called first

Coverage

No tests exist for this assertion

c)

The order of more than one observer with the same priority is undefined and the observer methods are notified therefore in a non predictable order.

#### Section 10.5.3 - Observer method invocation context [observer_method_invocation_context]

If the observer method is asynchronous, it is called:

aa)

in a new lifecycle contexts.

Coverage

No tests exist for this assertion

ab)

in a new transaction context.

Coverage

No tests exist for this assertion

a)

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

b)

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

c)

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

#### Section 11 - Portable extensions [spi]

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 [bean]

The BeanAttributes interface exposes the basic attributes of a bean.

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

No tests exist for this assertion

bc)

isAlternative() must return true if the bean is an alternative, and false otherwise.

Coverage

No tests exist for this assertion

The interface jakarta.enterprise.inject.spi.Bean defines everything the container needs to manage instances of a certain bean.

bb)

getBeanClass() returns the bean class of the managed bean or of the bean that declares the producer method or field.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

bd)

isNullable() is deprecated in CDI 1.1 and should be ignored by the container.

aa)

Implementations of Bean must also implement the inherited operations defined by the Contextual interface defined in Section 6.1, "The Contextual interface".

Coverage

No tests exist for this assertion

f)

An instance of Bean exists for every enabled bean.

Coverage

No tests exist for this assertion

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 [decorator]

a)

The Bean object for a decorator must implement the interface jakarta.enterprise.inject.spi.Decorator.

Coverage

No tests exist for this assertion

b)

getDecoratedTypes() returns the decorated types of the decorator.

Coverage

No tests exist for this assertion

c)

getDelegateType() and getDelegateQualifiers() return the delegate type and qualifiers of the decorator.

Coverage

No tests exist for this assertion

d)

An instance of Decorator exists for every enabled decorator.

Coverage

No tests exist for this assertion

#### Section 11.1.2 - The Interceptor interface [interceptor]

a)

The Bean object for an interceptor must implement jakarta.enterprise.inject.spi.Interceptor.

Coverage

No tests exist for this assertion

b)

getInterceptorBindings() returns the interceptor bindings of the interceptor.

Coverage

No tests exist for this assertion

c)

intercepts() returns true if the interceptor intercepts the specified kind of lifecycle callback or method invocation, and false otherwise.

Coverage

No tests exist for this assertion

d)

intercept() invokes the specified kind of lifecycle callback or method invocation interception upon the given instance of the interceptor.

Coverage

No tests exist for this assertion

e)

An InterceptionType identifies the kind of lifecycle callback or business method.

Coverage

No tests exist for this assertion

f)

An instance of Interceptor exists for every enabled interceptor.

Coverage

No tests exist for this assertion

#### Section 11.1.3 - The ObserverMethod interface [observer_method]

a)

The interface jakarta.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

No tests exist for this assertion

c)

getObservedType() and getObservedQualifiers() return the observed event type and qualifiers.

Coverage

No tests exist for this assertion

d)

getReception() returns IF_EXISTS for a conditional observer and ALWAYS otherwise.

Coverage

No tests exist for this assertion

e)

getTransactionPhase() returns the appropriate transaction phase for a transactional observer method or IN_PROGRESS otherwise.

Coverage

No tests exist for this assertion

ea)

getPriority() returns the priority that will be used by the container to determine the notification order.

Coverage

No tests exist for this assertion

f)

notify() calls the observer method, as defined in Section 5.5.6 "Invocation of observer methods".

Coverage

No tests exist for this assertion

g)

isAsync() returns true if the method is an asynchronous observer method otherwise returns false

Coverage

No tests exist for this assertion

ga)

An instance of ObserverMethod exists for every observer method of every enabled bean.

Coverage

No tests exist for this assertion

#### Section 11.2 - The Producer and InjectionTarget interfaces [injectiontarget]

a)

The interface jakarta.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

No tests exist for this assertion

bb)

Test initializer methods called

Coverage

No tests exist for this assertion

bc)

Test constructor injected

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

db)

Test bean constructor parameters.

Coverage

No tests exist for this assertion

dc)

Test initializer method parameters.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

eba)

Test with producer field.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

g)

For a Producer that represents a producer method, getInjectionPoints() returns the set of InjectionPoint objects representing all parameters of the producer method.

Coverage

No tests exist for this assertion

h)

The subinterface jakarta.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 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

No tests exist for this assertion

j)

postConstruct() calls the @PostConstruct callback, if it exists.

Coverage

No tests exist for this assertion

k)

preDestroy() calls the @PreDestroy callback, if it exists.

Coverage

No tests exist for this assertion

l)

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 [beanmanager]

The container provides a built-in bean with bean type BeanManager, scope @Dependent and qualifier @Default.

aa)

Test the bean type.

Coverage

No tests exist for this assertion

ab)

Test the scope.

Coverage

No tests exist for this assertion

ac)

Test the qualifier.

Coverage

No tests exist for this assertion

Exception is thrown if the following operations are called before the AfterBeanDiscovery event is fired:

ad)

Test getBeans(String)

Coverage

No tests exist for this assertion

ae)

Test getBeans(Type, Annotation...)

Coverage

No tests exist for this assertion

af)

Test getPassivationCapableBean(String)

Coverage

No tests exist for this assertion

ag)

Test resolve(Set)

Coverage

No tests exist for this assertion

ah)

Test resolveDecorators(Set, Annotation...)

Coverage

No tests exist for this assertion

ai)

Test resolveInterceptors(InterceptionType, Annotation...)

Coverage

No tests exist for this assertion

aj)

Test resolveObserverMethods(Object, Annotation...)

Coverage

No tests exist for this assertion

ak)

Test validate(InjectionPoint)

Coverage

No tests exist for this assertion

Exception is thrown if the following operations are called before the {@Link AfterDeploymentValidation} event is fired:

al)

Test createInstance()

Coverage

No tests exist for this assertion

am)

Test getReference(Bean, Type, CreationalContext)

Coverage

No tests exist for this assertion

an)

Test getInjectableReference(InjectionPoint, CreationalContext)

Coverage

No tests exist for this assertion

b)

The built-in implementation must be a passivation capable dependency, as defined in Section 6.6.2, "Passivation capable dependencies".

Coverage

No tests exist for this assertion

c)

Any bean may obtain an instance of BeanManager by injecting it.

Coverage

No tests exist for this assertion

e)

Any operation of BeanManager may be called at any time during the execution of the application.

#### Section 11.3.1 - Obtaining a reference to the CDI container [provider]

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

No tests exist for this assertion

ab)

Test CDI.getBeanManager() is called after the application initialization is completed.

Coverage

No tests exist for this assertion

ac)

Test lookup of bean instances after the application initialization is completed.

Coverage

No tests exist for this assertion

b)

CDI implements jakarta.enterprise.inject.Instance and therefore might be used to perform programmatic lookup as defined in "The Instance interface". If no qualifier is passed to CDI.select() method, the @Default qualifier is assumed.

Coverage

No tests exist for this assertion

c)

When CDI.current() is called, getCDI() method is called on jakarta.enterprise.inject.spi.CDIProvider.

Coverage

No tests exist for this assertion

The CDIProvider to use may be set by the application or container using the setCDIProvider() method. If the setCDIProvider() has not been called, the service provider with highest priority of the service jakarta.enterprise.inject.spi.CDIProvider declared in META-INF/services is used. The order of more than one CDIProvider with the same priority is undefined.. If no provider is available an IllegalStateException is thrown.

da)

Test using CDIProvider set by the application.

Coverage

No tests exist for this assertion

#### Section 11.3.2 - Obtaining a contextual reference for a bean [bm_obtain_contextual_reference]

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

No tests exist for this assertion

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

No tests exist for this assertion

c)

If the given type is not a bean type of the given bean, an IllegalArgumentException is thrown.

Coverage

No tests exist for this assertion

#### Section 11.3.3 - Obtaining an injectable reference [bm_obtain_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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

bb)

If typesafe resolution results in an unsatisfied dependency, the container must throw an UnsatisfiedResolutionException.

Coverage

No tests exist for this assertion

bc)

If typesafe resolution results in an unresolvable ambiguous dependency, the container must throw an AmbiguousResolutionException.

Coverage

No tests exist for this assertion

c)

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 non-contextual instance [bm_obtain_unmanaged_instance]

A helper class, Unmanaged provides a set of methods optimized for working with unmanaged instances.

a)

Test creating an injector for the given class, using the current bean manager.

Coverage

No tests exist for this assertion

b)

Test creating an injector for the given class.

Coverage

No tests exist for this assertion

UnmanagedInstance methods throws IllegalStateException in following cases:

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

produce() is called on an already produced instance.

Coverage

No tests exist for this assertion

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

produce() is called on an instance that has already been disposed

Coverage

No tests exist for this assertion

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

inject() is called before produce() is called

Coverage

No tests exist for this assertion

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

inject() is called on an instance that has already been disposed

Coverage

No tests exist for this assertion

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

postConstruct() is called before produce() is called

Coverage

No tests exist for this assertion

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

postConstruct() is called on an instance that has already been disposed

Coverage

No tests exist for this assertion

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

preDestroy() is called before produce() is called

Coverage

No tests exist for this assertion

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

preDestroy() is called on an instance that has already been disposed

Coverage

No tests exist for this assertion

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

dispose() is called before produce() is called

Coverage

No tests exist for this assertion

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

dispose() is called on an instance that has already been disposed

Coverage

No tests exist for this assertion

#### Section 11.3.5 - Obtaining a CreationalContext [bm_obtain_creationalcontext]

a)

An instance of CreationalContext for a certain instance of Contextual may be obtained by calling BeanManager.createCreationalContext().

Coverage

No tests exist for this assertion

b)

An instance of CreationalContext for a non-contextual object may be obtained by passing a null value to createCreationalContext().

Coverage

No tests exist for this assertion

#### Section 11.3.6 - Obtaining a Bean by type [bm_obtain_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 or the class 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

No tests exist for this assertion

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

Test alternatives are not filtered.

Coverage

No tests exist for this assertion

b)

The first parameter is a required bean type. The remaining parameters are required qualifiers.

Coverage

No tests exist for this assertion

c)

If no qualifiers are passed to getBeans(), the default qualifier @Default is assumed.

Coverage

No tests exist for this assertion

da)

If the given type represents a type variable, an IllegalArgumentException is thrown.

Coverage

No tests exist for this assertion

e)

If two instances of the same non repeating qualifier type are given, an IllegalArgumentException is thrown.

Coverage

No tests exist for this assertion

f)

If an instance of an annotation that is not a qualifier type is given, an IllegalArgumentException is thrown.

Coverage

No tests exist for this assertion

#### Section 11.3.7 - Obtaining a Bean by name [bm_obtain_bean_by_name]

aa)

The method BeanManager.getBeans() which accepts a string returns the set of beans which have the given bean name and are available for injection in the module or library containing the class into which the BeanManager was injected or the class from whose JNDI environment namespace the BeanManager was obtained, according to the rules of name resolution defined in Section 5.3, "Name resolution".

Coverage

No tests exist for this assertion

b)

The parameter is a bean name.

Coverage

No tests exist for this assertion

#### Section 11.3.8 - Obtaining a passivation capable bean by identifier [bm_obtain_passivation_capable_bean]

a)

The method BeanManager.getPassivationCapableBean() returns the PassivationCapable bean with the given identifier (see Section 6.6.1, "Passivation capable beans").

Coverage

No tests exist for this assertion

#### Section 11.3.9 - Resolving an ambiguous dependency [bm_resolve_ambiguous_dep]

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

No tests exist for this assertion

b)

If the ambiguous dependency resolution rules fail, the container must throw an AmbiguousResolutionException.

Coverage

No tests exist for this assertion

The method BeanManager.resolve() must return null, if:

c)

null is passed to resolve(),

Coverage

No tests exist for this assertion

d)

no beans are passed to resolve(),

Coverage

No tests exist for this assertion

#### Section 11.3.10 - Validating an injection point [bm_validate_ip]

a)

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

No tests exist for this assertion

#### Section 11.3.11 - Firing an event [bm_fire_event]

a)

The method BeanManager.fireEvent() fires an event and notifies observers, according to Section 10.5, "Observer notification".

Coverage

No tests exist for this assertion

b)

The first argument is the event object. The remaining parameters are event qualifiers.

Coverage

No tests exist for this assertion

c)

If the runtime type of the event object contains a type variable, an IllegalArgumentException is thrown.

Coverage

No tests exist for this assertion

d)

If two instances of the same non repeating qualifier type are given, an IllegalArgumentException is thrown.

Coverage

No tests exist for this assertion

e)

If an instance of an annotation that is not a qualifier type is given, an IllegalArgumentException is thrown.

Coverage

No tests exist for this assertion

f)

If the runtime type of the event object is assignable to the type of a container lifecycle event, IllegalArgumentException is thrown.

Coverage

No tests exist for this assertion

#### Section 11.3.12 - Observer method resolution [bm_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.4, "Observer resolution".

Coverage

No tests exist for this assertion

b)

The first parameter of resolveObserverMethods() is the event object. The remaining parameters are event qualifiers.

Coverage

No tests exist for this assertion

c)

If the runtime type of the event object contains a type variable, an IllegalArgumentException is thrown.

Coverage

No tests exist for this assertion

d)

If two instances of the same non repeating qualifier type are given, an IllegalArgumentException is thrown.

Coverage

No tests exist for this assertion

e)

If an instance of an annotation that is not a qualifier type is given, an IllegalArgumentException is thrown.

Coverage

No tests exist for this assertion

#### Section 11.3.13 - Decorator resolution [bm_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 class from whose JNDI environment namespace the BeanManager was obtained, as defined in Section 8.3, "Decorator resolution".

Coverage

No tests exist for this assertion

b)

The first argument is the set of bean types of the decorated bean. The annotations are qualifiers declared by the decorated bean.

Coverage

No tests exist for this assertion

c)

If two instances of the same non repeating qualifier type are given, an IllegalArgumentException is thrown.

Coverage

No tests exist for this assertion

d)

If an instance of an annotation that is not a qualifier type is given, an IllegalArgumentException is thrown.

Coverage

No tests exist for this assertion

e)

If the set of bean types is empty, an IllegalArgumentException is thrown.

Coverage

No tests exist for this assertion

#### Section 11.3.14 - Interceptor resolution [bm_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 class from whose JNDI environment namespace the BeanManager was obtained, as defined in Section 9.5, "Interceptor resolution".

Coverage

No tests exist for this assertion

b)

If two instances of the same non repeating interceptor binding type are given, an IllegalArgumentException is thrown.

Coverage

No tests exist for this assertion

c)

If no interceptor binding type instance is given, an IllegalArgumentException is thrown.

Coverage

No tests exist for this assertion

d)

If an instance of an annotation that is not an interceptor binding type is given, an IllegalArgumentException is thrown.

Coverage

No tests exist for this assertion

#### Section 11.3.15 - Determining if an annotation is a qualifier type, scope type, stereotype or interceptor binding type [bm_determining_annotation]

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

No tests exist for this assertion

ab)

Test scope type.

Coverage

No tests exist for this assertion

ac)

Test stereotype.

Coverage

No tests exist for this assertion

ad)

Test interceptor binding type.

Coverage

No tests exist for this assertion

ae)

Test meta-annotations for stereotype.

Coverage

No tests exist for this assertion

af)

Test meta-annotations for interceptor binding type.

Coverage

No tests exist for this assertion

ag)

Test obtaining a ScopeType.

Coverage

No tests exist for this assertion

#### Section 11.3.16 - Determining the hash code and equivalence of qualifiers and interceptor bindings [bm_determining_hash]

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

No tests exist for this assertion

b)

Test equivalence of interceptor bindings using BeanManager.areInterceptorBindingsEquivalent().

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

d)

Determine the hash code of an interceptor binding using BeanManager.getInterceptorBindingHashCode().

Coverage

No tests exist for this assertion

#### Section 11.3.17 - Obtaining the active Context for a scope [bm_obtain_active_context]

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

No tests exist for this assertion

#### Section 11.3.18 - Obtaining the ELResolver [bm_obtain_elresolver]

a)

The method BeanManager.getELResolver() returns the jakarta.el.ELResolver specified in Section 12.4, "Integration with Unified EL".

Coverage

No tests exist for this assertion

#### Section 11.3.19 - Obtaining an AnnotatedType for a class [bm_obtain_annotatedtype]

a)

The method BeanManager.createAnnotatedType() returns an AnnotatedType that may be used to read the annotations of a given Java class or interface.

Coverage

No tests exist for this assertion

#### Section 11.3.20 - Obtaining an InjectionTarget for a class [bm_obtain_injectiontarget]

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

No tests exist for this assertion

ab)

Check IllegalArgumentException is thrown.

Coverage

No tests exist for this assertion

b)

configure() method returns an AnnotatedTypeConfigurator as defined in AnnotatedTypeConfigurator SPI to configure the AnnotatedType used to create the InjectionTargetFactory. Subsequent invocations of the configure() method within one InjectionTargetFactory instance will always return the same AnnotatedTypeConfigurator instance.

Coverage

No tests exist for this assertion

c)

Once createInjectionTarget() method has been invoked, any invocations of configure() throws an IllegalStateException.

Coverage

No tests exist for this assertion

#### Section 11.3.21 - Obtaining a Producer for a field or method [bm_obtain_producer]

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

No tests exist for this assertion

b)

Test that the method BeanManager.createProducer() returns a container provided implementation of Producer for a given AnnotatedField.

Coverage

No tests exist for this assertion

c)

Test that the method BeanManager.createProducer() throws an IllegalArgumentException if there is a definition error associated with the producer method.

Coverage

No tests exist for this assertion

d)

Test that the method BeanManager.createProducer() throws an IllegalArgumentException if there is a definition error associated with the producer field.

Coverage

No tests exist for this assertion

#### Section 11.3.22 - Obtaining an InjectionPoint [bm_obtain_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

No tests exist for this assertion

b)

Test that the method BeanManager.createInjectionPoint() returns a container provided implementation of InjectionPoint for a given AnnotatedParameter.

Coverage

No tests exist for this assertion

c)

Test that the method BeanManager.createInjectionPoint() throws an IllegalArgumentException if there is a definition error associated with the injection point.

Coverage

No tests exist for this assertion

#### Section 11.3.23 - Obtaining a BeanAttributes [bm_obtain_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

No tests exist for this assertion

b)

Test that the method BeanManager.createBeanAttributes() returns a container provided implementation of BeanAttributes by reading the annotations of a given AnnotatedMember.

Coverage

No tests exist for this assertion

c)

Test that the method BeanManager.createBeanAttributes() throws an IllegalArgumentException if there is a definition error associated with the declared bean attributes.

Coverage

No tests exist for this assertion

#### Section 11.3.24 - Obtaining a Bean [bm_obtain_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

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 11.3.25 - Obtaining the instance of an Extension [bm_obtain_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

No tests exist for this assertion

b)

Test that the method BeanManager.getExtension() throws an IllegalArgumentException if the container has no instance of the given class.

Coverage

No tests exist for this assertion

#### Section 11.3.26 - Obtain an InterceptionFactory [bm_obtain_interception_factory]

a)

The method BeanManager.getInterceptionFactory() returns an InterceptionFactory for the provided type as defined in `Apply interceptor programmatically`.

Coverage

No tests exist for this assertion

#### Section 11.3.27 - Obtain an Instance [bm_obtain_instance]

a)

The method BeanManager.createInstance() returns an Instance<Object> to request bean instances programmatically as described in "The Instance interface".

Coverage

No tests exist for this assertion

b)

If no qualifier is passed to Instance.select() method, the @Default qualifier is assumed.

Coverage

No tests exist for this assertion

#### Section 11.4 - Alternative metadata sources [alternative_metadata_sources]

a)

The interfaces AnnotatedType, AnnotatedField, AnnotatedMethod, AnnotatedConstructor and AnnotatedParameter in the package jakarta.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 jakarta.enterprise.inject.spi.AnnotatedType exposes the Class object and members.

aaa)

Test that getConstructors() returns all default-access, public, protected or private constructors declared for the type.

Coverage

No tests exist for this assertion

aab)

Test that getMethods() returns all default-access, public, protected or private methods declared on the type and those declared on any supertypes.

Coverage

No tests exist for this assertion

aac)

The container should call AnnotatedMethod.getJavaMember().getDeclaringClass() to determine the type in the type hierarchy that declared the method.

Coverage

No tests exist for this assertion

aad)

Test that getFields() returns all default-access, public, protected or private fields declared on the type and those declared on any supertypes.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

The interface jakarta.enterprise.inject.spi.Annotated exposes the overriding annotations and type declarations.

c)

getBaseType() returns the type of the program element.

Coverage

No tests exist for this assertion

d)

getTypeClosure() returns all types to which the base type should be considered assignable.

Coverage

No tests exist for this assertion

e)

getAnnotation() returns the program element annotation of the given annotation type, or a null value.

Coverage

No tests exist for this assertion

f)

getAnnotations() returns all annotations of the program element.

Coverage

No tests exist for this assertion

g)

isAnnotationPresent() returns true if the program element has an annotation of the given annotation type, or false otherwise.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

ha)

Check that getBaseType() is used to determine the type of a field injection point. The base type should be different from the original type specified in the class definition

Coverage

No tests exist for this assertion

hb)

Check that getBaseType() is used to determine the type of an initializer method injection point. The base type should be different from the original type specified in the class definition

Coverage

No tests exist for this assertion

hc)

Check that getBaseType() is used to determine the type of a constructor injection point. The base type should be different from the original 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 original 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 original 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 original 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 original 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 original 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 original 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 original 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 original 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 original type specified in the class definition.

Coverage

No tests exist for this assertion

m)

Check that getAnnotations() is used to determine the bean qualifiers. The annotations should be different from the original type specified in the class definition.

Coverage

No tests exist for this assertion

n)

Check that getAnnotations() is used to determine the bean stereotypes. The annotations should be different from the original type specified in the class definition.

Coverage

No tests exist for this assertion

p)

Check that getAnnotations() is used to determine the bean interceptors. The annotations should be different from the original type specified in the class definition.

Coverage

No tests exist for this assertion

q)

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

No tests exist for this assertion

s)

Check that a qualifier added to a constructor 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

No tests exist for this assertion

u)

Check that an extra qualifier is applied to a field.

Coverage

No tests exist for this assertion

v)

Check that @Produces added creates a producer field.

Coverage

No tests exist for this assertion

w)

Check that a previously non-inject-annotated method is injected.

Coverage

No tests exist for this assertion

x)

Check that an extra qualifier is applied to an injectable method

Coverage

No tests exist for this assertion

y)

Check that @Produces added creates a producer method

Coverage

No tests exist for this assertion

z)

Check that an extra qualifier is applied to a producer method.

Coverage

No tests exist for this assertion

aa)

Check that a qualifer added to a producer method parameter is applied.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

af)

Check that an extra qualifier is applied to an observes method parameter.

Coverage

No tests exist for this assertion

ag)

Check that a qualifer added to a observes method injectable parameter is applied.

Coverage

No tests exist for this assertion

#### Section 11.4.1 - AnnotatedTypeConfigurator SPI [annotated_type_configurator]

This SPI is composed of the following interfaces:

aa)

`jakarta.enterprise.inject.spi.builder.AnnotatedTypeConfigurator` to configure an AnnotatedType

ab)

`jakarta.enterprise.inject.spi.builder.AnnotatedFieldConfigurator` to configure an AnnotatedField

ac)

`jakarta.enterprise.inject.spi.builder.AnnotatedConstructorConfigurator` to configure an AnnotatedConstructor

ad)

`jakarta.enterprise.inject.spi.builder.AnnotatedMethodConfigurator` to configure an AnnotatedMethod

ae)

`jakarta.enterprise.inject.spi.builder.AnnotatedParameterConfigurator` to configure an AnnotatedParameter

AnnotatedTypeConfigurator is the entry point for this SPI.

bc)

Test getAnnotated() returns the original AnnotatedType with which this configurator was initialized.

Coverage

No tests exist for this assertion

bd)

Test add() adds an annotation to the configured element.

Coverage

No tests exist for this assertion

be)

Test remove() method removes annotations that match the specified predicate from the configured element.

Coverage

No tests exist for this assertion

bf)

Test removeAll() removes all annotations from the configured element.

Coverage

No tests exist for this assertion

bg)

Test methods() returns a set of AnnotatedMethodConfigurator to configure annotations on methods.

Coverage

No tests exist for this assertion

bh)

Test filterMethods() returns a `Stream < AnnotatedMethodsConfigurator >` filtered by applying the provided Predicate on methods().

Coverage

No tests exist for this assertion

bi)

Test fields() returns a set of AnnotatedFieldConfigurator to configure annotations on fields.

Coverage

No tests exist for this assertion

bj)

Test filterFields() returns a `Stream < AnnotatedFieldConfigurator >` filtered by applying the provided Predicate on fields().

Coverage

No tests exist for this assertion

bk)

Test constructors() returns a set of AnnotatedConstructorConfigurator to configure annotations on constructors.

Coverage

No tests exist for this assertion

bl)

Test filterConstructors() returns a Stream `<AnnotatedConstructorConfigurator >` filtered by applying the provided Predicate on Constructors().

Coverage

No tests exist for this assertion

#### Section 11.4.1.1 - AnnotatedMethodConfigurator [annotated_method_configurator]

AnnotatedMethodConfigurator

a)

Test getAnnotated() returns the original `AnnotatedMethod` with which this configurator was initialized.

Coverage

No tests exist for this assertion

b)

Test add() adds an annotation to the configured element.

Coverage

No tests exist for this assertion

c)

Test remove() method removes annotations that match the specified predicate from the configured element.

Coverage

No tests exist for this assertion

d)

Test removeAll() removes all annotations from the configured element.

Coverage

No tests exist for this assertion

e)

Test params() returns a list of AnnotatedParameterConfigurator to configure annotations on parameters.

Coverage

No tests exist for this assertion

f)

Test filterParams(Predicate `< AnnotatedParameter <T >>` predicate) returns a `Stream <AnnotatedParameterConfigurator>` filtered by applying the provided Predicate on params().

Coverage

No tests exist for this assertion

#### Section 11.4.1.2 - AnnotatedConstructorConfigurator [annotated_constructor_configurator]

AnnotatedConstructorConfigurator

a)

Test getAnnotated() returns the original `AnnotatedConstructor` with which this configurator was initialized.

Coverage

No tests exist for this assertion

b)

Test add() adds an annotation to the configured element.

Coverage

No tests exist for this assertion

c)

Test remove() method removes annotations that match the specified predicate from the configured element.

Coverage

No tests exist for this assertion

d)

Test removeAll() removes all annotations from the configured element.

Coverage

No tests exist for this assertion

e)

Test params() returns a list of AnnotatedParameterConfigurator to configure annotations on parameters.

Coverage

No tests exist for this assertion

f)

Test filterParams(Predicate `< AnnotatedParameter <T >>` predicate) returns a `Stream <AnnotatedParameterConfigurator>` filtered by applying the provided Predicate on params().

Coverage

No tests exist for this assertion

#### Section 11.4.1.3 - AnnotatedParameterConfigurator [annotated_parameter_configurator]

AnnotatedParameterConfigurator

a)

Test getAnnotated() returns the original `AnnotatedParameter` with which this configurator was initialized.

Coverage

No tests exist for this assertion

b)

Test add() adds an annotation to the configured element.

Coverage

No tests exist for this assertion

c)

Test remove() method removes annotations that match the specified predicate from the configured element.

Coverage

No tests exist for this assertion

d)

Test removeAll() removes all annotations from the configured element.

Coverage

No tests exist for this assertion

#### Section 11.4.1.4 - AnnotatedFieldConfigurator [annotated_field_configurator]

AnnotatedFieldConfigurator

a)

Test getAnnotated() returns the original `AnnotatedField` with which this configurator was initialized.

Coverage

No tests exist for this assertion

b)

Test add() adds an annotation to the configured element.

Coverage

No tests exist for this assertion

c)

Test remove() method removes annotations that match the specified predicate from the configured element.

Coverage

No tests exist for this assertion

d)

Test removeAll() removes all annotations from the configured element.

Coverage

No tests exist for this assertion

#### Section 11.5 - Container lifecycle events [init_events]

a)

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 jakarta.enterprise.inject.spi.Extension declared in META-INF/services.

Coverage

No tests exist for this assertion

bb)

Service providers may have observer methods, which may observer any event, including any container lifecycle event, and obtain an injected BeanManager reference.

Coverage

No tests exist for this assertion

bc)

An extension may use BeanManager.fireEvent() to deliver events to observer methods defined on extensions.

Coverage

No tests exist for this assertion

bd)

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

No tests exist for this assertion

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

No tests exist for this assertion

da)

If an extension declares a static observer method whose event parameter type is a container lifecycle event, or is java.lang.Object and the event parameter has either no qualifiers or a single qualifier @Any, non-portable behavior results.

e)

The notification order for observer methods within extensions follows the same ordering rule as defined in Observer ordering for non-extension observers. The priority of an observer method may be declared using the @Priority annotation.

Coverage

No tests exist for this assertion

f)

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

No tests exist for this assertion

#### Section 11.5.1 - BeforeBeanDiscovery event [before_bean_discovery]

a)

The container must fire an event before it begins the bean discovery process. The event object must be of type jakarta.enterprise.inject.spi.BeforeBeanDiscovery.

Coverage

No tests exist for this assertion

addQualifier() declares an annotation type as a qualifier type.

ab)

Test Class method parameter.

Coverage

No tests exist for this assertion

aba)

Test AnnotatedType method parameter.

Coverage

No tests exist for this assertion

ac)

addScope() declares an annotation type as a scope type.

Coverage

No tests exist for this assertion

ad)

addStereotype() declares an annotation type as a stereotype, and specifies its meta-annotations.

Coverage

No tests exist for this assertion

addInterceptorBinding() declares an annotation type as an interceptor binding type, and specifies its meta-annotations.

ae)

Test Class method parameter.

Coverage

No tests exist for this assertion

aea)

Test AnnotatedType method parameter.

Coverage

No tests exist for this assertion

addAnnotatedType() adds a given AnnotatedType to the set of types which will be scanned during bean discovery, with an optional identifier.

af)

Test the addAnnotatedType() method.

Coverage

No tests exist for this assertion

afa)

Test that more than one AnnotatedType may use the same base type.

Coverage

No tests exist for this assertion

afb)

Test adding AnnotatedType if any other AnnotatedType with the same identifier already exists in the set of types.

Coverage

No tests exist for this assertion

b)

Test AnnotatedTypeConfigurator<?> addAnnotatedType(String id) returns a new AnnotatedTypeConfigurator as defined in AnnotatedTypeConfigurator interface to easily configure the AnnotatedType which will be added at the end of the observer invocation. The returned AnnotatedTypeConfigurator is initialized with type and annotations of the provided class.

Coverage

No tests exist for this assertion

c)

configureQualifier() returns a new AnnotatedTypeConfigurator as defined in AnnotatedTypeConfigurator SPI to configure a new AnnotatedType and declares it as a qualifier type.

Coverage

No tests exist for this assertion

d)

configureInterceptorBinding() returns a new AnnotatedTypeConfigurator as defined in AnnotatedTypeConfigurator SPI to configure a new AnnotatedType and declares it as an interceptor binding.

Coverage

No tests exist for this assertion

e)

If any observer method of the BeforeBeanDiscovery event throws an exception, the exception is treated as a definition error by the container.

Coverage

No tests exist for this assertion

f)

If any BeforeBeanDiscovery method is called outside of the observer method invocation, an IllegalStateException is thrown.

Coverage

No tests exist for this assertion

#### Section 11.5.2 - AfterTypeDiscovery event [after_type_discovery]

a)

The container must fire an event when it has fully completed the type discovery process and before it begins the bean discovery process. The event object must be of type jakarta.enterprise.inject.spi.AfterTypeDiscovery.

Coverage

No tests exist for this assertion

b)

getAlternatives() returns list of enabled alternatives for the application, sorted by priority in ascending order. Alternatives enabled for a bean archive are not included.

Coverage

No tests exist for this assertion

c)

getInterceptors() returns the list of enabled interceptors for the application, sorted by priority in ascending order. Interceptors enabled for a bean archive are not included.

Coverage

No tests exist for this assertion

d)

getDecorators() returns list of enabled decorators for the application, sorted by priority in ascending order. Decorators enabled for a bean archive are not included.

Coverage

No tests exist for this assertion

e)

addAnnotatedType() adds a given AnnotatedType to the set of types which will be scanned during bean discovery, with an identifier.

Coverage

No tests exist for this assertion

ea)

Test AnnotatedTypeConfigurator<?> addAnnotatedType(String id) returns a new AnnotatedTypeConfigurator as defined in AnnotatedTypeConfigurator interface to easily configure the AnnotatedType which will be added at the end of observer invocation. The returned AnnotatedTypeConfigurator is initialized with type and annotations of the provided class.

Coverage

No tests exist for this assertion

f)

If an alternative, interceptor or decorator is added using AfterTypeDiscovery.addAnnotatedType(), non-portable behavior results.

Any observer of this event is permitted to add classes to, or remove classes from, the list of alternatives, list of interceptors or list of decorators. The container must use the final values of these collections, after all observers of AfterTypeDiscovery have been called, to determine the order of the enabled alternatives, interceptors, and decorators for application.

ga)

Test the final values of the list of alternatives.

Coverage

No tests exist for this assertion

gb)

Test the final values of the list of interceptors.

Coverage

No tests exist for this assertion

gc)

Test the final values of the list of decorators.

Coverage

No tests exist for this assertion

The initial values of these collections is defined by the @Priority annotation.

ha)

Test the initial values of the list of alternatives.

Coverage

No tests exist for this assertion

hb)

Test the initial values of the list of interceptors.

Coverage

No tests exist for this assertion

hc)

Test the initial values of the list of decorators.

Coverage

No tests exist for this assertion

i)

If any observer method of an AfterTypeDiscovery event throws an exception, the exception is treated as a definition error by the container.

Coverage

No tests exist for this assertion

j)

If any AfterTypeDiscovery method is called outside of the observer method invocation, an IllegalStateException is thrown.

Coverage

No tests exist for this assertion

#### Section 11.5.3 - AfterBeanDiscovery event [after_bean_discovery]

a)

The container must fire an 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 jakarta.enterprise.inject.spi.AfterBeanDiscovery.

Coverage

No tests exist for this assertion

ca)

addDefinitionError() registers a definition error with the container, causing the container to abort deployment after all observers have been notified.

Coverage

No tests exist for this assertion

addBean() fires an event of type ProcessSyntheticBean 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 ProcessSyntheticBean is fired

Coverage

No tests exist for this assertion

db)

Check that a bean is registered

Coverage

No tests exist for this assertion

dc)

Check that a decorator is registered

Coverage

No tests exist for this assertion

dd)

Check that an interceptor is registered

Coverage

No tests exist for this assertion

de)

Test BeanConfigurator<?> addBean() returns a new BeanConfigurator as defined in BeanConfigurator interface to easily configure the Bean which will be added at the end of observer invocation.

Coverage

No tests exist for this assertion

addObserverMethod() fires an event of type ProcessSyntheticObserverMethod containing the given ObserverMethod and then registers the ObserverMethod with the container, thereby making it available for event notifications.

ea)

Check that the ProcessSynthethicObserverMethod is fired

Coverage

No tests exist for this assertion

eb)

Check that the observer method is registered

Coverage

No tests exist for this assertion

ec)

If the given ObserverMethod does not override either ObserverMethod.notify(T) or ObserverMethod.notify(EventContext<T>), the container automatically detects the problem and treats it as a definition error.

Coverage

No tests exist for this assertion

ed)

Test ObserverMethodConfigurator<?> addObserverMethod() returns a new ObserverMethodConfigurator as defined in ObserverMethodConfigurator interface to easily configure the ObserverMethod which will be added at the end of observer invocation.

Coverage

No tests exist for this assertion

ee)

If the container is unable to process the ObserverMethodConfigurator it automatically detects the problem and treats it as a deployment problem.

Coverage

No tests exist for this assertion

f)

addContext() registers a custom Context object with the container.

Coverage

No tests exist for this assertion

g)

If any observer method of the AfterBeanDiscovery event throws an exception, the exception is treated as a definition error by the container.

Coverage

No tests exist for this assertion

h)

getAnnotatedType() returns the AnnotatedType discovered or added during container initialization. If the id passed is null, the container should substitute the container generated id.

Coverage

No tests exist for this assertion

i)

getAnnotatedTypes() returns the AnnotatedTypes discovered or added during container initialization.

Coverage

No tests exist for this assertion

fb)

A portable extension may take advantage of this event to register beans, interceptors, decorators, observer methods and custom context objects with the container.

j)

If any AfterBeanDiscovery method is called outside of the observer method invocation, an IllegalStateException is thrown.

Coverage

No tests exist for this assertion

#### Section 11.5.3.1 - BeanConfigurator interface [bean_configurator]

With BeanConfigurator you can perform all the operations defined in BeanAttributesConfigurator interface plus the following:

aa)

Initialize the bean metadata with one of its read() methods. It can be done from an existing BeanAttributes or by reading metadata on a given AnnotatedType, according to the rules defined in Concepts.

Coverage

No tests exist for this assertion

ab)

Set the class of the bean with beanClass method.

Coverage

No tests exist for this assertion

b)

Add an injection point for the bean with addInjectionPoint method.

Coverage

No tests exist for this assertion

c)

Add multiple injection points for the bean with addInjectionPoints methods.

Coverage

No tests exist for this assertion

d)

Replace all injection points for the bean with injectionPoints methods.

Coverage

No tests exist for this assertion

e)

Make the bean implements `PassivationCapable` and set its id with id method.

Coverage

No tests exist for this assertion

f)

Set a callback to create a bean instance with createWith() or produceWith() method.

Coverage

No tests exist for this assertion

g)

Set a callback to destroy a bean instance with destroyWith() or disposeWith() method.

Coverage

No tests exist for this assertion

h)

If a BeanConfigurator has no scope specified, the default scope rules, defined in the Default Scope rules apply.

Coverage

No tests exist for this assertion

#### Section 11.5.3.2 - ObserverMethodConfigurator interface [observer_method_configurator]

`ObserverMethodConfigurator` must be initialized from a `java.lang.reflect.Method`, `AnnotatedMethod` or an existing `ObserverMethod` with one of its `read()` methods.

aa)

Test initialization of `ObserverMethodConfigurator` from a `java.lang.reflect.Method`.

Coverage

No tests exist for this assertion

ab)

Test initialization of `ObserverMethodConfigurator` from a `AnnotatedMethod`.

Coverage

No tests exist for this assertion

ac)

Test initialization of `ObserverMethodConfigurator` from an existing `ObserverMethod`.

Coverage

No tests exist for this assertion

With ObserverMethodConfigurator you can perform the following operations:

ba)

Set the `ObserverMethod` bean class with beanClass method.

Coverage

No tests exist for this assertion

baa)

If the class of the bean is not set, the extension class is used.

Coverage

No tests exist for this assertion

bb)

Set the type of the observed event with observedType method.

Coverage

No tests exist for this assertion

bc)

Add a qualifier with addQualifier method.

Coverage

No tests exist for this assertion

bd)

Set or add multiple qualifiers with addQualifiers and qualifiers methods.

Coverage

No tests exist for this assertion

be)

Set the `Reception` type with reception method.

Coverage

No tests exist for this assertion

bf)

Set the `TransactionPhase` type with transactionPhase method.

Coverage

No tests exist for this assertion

bg)

Set the priority with priority method.

Coverage

No tests exist for this assertion

bh)

Define the `Consumer` to call on notification with notifyWith method.

Coverage

No tests exist for this assertion

bi)

Make the observer asynchronous with async method.

Coverage

No tests exist for this assertion

#### Section 11.5.4 - AfterDeploymentValidation event [after_deployment_validation]

a)

The container must fire an 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 jakarta.enterprise.inject.spi.AfterDeploymentValidation.

Coverage

No tests exist for this assertion

b)

addDeploymentProblem() registers a deployment problem with the container, causing the container to abort deployment after all observers have been notified.

Coverage

No tests exist for this assertion

c)

If any observer method of the AfterDeploymentValidation event throws an exception, the exception is treated as a deployment problem by the container.

Coverage

No tests exist for this assertion

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

e)

If any AfterDeploymentValidation method is called outside of the observer method invocation,an IllegalStateException is thrown.

Coverage

No tests exist for this assertion

#### Section 11.5.5 - BeforeShutdown event [before_shutdown]

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 jakarta.enterprise.inject.spi.BeforeShutdown.

Coverage

No tests exist for this assertion

ba)

If any observer method of the BeforeShutdown event throws an exception, the exception is ignored by the container.

#### Section 11.5.6 - ProcessAnnotatedType event [process_annotated_type]

The container must fire an event, before it processes a type, for every Java class, interface (excluding the special kind of interface declaration annotation type) or enum discovered.

aa)

Test class discovered in a bean archive.

Coverage

No tests exist for this assertion

ab)

Test interface discovered in a bean archive.

Coverage

No tests exist for this assertion

ac)

Test enum discovered in a bean archive.

Coverage

No tests exist for this assertion

ae)

Test class added by BeforeBeanDiscovery.addAnnotatedType().

Coverage

No tests exist for this assertion

af)

Test interface added by BeforeBeanDiscovery.addAnnotatedType().

Coverage

No tests exist for this assertion

ag)

Test enum added by BeforeBeanDiscovery.addAnnotatedType().

Coverage

No tests exist for this assertion

ah)

Excluding the special kind of interface declaration annotation type.

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

No tests exist for this assertion

ib)

Test @Vetoed interface discovered in a bean archive.

Coverage

No tests exist for this assertion

ie)

Test @Vetoed class added by BeforeBeanDiscovery.addAnnotatedType().

Coverage

No tests exist for this assertion

if)

Test @Vetoed interface added by BeforeBeanDiscovery.addAnnotatedType().

Coverage

No tests exist for this assertion

ii)

Test @Vetoed package.

Coverage

No tests exist for this assertion

j)

The event object must be of type jakarta.enterprise.inject.spi.ProcessAnnotatedType<X>, where X is the class, for types discovered in a bean archive, or of type jakarta.enterprise.inject.spi.ProcessSyntheticAnnotatedType<X> for types added by BeforeBeanDiscovery.addAnnotatedType().

Coverage

No tests exist for this assertion

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 annotated type, or on any member, or any parameter of any member of the annotated type, as defined in Section 11.4.

fa)

Test annotation on the annotated type.

Coverage

No tests exist for this assertion

fb)

Test annotation on the field declared by the annotated type.

Coverage

No tests exist for this assertion

fc)

Test annotation on the method declared by the annotated type.

Coverage

No tests exist for this assertion

fd)

Test annotation on the constructor declared by the annotated type.

Coverage

No tests exist for this assertion

fe)

Test annotation on the parameter of the method declared by the annotated type.

Coverage

No tests exist for this assertion

ff)

Test annotation on the parameter of the constructor declared by the annotated type.

Coverage

No tests exist for this assertion

g)

The annotation may be applied as a meta-annotation on any annotation considered.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

ba)

getAnnotatedType() returns the AnnotatedType object that will be used by the container to read the declared annotations.

Coverage

No tests exist for this assertion

bb)

setAnnotatedType() replaces the AnnotatedType.

Coverage

No tests exist for this assertion

bba)

configureAnnotatedType() returns an AnnotatedTypeConfigurator (as defined in AnnotatedTypeConfigurator interface) initialized with the AnnotatedType processed by the event to easily configure the AnnotatedType which will be used to replace the original one at the end of observer invocation.

Coverage

No tests exist for this assertion

bbb)

configureAnnotatedType() method always returns the same AnnotatedTypeConfigurator.

Coverage

No tests exist for this assertion

bc)

veto() forces the container to ignore the type.

Coverage

No tests exist for this assertion

bd)

getSource() returns the Extension instance that added the annotated type.

Coverage

No tests exist for this assertion

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 replacing AnnotatedType added by BeforeBeanDiscovery.addAnnotatedType().

Coverage

No tests exist for this assertion

k)

Any observer of this event is permitted to wrap and/or replace the AnnotatedType by calling either setAnnotatedType() or configureAnnotatedType(). If both methods are called within an observer notification an IllegalStateException is thrown.

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

No tests exist for this assertion

f)

If any ProcessAnnotatedType method is called outside of the observer method invocation, an IllegalStateException is thrown.

Coverage

No tests exist for this assertion

#### Section 11.5.7 - ProcessInjectionPoint event [process_injection_point]

a)

The container must fire an event for every injection point of every bean, interceptor and decorator. The event object must be of type jakarta.enterprise.inject.spi.ProcessInjectionPoint<T, X> where T is the bean class and X is the declared type of the injection point.

Coverage

No tests exist for this assertion

ba)

getInjectionPoint() returns the InjectionPoint object that will be used by the container to perform injection.

Coverage

No tests exist for this assertion

bb)

setInjectionPoint() replaces the InjectionPoint.

Coverage

No tests exist for this assertion

bba)

configureInjectionPoint() returns an InjectionPointConfigurator (as defined in InjectionPointConfigurator interface) initialized with the InjectionPoint processed by the event to easily configure the InjectionPoint which will be used to replace the original one at the end of observer invocation.

Coverage

No tests exist for this assertion

bbb)

configureInjectionPoint() method always returns the same InjectionPointConfigurator.

Coverage

No tests exist for this assertion

bc)

addDefinitionError() registers a definition error with the container, causing the container to abort deployment after bean discovery is complete.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

g)

Any observer of this event is permitted to wrap and/or replace the AnnotatedType by calling either setAnnotatedType() or configureAnnotatedType(). If both methods are called within an observer notification an IllegalStateException is thrown.

Coverage

No tests exist for this assertion

d)

If any observer method of a ProcessInjectionPoint event throws an exception, the exception is treated as a definition error by the container.

Coverage

No tests exist for this assertion

e)

If any ProcessInjectionPoint method is called outside of the observer method invocation, an IllegalStateException is thrown.

Coverage

No tests exist for this assertion

#### Section 11.5.7.1 - InjectionPointConfigurator interface [injection_point_configurator]

With InjectionPointConfigurator you can perform the following operation:

ba)

Set the type of `InjectionPoint` with type method.

Coverage

No tests exist for this assertion

bb)

Add a qualifier with addQualifier method.

Coverage

No tests exist for this assertion

bc)

Set or add multiple qualifiers with addQualifiers and qualifiers methods.

Coverage

No tests exist for this assertion

be)

Make the injection point delegate with delegate method.

Coverage

No tests exist for this assertion

bf)

Make the injection point a transient field with transientField method.

Coverage

No tests exist for this assertion

#### Section 11.5.8 - ProcessInjectionTarget event [process_injection_target]

The container must fire an event for every bean, interceptor or decorator. The event object must be of type jakarta.enterprise.inject.spi.ProcessInjectionTarget<X>, where x is the managed bean class.

aaa)

Test event is fired for a managed bean

Coverage

No tests exist for this assertion

getAnnotatedType() returns the AnnotatedType representing the managed bean class.

aba)

Test type for a managed bean

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

da)

addDefinitionError() registers a definition error with the container, causing the container to abort deployment after bean discovery is complete.

Coverage

No tests exist for this assertion

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.

ea)

Test type for a managed bean

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

No tests exist for this assertion

g)

If any ProcessInjectionTarget method is called outside of the observer method invocation, an IllegalStateException is thrown.

Coverage

No tests exist for this assertion

#### Section 11.5.9 - ProcessBeanAttributes event [process_bean_attributes]

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" or beans added programmatically using AfterBeanDiscovery.addBean() or for any built-in beans. The event object must be of type jakarta.enterprise.inject.spi.ProcessBeanAttributes<T> where T is the bean class of the bean, the return type of the producer method, or the type of the producer field.

aa)

Event is fired for enabled bean.

Coverage

No tests exist for this assertion

ab)

Event is fired for enabled interceptor.

Coverage

No tests exist for this assertion

ac)

Event is fired for enabled decorator.

Coverage

No tests exist for this assertion

ad)

No event is fired for any @New qualified bean.

Coverage

No tests exist for this assertion

ae)

No event is fired for beans added programmatically using AfterBeanDiscovery.addBean().

Coverage

No tests exist for this assertion

af)

No event is fired for any built-in bean.

Coverage

No tests exist for this assertion

getAnnotated() returns the AnnotatedType representing the bean class, the AnnotatedMethod representing the producer field, or the AnnotatedField representing the producer field.

baa)

Test managed bean.

Coverage

No tests exist for this assertion

bac)

Test producer method.

Coverage

No tests exist for this assertion

bad)

Test producer field.

Coverage

No tests exist for this assertion

bb)

getBeanAttributes() returns the BeanAttributes object that will be used by the container to manage instances of the bean.

Coverage

No tests exist for this assertion

bc)

setBeanAttributes() replaces the BeanAttributes.

Coverage

No tests exist for this assertion

bca)

configureBeanAttributes() returns a BeanAttributesConfigurator (as defined in BeanAttributesConfigurator interface) initialized with the BeanAttributes processed by the event to easily configure the BeanAttributes which will be used to replace the original one at the end of observer invocation.

Coverage

No tests exist for this assertion

bcb)

configureBeanAttributes() method always returns the same BeanAttributesConfigurator

Coverage

No tests exist for this assertion

bd)

addDefinitionError() registers a definition error with the container, causing the container to abort deployment after bean discovery is complete.

Coverage

No tests exist for this assertion

be)

veto() forces the container to ignore the bean.

Coverage

No tests exist for this assertion

bf)

ignoreFinalMethods() method instructs the container to ignore all non-static, final methods with public, protected or default visibility declared on any bean type of the specific bean during validation of injection points that require proxyable bean type. These method should never be invoked upon bean instances. Otherwise, unpredictable behavior results. It will bypass standard rules defined in Unproxyable bean types.

Coverage

No tests exist for this assertion

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. Changes to BeanAttributes are not propagated to the annotated type from which the bean definition was created.

ca)

Test the final value of this property is used.

Coverage

No tests exist for this assertion

cc)

Test the changes are not propagated.

Coverage

No tests exist for this assertion

d)

If any observer method of a ProcessBeanAttributes event throws an exception, the exception is treated as a definition error by the container.

Coverage

No tests exist for this assertion

g)

Any observer of this event is permitted to wrap and/or replace the AnnotatedType by calling either setAnnotatedType() or configureAnnotatedType(). If both methods are called within an observer notification an IllegalStateException is thrown.

Coverage

No tests exist for this assertion

e)

Any bean which has its bean attributes altered must have it’s definition validated during deployment validation.

Coverage

No tests exist for this assertion

f)

If any ProcessBeanAttributes method is called outside of the observer method invocation, an IllegalStateException is thrown.

Coverage

No tests exist for this assertion

#### Section 11.5.9.1 - BeanAttributesConfigurator interface [bean_attributes_configurator]

a)

BeanAttributesConfigurator is obtainable during ProcessBeanAttributes event and is therefore automatically initialized from existing BeanAttributes.

Coverage

No tests exist for this assertion

With `BeanAttributesConfigurator` you can perform the following operation:

ba)

Add type with addType or addTransitiveTypeClosure methods.

Coverage

No tests exist for this assertion

bb)

Set multiple types with types methods.

Coverage

No tests exist for this assertion

bc)

Set scope with scope method.

Coverage

No tests exist for this assertion

bd)

Add a qualifier with addQualifier method.

Coverage

No tests exist for this assertion

be)

Set or add multiple qualifiers with addQualifiers and qualifiers methods.

Coverage

No tests exist for this assertion

bf)

Add a stereotype with addStereotype method.

Coverage

No tests exist for this assertion

bg)

Set or add multiple stereotypes with addStereotypes and stereotypes methods.

Coverage

No tests exist for this assertion

bh)

Set the bean name name method.

Coverage

No tests exist for this assertion

bi)

Make the bean an alternative with alternative methods.

Coverage

No tests exist for this assertion

#### Section 11.5.10 - ProcessBean event [process_bean]

aa)

The container must fire an event for each 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".

Coverage

No tests exist for this assertion

ba)

For a managed bean with bean class X, the container must raise an event of type ProcessManagedBean<X>.

Coverage

No tests exist for this assertion

bb)

Test ProcessManagedBean is fired after ProcessBeanAttributes.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

eab)

Test ProcessProducerMethod is fired after ProcessBeanAttributes.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

ebb)

Test ProcessProducerField is fired after ProcessBeanAttributes.

Coverage

No tests exist for this assertion

eca)

For a custom implementation of Bean, the container must raise an event of type ProcessSyntheticBean <X>.

Coverage

No tests exist for this assertion

ec)

Resources are considered to be producer fields.

Coverage

No tests exist for this assertion

The interface jakarta.enterprise.inject.spi.ProcessBean is a supertype of all these event types.

eda)

Test ProcessManagedBean

Coverage

No tests exist for this assertion

edc)

Test ProcessProducerMethod

Coverage

No tests exist for this assertion

edd)

Test ProcessProducerField

Coverage

No tests exist for this assertion

getAnnotated() returns the AnnotatedType representing the bean class, the AnnotatedMethod representing the producer method, or the AnnotatedField representing the producer field. If invoked upon a ProcessSyntheticBean event, non-portable behavior results and the returned value should be ignored.

efa)

Test ProcessManagedBean

Coverage

No tests exist for this assertion

efc)

Test ProcessProducerMethod

Coverage

No tests exist for this assertion

efd)

Test ProcessProducerField

Coverage

No tests exist for this assertion

getBean() returns the Bean object that is about to be registered. The Bean may implement Interceptor or Decorator.

fa)

Test ProcessManagedBean

Coverage

No tests exist for this assertion

fc)

Test ProcessProducerMethod

Coverage

No tests exist for this assertion

fd)

Test ProcessProducerField

Coverage

No tests exist for this assertion

h)

addDefinitionError() registers a definition error with the container, causing the container to abort deployment after bean discovery is complete.

Coverage

No tests exist for this assertion

hd)

If any observer method of a ProcessBean event throws an exception, the exception is treated as a definition error by the container.

Coverage

No tests exist for this assertion

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

Check the getAnnotatedProducerMethod()

Coverage

No tests exist for this assertion

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

Check the getAnnotatedDisposesParameter()

Coverage

No tests exist for this assertion

Check the getAnnotatedBeanClass()

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

Check for managed bean

Coverage

No tests exist for this assertion

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

Check the getAnnotatedProducerField()

Coverage

No tests exist for this assertion

o)

If any ProcessBean method is called outside of the observer method invocation, an IllegalStateException is thrown.

Coverage

No tests exist for this assertion

#### Section 11.5.11 - ProcessProducer event [process_producer]

The container must fire an event for each producer method or field of each enabled bean, including resources.

aa)

Test producer method

Coverage

No tests exist for this assertion

ab)

Test producer field

Coverage

No tests exist for this assertion

ac)

Test resource producer field

Coverage

No tests exist for this assertion

The event object must be of type jakarta.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

No tests exist for this assertion

bb)

Test producer field

Coverage

No tests exist for this assertion

getAnnotatedMember() returns the AnnotatedField representing the producer field or the AnnotatedMethod representing the producer method.

ca)

Test producer method

Coverage

No tests exist for this assertion

cb)

Test producer field

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

db)

Test producer field

Coverage

No tests exist for this assertion

e)

setProducer() replaces the Producer.

Coverage

No tests exist for this assertion

f)

configureProducer() returns a ProducerConfigurator (as defined in ProducerConfigurator interface) initialized with the Producer processed by this event to configure the Producer that will replace the original one at the end of the observer invocation. Each call returns the same configurator instance within an observer notification

Coverage

No tests exist for this assertion

g)

addDefinitionError() registers a definition error with the container, causing the container to abort deployment after bean discovery is complete.

Coverage

No tests exist for this assertion

Any observer of this event is permitted to wrap and/or replace the Producer by calling either setProducer() or configureProducer(). If both methods are called within an observer notification an IllegalStateException is thrown. 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

gc)

If both methods setProducer() and configureProducer() are called within an observer notification an IllegalStateException is thrown.

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

No tests exist for this assertion

i)

If any ProcessProducer method is called outside of the observer method invocation, an IllegalStateException is thrown.

Coverage

No tests exist for this assertion

#### Section 11.5.11.1 - ProducerConfigurator interface [producer_configurator]

With ProducerConfigurator you can perform the following operations:

a)

Set a callback to produce a new instance with produceWith() method.

Coverage

No tests exist for this assertion

b)

Set a callback to destroy the produced instance with disposeWith() method.

Coverage

No tests exist for this assertion

#### Section 11.5.12 - ProcessObserverMethod event [process_observer_method]

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

No tests exist for this assertion

aab)

For a custom implementation of jakarta.enterprise.inject.spi.ObserverMethod, the container must raise an event of type jakarta.enterprise.inject.spi.ProcessSyntheticObserverMethod<T, X>, where T is the observed event type of the observer method and X is the return value of ObserverMethod.getBeanClass().

Coverage

No tests exist for this assertion

aba)

getAnnotatedMethod() returns the AnnotatedMethod representing the observer method. If invoked upon a ProcessSyntheticObserverMethod event, non-portable behavior results and the returned value should be ignored.

Coverage

No tests exist for this assertion

ba)

getObserverMethod() returns the ObserverMethod object that will be used by the container to call the observer method.

Coverage

No tests exist for this assertion

da)

addDefinitionError() registers a definition error with the container, causing the container to abort deployment after bean discovery is complete.

Coverage

No tests exist for this assertion

daa)

setObserverMethod() replaces the ObserverMethod.

Coverage

No tests exist for this assertion

dab)

configureObserverMethod() returns an ObserverMethodConfigurator (as defined in ObserverMethodConfigurator interface) initialized with the ObserverMethod processed by the event to easily configure the ObserverMethod which will be used to replace the original one at the end of observer invocation.

Coverage

No tests exist for this assertion

dac)

configureObserverMethod() method always returns the same ObserverMethodConfigurator

Coverage

No tests exist for this assertion

dad)

veto() forces the container to ignore the ObserverMethod.

Coverage

No tests exist for this assertion

dae)

getSource() returns the Extension instance that added the observer method.

Coverage

No tests exist for this assertion

e)

Any observer of this event is permitted to wrap and/or replace the AnnotatedType by calling either setAnnotatedType() or configureAnnotatedType(). If both methods are called within an observer notification an IllegalStateException is thrown.

Coverage

No tests exist for this assertion

db)

If any observer method of a ProcessObserverMethod event throws an exception, the exception is treated as a definition error by the container.

Coverage

No tests exist for this assertion

dc)

If any ProcessObserverMethod method is called outside of the observer method invocation, an IllegalStateException is thrown.

Coverage

No tests exist for this assertion

#### Section 11.6 - Configurators interfaces [configurators]

CDI 2.0 introduced the following Configurators interface:

aa)

AnnotatedTypeConfigurator for AnnotatedType configuration.

ab)

InjectionPointConfigurator for InjectionPoint configuration

ac)

BeanAttributesConfigurator for BeanAttributes configuration

ad)

BeanConfigurator for Bean configuration

ae)

ObserverMethodConfigurator for ObserverMethod configuration.

af)

ProducerConfigurator interface for Producer configuration

ag)

The container must provide implementation for all these configurators and make them available in matching container lifecycle events as defined in `Container lifecycle events`.

#### Section 11.7 - The InterceptionFactory interface [interception_factory]

a)

Method ignoreFinalMethods() instructs the container to ignore all non-static, final methods with public, protected or default visibility declared by any class in the type hierarchy of the intercepted instance during invocation of createInterceptedInstance() method. Ignored methods should never be invoked upon the wrapper instance. Otherwise, unpredictable behavior results.

Coverage

No tests exist for this assertion

b)

Method configure() returns an AnnotatedTypeConfigurator (as defined in AnnotatedTypeConfigurator SPI) initialized with the AnnotatedType created either for the class passed to BeanManager.createInterceptionFactory(CreationalContext, Class) or derived from the InterceptionFactory parameter injection point. The method always return the same AnnotatedTypeConfigurator

Coverage

No tests exist for this assertion

Method createInterceptedInstance()

ca)

returns a wrapper instance whose method invocations are intercepted by method interceptors and forwarded to a provided instance.

Coverage

No tests exist for this assertion

cb)

can be only called once, subsequent calls will throw an IllegalStateException.

Coverage

No tests exist for this assertion

cd)

If it is called at the type of the instance which is not proxyable as defined in `Unproxyable bean types` an UnproxyableResolutionException exception is thrown.

Coverage

No tests exist for this assertion

ce)

If the provided instance is an internal container construct (such as client proxy), non-portable behavior results.

f)

An InterceptionFactory can be obtain be calling BeanManager.createInterceptionFactory as defined in `Obtain an InterceptionFactory`

Coverage

No tests exist for this assertion

g)

The container must provide a bean with scope `@Dependent`, bean type InterceptionFactory and qualifier `@Default`.

Coverage

No tests exist for this assertion

h)

If an injection point of type InterceptionFactory and qualifier @Default exists and is not a parameter of a producer method, the container automatically detects the problem and treats it as a definition error.

Coverage

No tests exist for this assertion

#### Section 12 - Packaging and deployment [packaging_deployment]

a)

When an application is started, the container must perform bean discovery, detect definition errors and deployment problems and raise events that allow portable extensions to integrate with the deployment lifecycle.

Bean discovery is the process of determining:

ba)

The bean archives that exist in the application, and the beans they contain

bb)

Which alternatives, interceptors and decorators are enabled for each bean archive

bc)

The ordering of enabled interceptors and decorators

c)

Additional beans may be registered programmatically with the container by the application or a portable extension after the automatic bean discovery completes. Portable extensions may even integrate with the process of building the Bean object for a bean, to enhance the container’s built-in functionality.

#### Section 12.1 - Bean archives [bean_archive]

a)

Bean classes of enabled beans must be deployed in bean archives.

oa)

An archive which contains a beans.xml file with the bean-discovery-mode of none is not a bean archive.

Coverage

No tests exist for this assertion

ob)

An archive which contains an extension and no beans.xml file is not a bean archive.

Coverage

No tests exist for this assertion

An explicit bean archive is an archive which contains a beans.xml file with a version number of 1.1 (or later), with the bean-discovery-mode of all, or with no version number, or that is an empty file.

ba)

Test an archive which contains a beans.xml file with a version number of 1.1, with the bean-discovery-mode of all.

Coverage

No tests exist for this assertion

bb)

Test an archive which contains a beans.xml file with no version number.

Coverage

No tests exist for this assertion

bc)

Test an archive which contains an empty beans.xml.

Coverage

No tests exist for this assertion

ca)

An implicit bean archive is any other archive which contains one or more bean classes with a bean defining annotation as defined in Section 2.5.1, “Bean defining annotations”.

Coverage

No tests exist for this assertion

When determining which archives are bean archives, the container must consider:

da)

Library jars

dc)

Directories in the JVM classpath.

The beans.xml file must be named:

fa)

META-INF/beans.xml

h)

If beans.xml file with version 1.1 is used, the bean-discovery-mode attribute is required.

i)

For compatibility with Contexts and Dependency 1.0, products must contain an option to cause an archive to be ignored by the container when no beans.xml is present.

k)

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.

l)

Explicit bean archives may contain classes which are not deployed as beans. For example a bean archive might contain an abstract class not annotated with @Decorator.

m)

Implicit bean archives are likely to contain classes which are not deployed as beans.

n)

An extension may be deployed in any archive, including those that are not bean archives.

Coverage

No tests exist for this assertion

#### Section 12.2 - Application initialization lifecycle [initialization]

a)

When an application is started, the container performs the following steps.

b)

First, the container must search for service providers for the service jakarta.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

No tests exist for this assertion

c)

Next, the container must fire an event of type BeforeBeanDiscovery, as defined in Section 11.5.1, "BeforeBeanDiscovery event".

Coverage

No tests exist for this assertion

i)

Next, the container must perform type discovery, as defined in Section 12.4.1, “Type discovery”

Coverage

No tests exist for this assertion

j)

Next, the container must fire an event of type AfterTypeDiscovery, as defined in Section 11.5.2., "AfterTypeDiscovery event".

Coverage

No tests exist for this assertion

ja)

Next, the container must perform bean discovery, as defined in Section 12.4.3, “Bean discovery”

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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.9, "Problems detected automatically by the container".

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

h)

Finally, the container begins directing requests to the application.

Coverage

No tests exist for this assertion

#### Section 12.3 - Application shutdown lifecycle [shutdown]

When an application is stopped, the container performs the following steps:

a)

First, the container must destroy all contexts.

Coverage

No tests exist for this assertion

b)

Finally, the container must fire an event of type BeforeShutdown, as defined in Section 11.5.4, "BeforeShutdown event".

Coverage

No tests exist for this assertion

#### Section 12.4 - Type and Bean discovery [type_bean_discovery]

a)

The container automatically discovers managed beans (according to the rules of Section 3.1.1, "Which Java classes are managed beans?") in bean archives and searches the bean classes for producer methods, producer fields, disposer methods and observer methods.

#### Section 12.4.1 - Type discovery [type_discovery_steps]

First the container must discover types. The container discovers:

a)

The container discovers each Java class, interface or enum deployed in an explicit bean archive.

Coverage

No tests exist for this assertion

b)

The container discovers each Java class with a bean defining annotation in an implicit bean archive.

Coverage

No tests exist for this assertion

For every type discovered the container must create an AnnotatedType representing the type and fire an event of type ProcessAnnotatedType, as defined in Section 11.5.6.

c)

Check managed bean

Coverage

No tests exist for this assertion

d)

If an extension calls BeforeBeanDiscovery.addAnnotatedType() or AfterTypeDiscovery.addAnnotatedType(), the type passed must be added to the set of discovered types.

Coverage

No tests exist for this assertion

#### Section 12.4.2 - Exclude filters [exclude_filters]

Exclude filters are defined by <exclude> elements in the beans.xml for the bean archive as children of the <scan> element.

a)

By default an exclude filter is active.

Coverage

No tests exist for this assertion

b)

An exclude filter is not active if the definition contains a child element named <if-class-available> with a name attribute, and the classloader for the bean archive can load a class for that name.

Coverage

No tests exist for this assertion

c)

An exclude filter is not active if the definition contains a child element named <if-class-not-available> with a name attribute, and the classloader for the bean archive cannot load a class for that name.

Coverage

No tests exist for this assertion

d)

An exclude filter is not active if the definition contains a child element named <if-system-property> with a name attribute, and there is no system property defined for that name.

Coverage

No tests exist for this assertion

e)

An exclude filter is not active if the definition contains a child element named <if-system-property> with a name attribute and a value attribute, and there is no system property defined for that name with that value.

Coverage

No tests exist for this assertion

f)

The type is excluded from discovery if the fully qualified name of the type being discovered matches the value of the name attribute of the exclude filter.

Coverage

No tests exist for this assertion

g)

The type is excluded from discovery if the package name of the type being discovered matches the value of the name attribute with a suffix ".*" of the exclude filter.

Coverage

No tests exist for this assertion

h)

The type is excluded from discovery if the package name of the type being discovered starts with the value of the name attribute with a suffix ".**" of the exclude filter.

Coverage

No tests exist for this assertion

#### Section 12.4.3 - Trimmed bean archive [trimmed_bean_archive]

a)

If an explicit bean archive contains the <trim/> element in its beans.xml file, types that don’t have either a bean defining annotation (as defined in Bean defining annotations) or any scope annotation, are removed from the set of discovered types.

Coverage

No tests exist for this assertion

#### Section 12.4.4 - Bean discovery [bean_discovery_steps]

For every type in the set of discovered types (as defined in Type discovery), the container must:

c)

Inspect the type metadata to determine if it is a bean.

d)

detect definition errors by validating the class and its metadata.

e)

if the class is a managed bean, fire an event of type ProcessInjectionPoint for each injection point in the class, as defined in ProcessInjectionPoint event.

Coverage

No tests exist for this assertion

f)

if the class is a managed bean, fire an event of type ProcessInjectionTarget, as defined in ProcessInjectionTarget event.

Coverage

No tests exist for this assertion

g)

determine which alternatives, interceptors and decorators are enabled, according to the rules defined in Enabled and disabled beans, Interceptor enablement and ordering and Decorator enablement and ordering.

Coverage

No tests exist for this assertion

h)

if the class is an enabled bean, interceptor or decorator, fire an event of type ProcessBeanAttributes, as defined in ProcessBeanAttributes event.

Coverage

No tests exist for this assertion

i)

if the class is an enabled bean, interceptor or decorator and if ProcessBeanAttributes.veto() wasn’t called in previous step, fire an event which is a subtype of ProcessBean, as defined in ProcessBean event.

Coverage

No tests exist for this assertion

For each enabled bean, the container must search the class for producer methods and fields, as defined in Producer methods and in Producer fields, including resources, and for each producer:

ja)

if it is a producer method, fire an event of type ProcessInjectionPoint for each injection point in the method parameters, as defined in ProcessInjectionPoint event

Coverage

No tests exist for this assertion

jb)

fire an event of type ProcessProducer, as defined in ProcessProducer event.

Coverage

No tests exist for this assertion

jc)

if the producer method or field is enabled, fire an event of type ProcessBeanAttributes, as defined in ProcessBeanAttributes event

Coverage

No tests exist for this assertion

jd)

if the producer method or field is enabled and if ProcessBeanAttributes.veto() wasn’t called in previous step, fire an event which is a subtype of ProcessBean, as defined in ProcessBean event.

Coverage

No tests exist for this assertion

je)

For each enabled bean, the container must search for disposer methods as defined in Disposer methods, and for each disposer method fire an event of type ProcessInjectionPoint for each injection point in the method parameters, as defined in ProcessInjectionPoint event.

Coverage

No tests exist for this assertion

For each enabled bean, the container must search the class for observer methods, and for each observer method:

ka)

fire an event of type ProcessInjectionPoint for each injection point in the method parameters, as defined in ProcessInjectionPoint event

Coverage

No tests exist for this assertion

kb)

fire an event of type ProcessObserverMethod, as defined in ProcessObserverMethod event.

Coverage

No tests exist for this assertion

l)

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)

For each enabled interceptor, the container registers an instance of the Interceptor interface as defined in Section 11.1.2, "The Interceptor interface".

n)

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

No tests exist for this assertion

#### Section 13 - Bootstrapping a CDI container in Java SE [se_bootstrap]

a)

In Java SE, the CDI container must be explicitly bootstrapped by the application. This is performed with `SeContainerInitializer` abstract class and its static method `newInstance()`.

Coverage

No tests exist for this assertion

b)

`SeContainerInitializer` is a service provider of the service jakarta.enterprise.inject.se.SeContainerInitializer declared in META-INF/services. It allows the configuration of the CDI container before its bootstrapping.

c)

The `SeContainerInitializer.initialize()` method bootstraps the container and returns a `SeContainer` instance.

Coverage

No tests exist for this assertion

Unless specified differently each method of `SeContainerInitializer` returns the current `SeContainerInitializer` object.

da)

newInstance() static method returns an instance of the implementation of `SeContainerInitializer` discovered by java service-provider. Each call returns a new instance of `SeContainerInitializer`.

Coverage

No tests exist for this assertion

db)

addBeanClasses() add classes to the the synthetic bean archive

Coverage

No tests exist for this assertion

dc)

addPackages() add packages content to the synthetic bean archive. Versions exist by providing classes in the wished package or Package objects themselves. Other version of the method allows recursive addition

Coverage

No tests exist for this assertion

de)

addExtensions() add the provided extensions (class or instance) to the synthetic bean archive.

Coverage

No tests exist for this assertion

df)

enableInterceptors() adds interceptor classes to the list of enabled interceptors for the synthetic bean archive.

Coverage

No tests exist for this assertion

dg)

enableDecorators() adds decorator classes to the list of enabled decorators for the synthetic bean archive.

Coverage

No tests exist for this assertion

dh)

selectAlternatives() adds alternatives classes to the list of selected alternatives for the synthetic bean archive.

Coverage

No tests exist for this assertion

di)

selectAlternativeStereotypes() adds alternative stereotype classes to the list of selected alternative stereotypes for the synthetic bean archive.

Coverage

No tests exist for this assertion

dj)

addProperty() add a configuration property for the container

Coverage

No tests exist for this assertion

dk)

setProperties() set the Map of configuration properties for the container. replace previous properties.

Coverage

No tests exist for this assertion

dm)

disableDiscovery() deactivate automatic type scanning and discovery. All bean archive will be ignored except the implicit bean archive.

Coverage

No tests exist for this assertion

dn)

setClassLoader() change the default class loader for the container

Coverage

No tests exist for this assertion

do)

initialize() bootstrap the container and returns a `SeContainer` as defined in `SeContainer interface`.

Coverage

No tests exist for this assertion

e)

Every invocation of the `SeContainerInitializer.initialize()` method returns a new `SeContainer` instance.

Coverage

No tests exist for this assertion

f)

The application context is started automatically by the container on start up.

Coverage

No tests exist for this assertion

#### Section 13.1 - SeContainerInitializer class [se_container_initializer]

a)

A CDI implementation is required to provide an implementation of `SeContainerInitializer` declared as a service-provider. `newInstance()` static method uses java service-provider to obtain an implementation of `SeContainerInitializer` and return an instance of it. There must be exactly one provider available, otherwise an `IllegalStateException` is thrown.

Coverage

No tests exist for this assertion

b)

`SeContainerInitializer` configuration allows explicit addition of elements to the set of automatically discovered elements. These additions are done in an internal synthetic bean archive that is added to the set of bean archives discovered by the container during deployment.

Coverage

No tests exist for this assertion

c)

This synthetic bean archive behaves like an explicit bean archive (as defined in Bean archives).

#### Section 13.2 - SeContainer interface [se_container]

a)

The jakarta.enterprise.inject.se.SeContainer interface provides access to the BeanManager and programmatic lookup as defined in The Instance interface.

Coverage

No tests exist for this assertion

b)

SeContainer extends AutoCloseable, so when dereferenced, it should shutdown automatically.

'SeContainer' methods:

ca)

close() method explicitly shutdown the container. If it is called and the container was already shutdown, it throws an IllegalStateException.

Coverage

No tests exist for this assertion

cb)

isRunning() method returns true if called before container shutdown and false after.

Coverage

No tests exist for this assertion

cc)

getBeanManager() method returns the BeanManager (as defined in The BeanManager object) for the running container. if it is called and the container was already shutdown, it throws an IllegalStateException.

Coverage

No tests exist for this assertion

d)

SeContainer implements jakarta.enterprise.inject.Instance and therefore might be used to perform programmatic lookup as defined in "The Instance interface". If no qualifier is passed to SeContainer.select() method, the @Default qualifier is assumed.

Coverage

No tests exist for this assertion

e)

If any Instance.select() method is called and the container was already shutdown, the IllegalStateException is thrown.

Coverage

No tests exist for this assertion

#### Section 14.1.1 - Application context lifecycle in Java SE [application_context_se]

a)

The application context is shared between all the beans that execute within the same container

Coverage

No tests exist for this assertion

b)

An event with qualifier @Initialized(ApplicationScoped.class) is fired when the application context is initialized

Coverage

No tests exist for this assertion

c)

An event with qualifier @Destroyed(ApplicationScoped.class) is fired when the application is destroyed

Coverage

No tests exist for this assertion

d)

The event payload is any java.lang.Object

Coverage

No tests exist for this assertion

#### Section 15.1 - Bean archive in Java SE [bean_archive_se]

An archive which doesn’t contain a beans.xml file can’t be discovered as an implicit bean archive unless:

a)

Application is launched with system property jakarta.enterprise.inject.scan.implicit set to true

Coverage

No tests exist for this assertion

b)

the container was initialized with a parameter map containing an entry with jakarta.enterprise.inject.scan.implicit as key and Boolean.TRUE as value

Coverage

No tests exist for this assertion

#### Section 16.1.1 - Obtaining a reference to the CDI container in Java SE [provider_se]

a)

In Java SE, while the access to CDI container and `BeanManager` described in `Obtaining a reference to the CDI container` is available, the preferred way to access them is through `SeContainer` interface as described in `SeContainer interface`.

#### Section 17.2 - Bean types for Jakarta EE component [bean_types_ee]

The bean types of a bean may be restricted by annotating the bean class or producer method or field with the annotation @jakarta.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 session bean

Coverage

No tests exist for this assertion

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.

b)

Check session bean

Coverage

No tests exist for this assertion

#### Section 17.3.1 - Built-in scope types in Jakarta EE [builtin_scopes_ee]

a)

When running in Jakarta EE, the implementations of the @RequestScoped, @ApplicationScoped and @SessionScoped annotations provided by the container, represent the standard scopes defined by the Java Servlets specification.

#### Section 17.4 - Default bean discovery mode for Jakarta EE [default_bean_discovery_ee]

When running in Jakarta EE, If the bean discovery mode is annotated, the container must extend the rules defined in Default bean discovery mode with:

a)

bean classes of EJB sessions beans, are discovered

Coverage

No tests exist for this assertion

b)

producer methods that are on an EJB session bean are discovered

Coverage

No tests exist for this assertion

c)

producer fields that are on an EJB session bean are discovered

Coverage

No tests exist for this assertion

d)

disposer methods that are on an EJB session bean are discovered

Coverage

No tests exist for this assertion

e)

observer methods that are on an EJB session bean are discovered.

Coverage

No tests exist for this assertion

#### Section 17.5 - Bean names in Jakarta EE [names_ee]

a)

A bean with a name may be referred to by its name in Unified EL expressions.

Coverage

No tests exist for this assertion

#### Section 17.5.1 - Default bean names for EJB session beans [default_name_ee]

a)

In the circumstances listed in 2.6.2 "Default bean names", the rule for determining default name for an EJB session bean are defined in 17.2.5 "Default bean name for a session bean".

#### Section 18.1.1 - Which Java classes are managed beans in Jakarta EE? [what_classes_are_beans_ee]

a)

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

Coverage

No tests exist for this assertion

b)

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

Coverage

No tests exist for this assertion

#### Section 18.2 - EJB Session beans [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 or in a package annotated @Vetoed.

Coverage

No tests exist for this assertion

ab)

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

No tests exist for this assertion

c)

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

Coverage

No tests exist for this assertion

da)

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

Coverage

No tests exist for this assertion

e)

A stateful session bean may have any scope.

Coverage

No tests exist for this assertion

f)

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

j)

If packages annotated @Vetoed are split across classpath entries, non-portable behavior results. An application can prevent packages being split across jars by sealing the package as defined by the Extension Mechanism Architecture.

#### Section 18.2.1 - EJB remove methods of session beans [session_bean_ejb_remove_method]

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 18.2.2 - Bean types of a session bean [session_bean_types]

aa)

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

Coverage

No tests exist for this assertion

ba)

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

Coverage

No tests exist for this assertion

c)

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

Coverage

No tests exist for this assertion

d)

Remote interfaces are not included in the set of bean types

Coverage

No tests exist for this assertion

e)

The resulting set of bean types for a session bean consists only of legal bean types, all other types are removed from the set of bean types.

Coverage

No tests exist for this assertion

#### Section 18.2.3 - Declaring a session bean [declaring_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

No tests exist for this assertion

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

ba)

Test a bean class with a scope.

Coverage

No tests exist for this assertion

bb)

Test a bean class with a name.

Coverage

No tests exist for this assertion

bd)

Test a bean class with a stereotype.

Coverage

No tests exist for this assertion

be)

Test a bean class with a qualifier.

Coverage

No tests exist for this assertion

c)

A session bean class may extend another bean class.

Coverage

No tests exist for this assertion

#### Section 18.2.4 - Specializing a session bean [specialize_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

No tests exist for this assertion

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

No tests exist for this assertion

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.

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

The second bean is never instantiated.

Coverage

No tests exist for this assertion

#### Section 18.2.5 - Default bean name for a session bean [session_bean_name]

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

No tests exist for this assertion

#### Section 18.3 - Producer methods on EJB session bean [producer_method_ee]

a)

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

Coverage

No tests exist for this assertion

The following assertion is not made explicitly by the spec, however it is implied 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

No tests exist for this assertion

#### Section 18.3.1 - Declaring a producer method in an EJB session bean [declaring_producer_method_ee]

a)

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

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 18.4 - Producer field on EJB session bean [producer_field_ee]

a)

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

Coverage

No tests exist for this assertion

#### Section 18.4.1 - Declaring a producer field in an EJB session bean [declaring_producer_field_ee]

a)

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

No tests exist for this assertion

#### Section 18.5 - Disposer methods on EJB session bean [disposer_method_ee]

a)

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

Coverage

No tests exist for this assertion

#### Section 18.5.1 - Declaring a disposer method on an EJB session bean [declaring_disposer_method_ee]

a)

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

Coverage

No tests exist for this assertion

#### Section 18.6 - Jakarta EE components [javaee_components]

The instance used by the container to service an invocation of a Jakarta EE component will not be the same instance obtained when using @Inject, instantiated by the container to invoke a producer method, observer method or disposer method, or instantiated by the container to access the value of a producer field.

a)

Test instance obtained using @Inject.

Coverage

No tests exist for this assertion

b)

Test instance instantiated by the container to invoke a producer method.

Coverage

No tests exist for this assertion

c)

Test instance instantiated by the container to invoke a disposer method.

Coverage

No tests exist for this assertion

d)

Test instance instantiated by the container to invoke a observer method.

Coverage

No tests exist for this assertion

e)

Test instance instantiated by the container to access the value of a producer field.

Coverage

No tests exist for this assertion

#### Section 18.7 - Resources [resources]

ka)

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

l)

A resource may not declare a bean EL name

#### Section 18.7.1 - Declaring a resource [declaring_resource]

aa)

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

bb)

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

Coverage

No tests exist for this assertion

cc)

For a persistence context, @PersistenceContext must be specified.

Coverage

No tests exist for this assertion

dd)

For a persistence unit, @PersistenceUnit must be specified.

Coverage

No tests exist for this assertion

ee)

For a remote EJB, @EJB must be specified.

Coverage

No tests exist for this assertion

ff)

For a web service, @WebServiceRef must be specified.

Coverage

No tests exist for this assertion

gg)

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

No tests exist for this assertion

i)

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

Coverage

No tests exist for this assertion

j)

If the matching object in the Jakarta 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 error.

Coverage

No tests exist for this assertion

#### Section 18.7.2 - Bean types of a resource [resource_types]

The unrestricted set of bean types for 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

No tests exist for this assertion

ab)

Check @PersistenceContext

Coverage

No tests exist for this assertion

ac)

Check @PersistenceUnit

Coverage

No tests exist for this assertion

ad)

Check @EJB

Coverage

No tests exist for this assertion

ae)

Check @WebServiceRef

Coverage

No tests exist for this assertion

b)

The resulting set of bean types for a resource consists only of legal bean types, all other types are removed from the set of bean types.

#### Section 18.8 - Additional built-in beans [additional_builtin_beans]

a)

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

Coverage

No tests exist for this assertion

b)

A Jakarta 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

No tests exist for this assertion

da)

A servlet container must provide a bean with qualifier @Default and bean type jakarta.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

No tests exist for this assertion

db)

A servlet container must provide a bean with qualifier @Default and bean type jakarta.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

No tests exist for this assertion

dc)

A servlet container must provide a bean with qualifier @Default and bean type jakarta.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

No tests exist for this assertion

e)

If a Jakarta 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 Jakarta EE platform specification, the container automatically detects the problem and treats it as a definition error.

Coverage

No tests exist for this assertion

#### Section 18.9 - Injected fields in Jakarta EE [injected_fields_ee]

An injected field is a non-static, non-final field of a bean class or of any other classes supporting injection.

b)

Test a Jakarta EE component class.

Coverage

No tests exist for this assertion

#### Section 18.10 - Initializer methods in Jakarta EE [initializer_methods_ee]

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

b)

Test a Jakarta EE component class.

Coverage

No tests exist for this assertion

e)

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

Coverage

No tests exist for this assertion

f)

All initializer method parameters are injection points.

Coverage

No tests exist for this assertion

#### Section 18.11 - @New qualified beans in Jakarta EE [new_ee]

j)

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

Coverage

No tests exist for this assertion

k)

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

Coverage

No tests exist for this assertion

l)

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

Coverage

No tests exist for this assertion

m)

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

Coverage

No tests exist for this assertion

n)

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

Coverage

No tests exist for this assertion

o)

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

Coverage

No tests exist for this assertion

p)

This second bean has scope @Dependent.

Coverage

No tests exist for this assertion

r)

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

Coverage

No tests exist for this assertion

s)

This second bean has no bean name.

Coverage

No tests exist for this assertion

t)

This second bean has no stereotypes.

Coverage

No tests exist for this assertion

u)

This second bean has no observer methods.

Coverage

No tests exist for this assertion

v)

This second bean has no producer methods.

Coverage

No tests exist for this assertion

x)

This second bean has no disposer methods.

Coverage

No tests exist for this assertion

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.

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 18.12 - Inheritance of type-level metadata in Jakarta EE [type_level_inheritance_ee]

Suppose a class X is extended directly or indirectly by the bean class of a managed 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.

al)

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

Coverage

No tests exist for this assertion

ala)

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

Coverage

No tests exist for this assertion

am)

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

Coverage

No tests exist for this assertion

ama)

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

Coverage

No tests exist for this assertion

an)

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

Coverage

No tests exist for this assertion

ana)

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

Coverage

No tests exist for this assertion

ap)

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

Coverage

No tests exist for this assertion

apa)

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

Coverage

No tests exist for this assertion

aq)

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

Coverage

No tests exist for this assertion

aqa)

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

Coverage

No tests exist for this assertion

ar)

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

Coverage

No tests exist for this assertion

ara)

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

Coverage

No tests exist for this assertion

Suppose a class X is extended directly or indirectly by the bean class of a managed 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.

be)

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

Coverage

No tests exist for this assertion

bea)

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

Coverage

No tests exist for this assertion

bh)

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

Coverage

No tests exist for this assertion

bha)

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

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 18.13 - Inheritance of member-level metadata in Jakarta EE [member_level_inheritance_ee]

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

ab)

Check session bean X directly extends session bean Y

Coverage

No tests exist for this assertion

ad)

Check session bean X indirectly extends session bean Y

Coverage

No tests exist for this assertion

Suppose a class X is extended directly or indirectly by the bean class of a managed 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().

bab)

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

Coverage

No tests exist for this assertion

bad)

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

Coverage

No tests exist for this assertion

bbb)

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

Coverage

No tests exist for this assertion

bbd)

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

Coverage

No tests exist for this assertion

df)

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

Coverage

No tests exist for this assertion

dl)

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

Coverage

No tests exist for this assertion

dn)

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

Coverage

No tests exist for this assertion

dp)

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

Coverage

No tests exist for this assertion

Suppose a class X is extended directly or indirectly by the bean class of a managed bean. 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().

kb)

Check session bean X directly extends managed bean Y

Coverage

No tests exist for this assertion

kd)

Check session bean X indirectly extends managed bean Y

Coverage

No tests exist for this assertion

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().

dd)

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

Coverage

No tests exist for this assertion

de)

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

Coverage

No tests exist for this assertion

dj)

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

Coverage

No tests exist for this assertion

dk)

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

Coverage

No tests exist for this assertion

#### Section 18.14.1 - Direct and indirect specialization in Jakarta EE [direct_and_indirect_specialization_ee]

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

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

Coverage

No tests exist for this assertion

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

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

Coverage

No tests exist for this assertion

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

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

Coverage

No tests exist for this assertion

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.

lc)

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

Coverage

No tests exist for this assertion

#### Section 19.1 - Modularity in Jakarta EE [selection_ee]

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.

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

Check an enabled session bean can be injected

Coverage

No tests exist for this assertion

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

Check a disabled session bean is not injectable

Coverage

No tests exist for this assertion

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

Check a specialized session bean is not injectable

Coverage

No tests exist for this assertion

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

Check a selected alternative being session bean is injected

Coverage

No tests exist for this assertion

#### Section 19.1.1 - Declaring selected alternatives for an application in Jakarta EE [declaring_selected_alternatives_application_ee]

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

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

Coverage

No tests exist for this assertion

An alternative may be given a priority for the application by placing the @Priority annotation on the bean class of a session bean.

ab)

Test @Priority on the bean class of a session bean.

Coverage

No tests exist for this assertion

#### Section 19.1.2 - Declaring selected alternatives for a bean archive in Jakarta EE [declaring_selected_alternatives_bean_archive_ee]

a)

An alternative may be explicitly declared using the <alternatives> element of the beans.xml file of the bean archive. The <alternative> element contains a list of bean classes and stereotypes.

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

bb)

Test selected session bean.

Coverage

No tests exist for this assertion

#### Section 19.1.3 - Unsatisfied and ambiguous dependencies in Jakarta EE [unsatisfied_and_ambig_dependencies_ee]

The container must validate all injection points of all enabled beans, all observer methods, all disposer methods and all other Jakarta 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.

ad)

Test unsatisfied dependency for Jakarta EE component.

Coverage

No tests exist for this assertion

ah)

Test ambiguous dependency for Jakarta EE component.

Coverage

No tests exist for this assertion

#### Section 19.2 - EL name resolution [name_resolution_ee]

a)

An EL name resolves to a bean if the name can be resolved to a bean according to rules in 5.3, "Name resolution", and the bean is available for injection in the war containing the JSP or JSF page with the EL expression.

Coverage

No tests exist for this assertion

#### Section 19.3 - Dependency injection in Jakarta EE [injection_ee]

a)

The container is required to perform dependency injection whenever it creates a contextual instance of a session bean.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

The container is required to perform dependency injection whenever it instantiates instances of any other Jakarta EE component class supporting injection.

ea)

Test injection into a servlet listener

Coverage

No tests exist for this assertion

eb)

Test injection into a tag handler

Coverage

No tests exist for this assertion

ec)

Test injection into a tag library listener

Coverage

No tests exist for this assertion

ed)

Test injection into an EJB Interceptor

Coverage

No tests exist for this assertion

ee)

Test injection into a WS endpoint

Coverage

No tests exist for this assertion

ef)

Test injection into a servlet

Coverage

No tests exist for this assertion

eg)

Test injection into a filter

Coverage

No tests exist for this assertion

f)

A Jakarta EE 5 container is not required to support injection for non-contextual objects.

#### Section 19.3.1 - Injection using the bean constructor in Jakarta EE [instantiation_ee]

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

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

Test an @Inject constructor is used on a session bean

Coverage

No tests exist for this assertion

When the container instantiates a 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.

ab)

Test session bean with a constructor annotated @Inject.

Coverage

No tests exist for this assertion

bb)

Test constructor with no parameters is used for a session bean

Coverage

No tests exist for this assertion

#### Section 19.3.2 - Injection of fields and initializer methods in Jakarta EE [fields_initializer_methods_ee]

When the container creates a new instance of session bean 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

No tests exist for this assertion

ab)

Test session bean initializer methods called

Coverage

No tests exist for this assertion

ae)

Test Servlet fields injected

Coverage

No tests exist for this assertion

af)

Test Servlet initializer methods called

Coverage

No tests exist for this assertion

ag)

Test Servlet Filter fields injected

Coverage

No tests exist for this assertion

ah)

Test Servlet Filter initializer methods called

Coverage

No tests exist for this assertion

ai)

Test Servlet Listener fields injected

Coverage

No tests exist for this assertion

aj)

Test Servlet Listener initializer methods called

Coverage

No tests exist for this assertion

ak)

Test non-contextual session bean fields injected

Coverage

No tests exist for this assertion

al)

Test non-contextual session bean initializer methods called

Coverage

No tests exist for this assertion

am)

Test tag handler fields injected

Coverage

No tests exist for this assertion

an)

Test tag handler initializer methods called

Coverage

No tests exist for this assertion

ao)

Test EJB interceptor fields injected

Coverage

No tests exist for this assertion

ap)

Test EJB interceptor initializer methods called

Coverage

No tests exist for this assertion

aq)

Test WS endpoint fields injected

Coverage

No tests exist for this assertion

ar)

Test WS endpoint bean initializer methods called

Coverage

No tests exist for this assertion

as)

Test tag handler listener fields injected

Coverage

No tests exist for this assertion

at)

Test tag handler listener initializer methods called

Coverage

No tests exist for this assertion

au)

Test JSF managed bean fields injected

Coverage

No tests exist for this assertion

av)

Test JSF managed bean initializer methods called

Coverage

No tests exist for this assertion

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 Jakarta 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 methods 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 Jakarta 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 Jakarta EE component environment resource dependencies have been injected.

ba)

Test session bean initializer methods called after injected field of X

Coverage

No tests exist for this assertion

bb)

Test session bean initializer methods called after injected field of superclass of X

Coverage

No tests exist for this assertion

bc)

Test session bean initializer methods called after EE resource injection of X

Coverage

No tests exist for this assertion

bd)

Test session bean initializer methods called after EE resource injection of superclass of X

Coverage

No tests exist for this assertion

be)

Test session bean @PostConstruct called after initializer of X

Coverage

No tests exist for this assertion

bf)

Test session bean @PostConstruct called after initializer of superclass of X

Coverage

No tests exist for this assertion

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

bm)

Servlet init() method called after initializer method

Coverage

No tests exist for this assertion

bn)

Servlet init() method called after injected fields

Coverage

No tests exist for this assertion

bo)

Servlet init() method called after Jakarta EE resource injection

Coverage

No tests exist for this assertion

bp)

Servlet Filter init() method called after initializer method

Coverage

No tests exist for this assertion

bq)

Servlet Filter init() method called after injected fields

Coverage

No tests exist for this assertion

br)

Servlet Filter init() method called after Jakarta EE resource injection

Coverage

No tests exist for this assertion

#### Section 19.3.3 - Destruction of dependent objects in Jakarta EE [dependent_objects_destruction_ee]

a)

When the container destroys an instance of a bean, the container destroys all dependent objects, as defined in Section 6.4.2, "Destruction of objects with scope @Dependent", after the @PreDestroy callback completes.

Coverage

No tests exist for this assertion

#### Section 19.3.4 - Bean metadata in Jakarta EE [bean_metadata_ee]

a)

Interceptor and decorator instances associated with Jakarta EE components that are not considered beans (as defined by this specification) cannot obtain information about the beans they intercept and decorate (as defined in Bean metadata) and thus null is injected into relevant injection points.

Coverage

No tests exist for this assertion

#### Section 20.1 - Dependent pseudo-scope in Jakarta EE [dependent_context_ee]

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

No tests exist for this assertion

#### Section 20.1.2 - Destruction of objects with scope @Dependent in Jakarta EE [dependent_destruction_ee]

The container must ensure that all dependent objects of a non-contextual instance of a bean or other Jakarta EE component class are destroyed when the instance is destroyed by the container.

aaab)

Test with a Jakarta EE component.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 20.1.3 - Dependent pseudo-scope and Unified EL [dependent_scope_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

No tests exist for this assertion

b)

Portable extensions that integrate with the container via Unified EL should also ensure that these rules are enforced.

#### Section 20.2.1 - Passivation capable beans in Jakarta EE [passivation_capable_ee]

As defined by the EJB specification, a stateful session bean is passivation capable if interceptors and decorators of the bean are passivation capable, and the stateful session bean does not have the passivationCapable flag set to false.

aa)

Test a passivation capable stateful session bean with passivationCapable flag set to true.

Coverage

No tests exist for this assertion

ab)

Test a stateful session bean with passivationCapable flag set to false.

Coverage

No tests exist for this assertion

i)

As defined by the EJB specification, a stateless session bean or a singleton session bean is not passivation capable.

#### Section 20.2.2 - Passivation capable dependencies in java EE [passivation_capable_dependency_ee]

aa)

The container must guarantee that all stateless session beans are passivation capable dependencies.

Coverage

No tests exist for this assertion

ab)

The container must guarantee that all singleton session beans are passivation capable dependencies.

Coverage

No tests exist for this assertion

ac)

The container must guarantee that all passivation capable stateful session beans are passivation capable dependencies.

Coverage

No tests exist for this assertion

The container must guarantee that all resources are passivation capable dependencies.

da)

Test resource for a Jakarta EE resource.

Coverage

No tests exist for this assertion

db)

Test resource for a persistence unit.

Coverage

No tests exist for this assertion

dc)

Test resource for a persistence context.

Coverage

No tests exist for this assertion

dd)

Test resource for a remote EJB.

Coverage

No tests exist for this assertion

de)

Test resource for a web service.

Coverage

No tests exist for this assertion

#### Section 20.2.3 - Validation of passivation capable beans and dependencies in Jakarta EE [passivation_validation_ee]

If a stateful session bean which declares a passivating scope, or a built-in bean is not passivation capable then the container automatically detects the problem and treats it as a deployment problem.

aa)

Test non-transient injected field.

Coverage

No tests exist for this assertion

b)

Test stateful session bean.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

bdd)

Test a decorator with an injected field.

Coverage

No tests exist for this assertion

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.

hb)

Test a stateful session bean with decorator which is not a passivation capable dependency.

Coverage

No tests exist for this assertion

hd)

Test a stateful session bean with interceptor which is not a passivation capable dependency.

Coverage

No tests exist for this assertion

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

Stateful session bean which does not declare a passivating scope needn't be passivation capable.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

fbb)

Test for a runtime exception with a producer field.

Coverage

No tests exist for this assertion

#### Section 20.3 - Context management for built-in scopes in Jakarta EE [builtin_contexts_ee]

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 20.3.1 - Request context lifecycle in Jakarta EE [request_context_ee]

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

No tests exist for this assertion

ab)

Check doFilter() method.

Coverage

No tests exist for this assertion

ac)

Check ServletRequestListener.

Coverage

No tests exist for this assertion

ad)

Check AsyncListener.

Coverage

No tests exist for this assertion

b)

The request scope is active during any Jakarta EE web service invocation.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

gb)

Test the request scope is active during any asynchronous method invocation of any EJB.

Coverage

No tests exist for this assertion

gc)

Test the request scope is active during any call to an EJB timeout method.

Coverage

No tests exist for this assertion

gd)

Test the request scope is active during message delivery to any EJB message-driven bean.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

bb)

Check doFilter() methods.

Coverage

No tests exist for this assertion

bc)

Check requestDestroyed() notification.

Coverage

No tests exist for this assertion

bd)

Check onComplete() notification.

Coverage

No tests exist for this assertion

d)

The request context is destroyed after the web service invocation completes.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

hb)

Test the request context is destroyed after an EJB asynchronous method invocation.

Coverage

No tests exist for this assertion

hc)

Test the request context is destroyed after the EJB timeout.

Coverage

No tests exist for this assertion

hd)

Test the request context is destroyed after the message delivery completes.

Coverage

No tests exist for this assertion

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 ServletRequest if the context is initialized or destroyed due to a servlet request.

Coverage

No tests exist for this assertion

jb)

The event payload is the ServletRequest if the context is initialized or destroyed due to a web service invocation.

Coverage

No tests exist for this assertion

jc)

The event payload is the java.lang.Object if the context is initialized or destroyed due to a EJB remote method invocation.

Coverage

No tests exist for this assertion

jd)

The event payload is the java.lang.Object if the context is initialized or destroyed due to a EJB asynchronous method invocation.

Coverage

No tests exist for this assertion

je)

The event payload is the java.lang.Object if the context is initialized or destroyed due to a EJB timeout method invocation.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 20.3.2 - Session context lifecycle in Jakarta EE [session_context_ee]

aa)

The session scope is active during the service() method of any servlet in the web application.

Coverage

No tests exist for this assertion

ab)

The session scope is active during the doFilter() method of any servlet filter.

Coverage

No tests exist for this assertion

ac)

The session scope is active when the container calls any HttpSessionListener.

Coverage

No tests exist for this assertion

ad)

The session scope is active when the container calls any AsyncListener.

Coverage

No tests exist for this assertion

ae)

The session scope is active when the container calls any ServletRequestListener.

Coverage

No tests exist for this assertion

b)

The session context is shared between all servlet requests that occur in the same HTTP servlet session.

Coverage

No tests exist for this assertion

ca)

The session context is destroyed at the very end of any request in which invalidate() was called, after all filters and ServletRequestListeners have been called.

Coverage

No tests exist for this assertion

cb)

The session context is destroyed when the HTTPSession times out, after all HttpSessionListeners have been called.

Coverage

No tests exist for this assertion

da)

An event with the HttpSession as payload and with qualifier @Initialized(SessionScoped.class) is synchronously fired when the session context is initialized.

Coverage

No tests exist for this assertion

db)

An event with the HttpSession as payload and with qualifier @BeforeDestroyed(SessionScoped.class) is synchronously fired when the session context is about to be destroyed, i.e. before the actual destruction.

Coverage

No tests exist for this assertion

dc)

An event with the HttpSession as payload and with qualifier @Destroyed(SessionScoped.class) is synchronously fired when the session context is destroyed.

Coverage

No tests exist for this assertion

#### Section 20.3.3 - Application context lifecycle in Jakarta EE [application_context_ee]

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

No tests exist for this assertion

ab)

Check filter.

Coverage

No tests exist for this assertion

ac)

Check ServletContextListener.

Coverage

No tests exist for this assertion

ad)

Check HttpSessionListener

Coverage

No tests exist for this assertion

ae)

Check AsyncListener

Coverage

No tests exist for this assertion

af)

Check ServletRequestListener

Coverage

No tests exist for this assertion

b)

The application scope is active during any Jakarta EE web service invocation.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

db)

Test asynchronous method invocation

Coverage

No tests exist for this assertion

dc)

Test EJB timeout method

Coverage

No tests exist for this assertion

dd)

Test message delivery to any EJB message-driven bean.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

dh)

Test @PreDestroy method

Coverage

No tests exist for this assertion

h)

The application scope is active during @PostConstruct callback of any bean.

Coverage

No tests exist for this assertion

e)

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

No tests exist for this assertion

f)

The application context is destroyed when the application is shut down.

Coverage

No tests exist for this assertion

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 ServletContext if the application is a web application deployed to a Servlet container.

Coverage

No tests exist for this assertion

gb)

the java.lang.Object for other types of application.

#### Section 20.3.4 - Conversation context lifecycle in Jakarta EE [conversation_context_ee]

The conversation scope is active during all Servlet requests.

a)

Test JSF request.

Coverage

No tests exist for this assertion

aa)

Test non-JSF servlet request.

Coverage

No tests exist for this assertion

An event with qualifier @Initialized(ConversationContext.class) is fired when the conversation context is initialized. An event with qualifier @BeforeDestroyed(ConversationScoped.class) is synchronously fired when the conversation is about to be destroyed, i.e. before the actual destruction.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 ServletRequest as the payload and with qualifier @Initialized(ConversationContext.class) is synchronously fired when the conversation context is initialized.

Coverage

No tests exist for this assertion

bb)

An event with the ServletRequest as the payload and with qualifier @BeforeDestroyed(ConversationScoped.class) is synchronously fired when the conversation is about to be destroyed

Coverage

No tests exist for this assertion

bc)

An event with the ServletRequest as the payload and with qualifier @Destroyed(ConversationContext.class) is synchronously fired when the conversation context is destroyed.

Coverage

No tests exist for this assertion

bd)

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

No tests exist for this assertion

c)

Any Servlet request has exactly one associated conversation.

d)

The container provides a filter with the name "CDI Conversation Filter", which may be mapped in web.xml, allowing the user alter when the conversation is associated with the servlet request.

Coverage

No tests exist for this assertion

If this filter is not mapped in any web.xml in the application, 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)

Test service() method of a servlet.

Coverage

No tests exist for this assertion

db)

Test doFilter() method of a servlet filter.

Coverage

No tests exist for this assertion

dc)

Test ServletRequestListener.

Coverage

No tests exist for this assertion

dd)

Test AsyncListener.

Coverage

No tests exist for this assertion

e)

By default, a conversation is transient.

Coverage

No tests exist for this assertion

f)

A transient conversation may be marked long-running by calling Conversation.begin()

Coverage

No tests exist for this assertion

g)

A long-running conversation may be marked transient by calling Conversation.end()

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

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

No tests exist for this assertion

oa)

Test request parameter named conversationPropagation.

Coverage

No tests exist for this assertion

p)

All long-running conversations are scoped to a particular HTTP servlet session and may not cross session boundaries.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

r)

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)

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 jakarta.enterprise.context.NonexistentConversationException.

Coverage

No tests exist for this assertion

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 jakarta.enterprise.context.BusyConversationException.

ua)

Test the container blocks the concurrent request.

Coverage

No tests exist for this assertion

#### Section 21.1 - Container invocations and interception in Jakarta EE [biz_method_ee]

ac)

When the application invokes a business method of a session bean via an EJB remote or local reference, the invocation is treated as a business method invocation.

Coverage

No tests exist for this assertion

ig)

Invocation of EJB timer service timeouts by the container are not business method invocations, but are intercepted by interceptors for EJB timeouts.

Coverage

No tests exist for this assertion

Invocations of message listener methods of message-driven beans during message delivery are business method invocations.

la)

Verify message listener methods are intercepted

Coverage

No tests exist for this assertion

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.

c)

Verify that a session bean's business methods are intercepted

Coverage

No tests exist for this assertion

d)

Verify that a session bean's business methods are decorated

Coverage

No tests exist for this assertion

f)

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

No tests exist for this assertion

i)

Verify that a non-contextual session bean's business methods are decorated

Coverage

No tests exist for this assertion

#### Section 21.1.1 - Lifecycle of EJB stateful session beans [stateful_lifecycle]

aa)

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

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 21.1.2 - Lifecycle of EJB stateless and singleton session beans [stateless_lifecycle]

a)

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

No tests exist for this assertion

c)

When the destroy() method is called, the container simply discards this internal reference.

Coverage

No tests exist for this assertion

#### Section 21.1.3 - Lifecycle of resources [resource_lifecycle]

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 Jakarta 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 Jakarta EE component environment resource

Coverage

No tests exist for this assertion

lb)

Check Entity Manager

Coverage

No tests exist for this assertion

lc)

Check Entity Manager Factory

Coverage

No tests exist for this assertion

ld)

Check Remote EJB instance

Coverage

No tests exist for this assertion

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 Jakarta EE component environment resource

Coverage

No tests exist for this assertion

mb)

Check injected Jakarta EE component environment resource is passivation capable

Coverage

No tests exist for this assertion

mc)

Check delegations to underlying Entity Manager

Coverage

No tests exist for this assertion

md)

Check injected Entity Manager is passivation capable

Coverage

No tests exist for this assertion

me)

Check delegations to Entity Manager Factory

Coverage

No tests exist for this assertion

mf)

Check injected Entity Manager Factory is passivation capable

Coverage

No tests exist for this assertion

mg)

Check delegations to underlying Remote EJB instance

Coverage

No tests exist for this assertion

mh)

Check injected Remote EJB instance is passivation capable

Coverage

No tests exist for this assertion

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 Jakarta EE component environment injection upon any non-static field that functions as a resource declaration, as defined by the Jakarta EE platform and Common Annotations for the Java platform specifications.

o)

Check @Resource injection

Coverage

No tests exist for this assertion

p)

The container is not required to perform Jakarta 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)

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 22 - Decorators in Jakarta EE [decorators_ee]

a)

When running in Jakarta EE, the container must extend the rules defined for managed beans in Decorators to EJB session beans.

Coverage

No tests exist for this assertion

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

A decorator may be enabled for the entire application by applying the @Priority annotation, along with a priority value, on the decorator class.

Coverage

No tests exist for this assertion

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

Decorators with the smaller priority values are called first.

Coverage

No tests exist for this assertion

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

A decorator may be explicitly enabled by listing its bean class under the <decorators> element of the beans.xml file of the bean archive.

Coverage

No tests exist for this assertion

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

A decorator is declared by annotating the bean class with the @jakarta.decorator.Decorator stereotype.

Coverage

No tests exist for this assertion

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

Decorators are called after interceptors.

Coverage

No tests exist for this assertion

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

The order of the decorator declarations determines the decorator ordering. Decorators which occur earlier in the list are called first.

Coverage

No tests exist for this assertion

#### Section 22.1 - Decorator beans in Jakarta EE [decorator_bean_ee]

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.

ab)

Test decorator of session bean is called .

Coverage

No tests exist for this assertion

aci)

Test injected HttpServletRequest

Coverage

No tests exist for this assertion

acj)

Test injected HttpSession

Coverage

No tests exist for this assertion

ack)

Test injected ServletContext

Coverage

No tests exist for this assertion

acl)

Test injected InjectionPoint

Coverage

No tests exist for this assertion

acm)

Test injected Principal

Coverage

No tests exist for this assertion

acn)

Test injected UserTransaction

Coverage

No tests exist for this assertion

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

The decorator class may be abstract.

Coverage

No tests exist for this assertion

e)

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

f)

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 23 - Interceptor bindings in Jakarta EE [interceptors_ee]

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

A stereotype may declare one interceptor bindings.

Coverage

No tests exist for this assertion

#### Section 23.1 - Interceptor resolution in Jakarta EE [interceptor_resolution_ee]

a)

For a custom implementation of the Interceptor interface defined in Section 11.1.2. "The Interceptor interface", the container also calls intercepts() to determine if the interceptor intercepts an EJB timeout method invocation.

Coverage

No tests exist for this assertion

#### Section 24.1 - Observer methods in EJB session beans [observer_methods_ee]

d)

An observer method may also be a non-abstract method of an EJB session bean class. It must be either a business method exposed by a local business interface of the EJB or a static method of the bean class.

Coverage

No tests exist for this assertion

#### Section 24.1.1 - Declaring an observer method in an EJB [observes_ee]

g)

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

Coverage

No tests exist for this assertion

#### Section 24.1.2 - Observer method invocation context in Jakarta EE [observer_method_invocation_context_ee]

a)

The transaction and security contexts for a business method exposed by a local business interface of an EJB session bean also depend upon the transaction attribute and @RunAs descriptor, if any.

Coverage

No tests exist for this assertion

b)

All kinds of observers are called in the same client security context as the invocation of Event.fire() or Event.fireAsync() or BeanManager.fireEvent().

Coverage

No tests exist for this assertion

#### Section 25.1.1 - The Interceptor interface in Jakarta EE [interceptor_ee]

a)

When Running in Jakarta EE, the container must extend the rules defined in Section 11.1.2 "The Interceptor interface" and must also ensure that PREPASSIVATE, POSTACTIVATE and AROUND_TIMEOUT InterceptorType values are linked to EJB lifecycle callback or timeout method.

Coverage

No tests exist for this assertion

#### Section 25.2 - InjectionTarget interface in Jakarta EE [injectiontarget_ee]

When running in Jakarta EE, the container must extend the rules defined for InjectionTarget in The Producer and InjectionTarget interfaces and must also ensure that:

a)

when inject() is called, The container performs Jakarta 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 Injection of fields and initializer methods in Jakarta EE.

Coverage

No tests exist for this assertion

b)

@PostConstruct callback is called according to the semantics required by the Jakarta EE platform specification.

Coverage

No tests exist for this assertion

c)

@PreDestroy callback is called according to the semantics required by the Jakarta EE platform specification.

Coverage

No tests exist for this assertion

#### Section 25.3.1 - Obtaining a reference to the CDI container in Jakarta EE [provider_ee]

d)

Jakarta EE components may obtain an instance of BeanManager from JNDI by looking up the name java:comp/BeanManager.

Coverage

No tests exist for this assertion

e)

When running in Jakarta EE, when initialize method of CDIProvider is called an UnsupportedOperationException is thrown.

Coverage

No tests exist for this assertion

#### Section 25.3.2 - Wrapping a Unified EL ExpressionFactory [bm_wrap_expressionfactory]

a)

The method BeanManager.wrapExpressionFactory() returns a wrapper jakarta.el.ExpressionFactory that delegates MethodExpression and ValueExpression creation to the given ExpressionFactory.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

#### Section 25.4 - Alternative metadata sources and EJB [alternative_metadata_sources_ee]

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.

kb)

Check that a getTypeClosure() is used to determine the bean types for a session bean. The type closure should be different from the original type specified in the class definition.

Coverage

No tests exist for this assertion

#### Section 25.5.1 - ProcessInjectionPoint event and EJB [process_injection_point_ee]

a)

When running in Jakarta EE, the container must also fire an event for every injection point of every Jakarta 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.

Coverage

No tests exist for this assertion

#### Section 25.5.2 - ProcessInjectionTarget event and EJB [process_injection_target_ee]

The container must fire an event for every bean, interceptor or decorator. The event object must be of type jakarta.enterprise.inject.spi.ProcessInjectionTarget<X>, where x is the managed bean class.

aab)

Test event is fired for a session bean

Coverage

No tests exist for this assertion

aaba)

Test event is fired for a message driven bean

Coverage

No tests exist for this assertion

aac)

Test event is fired for a servlet listener

Coverage

No tests exist for this assertion

aad)

Test event is fired for a tag handler

Coverage

No tests exist for this assertion

aae)

Test event is fired for a tag library listener

Coverage

No tests exist for this assertion

aaf)

Test event is fired for an EJB Interceptor

Coverage

No tests exist for this assertion

aag)

Test event is fired for a WS endpoint

Coverage

No tests exist for this assertion

aah)

Test event is fired for a servlet

Coverage

No tests exist for this assertion

aai)

Test event is fired for a filter

Coverage

No tests exist for this assertion

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

Test supertype for a servlet listener

Coverage

No tests exist for this assertion

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

Test supertype and subtype for a tag handler

Coverage

No tests exist for this assertion

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

Test supertype and subtype for a servlet

Coverage

No tests exist for this assertion

getAnnotatedType() returns the AnnotatedType representing the managed bean class.

abb)

Test type for a session bean

Coverage

No tests exist for this assertion

abba)

Test type for a message driven bean

Coverage

No tests exist for this assertion

abc)

Test type for a servlet listener

Coverage

No tests exist for this assertion

abd)

Test type for a tag handler

Coverage

No tests exist for this assertion

abe)

Test type for a tag library listener

Coverage

No tests exist for this assertion

abf)

Test type for an EJB Interceptor

Coverage

No tests exist for this assertion

abg)

Test type for a WS endpoint

Coverage

No tests exist for this assertion

abh)

Test type for a servlet

Coverage

No tests exist for this assertion

abi)

Test type for a filter

Coverage

No tests exist for this assertion

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 Jakarta EE component class supporting injection.

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

#### Section 25.5.3 - ProcessBeanAttributes event and EJB [process_bean_attributes_ee]

getAnnotated() returns the AnnotatedType representing the bean class or session bean class, the AnnotatedMethod representing the producer field, or the AnnotatedField representing the producer field.

bab)

Test session bean.

Coverage

No tests exist for this assertion

#### Section 25.5.4 - ProcessBean event and EJB [process_bean_ee]

ca)

For a session bean with bean class X, the container must raise an event of type ProcessSessionBean<X>.

Coverage

No tests exist for this assertion

cb)

Test ProcessSessionBean is fired after ProcessBeanAttributes.

Coverage

No tests exist for this assertion

The interface jakarta.enterprise.inject.spi.ProcessBean is a supertype of all these event types.

edb)

Test ProcessSessionBean

Coverage

No tests exist for this assertion

getAnnotated() returns the AnnotatedType representing the bean class, the AnnotatedMethod representing the producer method, or the AnnotatedField representing the producer field.

efb)

Test ProcessSessionBean

Coverage

No tests exist for this assertion

getBean() returns the Bean object that is about to be registered. The Bean may implement Interceptor or Decorator.

fb)

Test ProcessSessionBean

Coverage

No tests exist for this assertion

hb)

getEjbName() returns the EJB name of the session bean.

Coverage

No tests exist for this assertion

hc)

getSessionBeanType() returns a jakarta.enterprise.inject.spi.SessionBeanType representing the kind of session bean.

Coverage

No tests exist for this assertion

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

Check the getAnnotatedSessionBeanClass()

Coverage

No tests exist for this assertion

Check the getAnnotatedBeanClass()

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

Check for session bean

Coverage

No tests exist for this assertion

#### Section 26.1 - Bean archive with EJB Session Beans [bean_archive_ee]

When determining which archives are bean archives, the container must consider:

da)

Library jars, EJB jars or application client jars.

db)

The WEB-INF/classes directory of a war.

dc)

Directories in the JVM classpath.

e)

A Jakarta EE container is required by the Jakarta EE specification to support Jakarta EE modules. Other containers may or may not provide support for war, EJB jar or rar bean archives.

The beans.xml file must be named:

fb)

In a war, WEB-INF/beans.xml or WEB-INF/classes/META-INF/beans.xml

Coverage

No tests exist for this assertion

g)

If a war has a file named beans.xml in both the WEB-INF directory and in the WEB-INF/classes/META-INF directory, then non-portable behavior results. Portable applications must have a beans.xml file in only one of the WEB-INF or the WEB-INF/classes/META-INF directories.

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, EJB jars and rars contained in the ear. The bean archives might be library jars, EJB jars or war WEB-INF/classes directories.

ja)

Test an EJB jar in an EAR.

Coverage

No tests exist for this assertion

jb)

Test a bundled library in an EAR.

Coverage

No tests exist for this assertion

jc)

Test a bundled library in a WAR.

Coverage

No tests exist for this assertion

jd)

Test a rar in an EAR.

Coverage

No tests exist for this assertion

je)

Test a war in an EAR.

Coverage

No tests exist for this assertion

jf)

Test an installed library.

Coverage

No tests exist for this assertion

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.

jg)

Test WEB-INF/classes directory.

Coverage

No tests exist for this assertion

jh)

Test bundled library.

Coverage

No tests exist for this assertion

ji)

Test an installed library.

Coverage

No tests exist for this assertion

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.

jj)

Test classes in the EJB jar.

Coverage

No tests exist for this assertion

jk)

In an application deployed as a rar, the container searches every bean archive bundled with or referenced by the rar.

Coverage

No tests exist for this assertion

jl)

An embeddable EJB container searches each bean archive in the JVM classpath that is listed in the value of the embeddable container initialization property jakarta.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.

Coverage

No tests exist for this assertion

An explicit bean archive is an archive which contains a beans.xml file with a version number of 1.1 (or later), with the bean-discovery-mode of all, or with no version number, or that is an empty file.

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

Test an archive which contains a beans.xml file with a version number of 1.1, with the bean-discovery-mode of all.

Coverage

No tests exist for this assertion

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

Test an archive which contains a beans.xml file with no version number.

Coverage

No tests exist for this assertion

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

Test an archive which contains an empty beans.xml.

Coverage

No tests exist for this assertion

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

An archive which contains a beans.xml file with the bean-discovery-mode of none is not a bean archive.

Coverage

No tests exist for this assertion

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

An archive which contains an extension and no beans.xml file is not a bean archive.

Coverage

No tests exist for this assertion

#### Section 26.2 - Type and Bean discovery for EJB [type_bean_discovery_ee]

For every type discovered the container must create an AnnotatedType representing the type and fire an event of type ProcessAnnotatedType, as defined in Section 11.5.6.

bb)

Check session bean

Coverage

No tests exist for this assertion

bd)

Check JSF managed beans

Coverage

No tests exist for this assertion

be)

Check servlet listener

Coverage

No tests exist for this assertion

bf)

Check tag handler

Coverage

No tests exist for this assertion

bg)

Check tag library listener

Coverage

No tests exist for this assertion

bh)

Check EJB Interceptor

Coverage

No tests exist for this assertion

bi)

Check WS endpoint

Coverage

No tests exist for this assertion

bj)

Check servlet

Coverage

No tests exist for this assertion

bk)

Check filter

Coverage

No tests exist for this assertion

#### Section 26.2.1 - Bean discovery in Jakarta EE [bean_discovery_steps_ee]

tc)

The container discovers each session bean.

Coverage

No tests exist for this assertion

For every type in the set of discovered types (as defined in Type discovery), the container must fire an event of type ProcessInjectionTarget, as defined in ProcessInjectionTarget event,

bb)

Check session bean

Coverage

No tests exist for this assertion

bd)

Check JSF managed beans

Coverage

No tests exist for this assertion

be)

Check servlet listener

Coverage

No tests exist for this assertion

bf)

Check tag handler

Coverage

No tests exist for this assertion

bg)

Check tag library listener

Coverage

No tests exist for this assertion

bh)

Check EJB Interceptor

Coverage

No tests exist for this assertion

bi)

Check WS endpoint

Coverage

No tests exist for this assertion

bj)

Check servlet

Coverage

No tests exist for this assertion

bk)

Check filter

Coverage

No tests exist for this assertion

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", and fire an event which is a subtype of ProcessBean, as defined in Section 11.5.8, "ProcessBean event".

fb)

Check a session bean

Coverage

No tests exist for this assertion

#### Section 26.2.2 - Trimmed bean archive in Jakarta EE [trimmed_bean_archive_ee]

a)

When running in Jakarta EE, the container must extend the rules defined in "Trimmed bean archive" and must ensure that EJB session beans are not removed from the set of discovered types.

Coverage

No tests exist for this assertion

#### Section 26.3 - Integration with Unified EL [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, "Name resolution" and resolving ambiguities according to Section 5.3.1, "Ambiguous names".

Coverage

No tests exist for this assertion

c)

If a name used in an EL expression does not resolve to any bean, the ELResolver must return a null value.

Coverage

No tests exist for this assertion

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

No tests exist for this assertion

### Unversioned tests

The following 268 test classes either do not have a version specified, or the version is unrecognized:

Test Class | Version
--- | ---
org.jboss.cdi.tck.tests.implementation.disposal.method.definition.inheritance.ejb.DisposerMethodInheritanceTest | 2.0
org.jboss.cdi.tck.tests.definition.bean.broken.restricted.ejb.RestrictedSessionBeanTest | 2.0
org.jboss.cdi.tck.tests.implementation.simple.resource.persistenceContext.staticProducer.PersistenceInjectionStaticProducerFieldTest | 2.0
org.jboss.cdi.tck.tests.decorators.ordering.global.EnterpriseDecoratorOrderingTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.SelectedAlternativeManagedBeanInjectionAvailability02Test | 2.0
org.jboss.cdi.tck.tests.deployment.shutdown.ApplicationShutdownLifecycleTest | 2.0
org.jboss.cdi.tck.tests.deployment.discovery.enterprise.EnterpriseBeanDiscoveryTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.specialization.SpecializationModularity03Test | 2.0
org.jboss.cdi.tck.tests.event.observer.transactional.TransactionalObserverTest | 2.0
org.jboss.cdi.tck.tests.inheritance.specialization.enterprise.broken.extend.managedbean.DirectlyExtendsSimpleBeanTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.EnabledManagedBeanInjectionAvailability02Test | 2.0
org.jboss.cdi.tck.tests.lookup.modules.EnabledManagedBeanInjectionAvailabilityTest | 2.0
org.jboss.cdi.tck.tests.event.broken.observer.notBusinessMethod.EJBObserverMethodNotBusinessMethodTest | 2.0
org.jboss.cdi.tck.tests.lookup.injectionpoint.non.contextual.NonContextualInjectionPointTest | 2.0
org.jboss.cdi.tck.tests.lookup.el.integration.IntegrationWithUnifiedELTest | 2.0
org.jboss.cdi.tck.tests.inheritance.specialization.enterprise.broken.extend.sessionbean.SessionBeanSpecializingSessionBeanWithClientViewTest | 2.0
org.jboss.cdi.tck.tests.lookup.injection.enterprise.chain.SessionBeanInjectionChainTest | 2.0
org.jboss.cdi.tck.tests.implementation.disposal.method.definition.broken.observes.async.DisposerMethodWithAsyncObservesTest | 2.0
org.jboss.cdi.tck.tests.deployment.packaging.rar.ResourceAdapterArchiveTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.specialization.SpecializationModularity07Test | 2.0
org.jboss.cdi.tck.tests.lookup.manager.jndi.ManagerTest | 2.0
org.jboss.cdi.tck.tests.interceptors.definition.broken.finalClassInterceptor.ee.FinalClassMethodLevelInterceptorTest | 2.0
org.jboss.cdi.tck.tests.implementation.enterprise.lifecycle.EnterpriseBeanLifecycleTest | 2.0
org.jboss.cdi.tck.tests.decorators.builtin.http.servletcontext.BuiltinServletContextDecoratorTest | 2.0
org.jboss.cdi.tck.tests.deployment.packaging.visibility.VisibilityOfAnnotatedTypesFromExtensionInAlphaBeanArchiveTest | 2.0
org.jboss.cdi.tck.tests.event.observer.context.enterprise.staticMethod.SessionBeanStaticObserverMethodInvocationContextTest | 2.0
org.jboss.cdi.tck.tests.interceptors.ordering.global.EnterpriseInterceptorOrderingTest | 2.0
org.jboss.cdi.tck.tests.inheritance.specialization.enterprise.broken.extend.nothing.DirectlyExtendsNothingTest | 2.0
org.jboss.cdi.tck.tests.implementation.simple.resource.env.staticProducer.EnvInjectionStaticProducerFieldTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.InterModuleLookupTest | 2.0
org.jboss.cdi.tck.tests.decorators.builtin.http.request.BuiltinHttpServletRequestDecoratorTest | 2.0
org.jboss.cdi.tck.tests.deployment.packaging.visibility.VisibilityOfBeanInWebModuleFromBeanManagerInBeanLibraryTest | 2.0
org.jboss.cdi.tck.tests.implementation.disposal.method.definition.broken.enterprise.remoteMethod.RemoteBusinessDisposalMethodTest | 2.0
org.jboss.cdi.tck.tests.inheritance.specialization.producer.method.enterprise.EnterpriseProducerMethodSpecializationTest | 2.0
org.jboss.cdi.tck.tests.definition.qualifier.enterprise.EnterpriseQualifierDefinitionTest | 2.0
org.jboss.cdi.tck.tests.implementation.producer.method.broken.enterprise.remoteMethod.RemoteBusinessProducerMethodTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.EnabledProducerFieldInjectionAvailability02Test | 2.0
org.jboss.cdi.tck.tests.context.session.listener.SessionContextServletRequestListenerTest | 2.0
org.jboss.cdi.tck.tests.context.request.postconstruct.EagerSingletonPostConstructCallbackTest | 2.0
org.jboss.cdi.tck.tests.deployment.discovery.enterprise.annotated.EnterpriseDefaultBeanDiscoveryModeTest | 2.0
org.jboss.cdi.tck.tests.deployment.packaging.ear.SingleWebModuleWithExtensionTest | 2.0
org.jboss.cdi.tck.tests.context.request.event.RequestScopeEventTest | 2.0
org.jboss.cdi.tck.tests.deployment.packaging.visibility.JarToJarAlphaVisibilityTest | 2.0
org.jboss.cdi.tck.tests.lookup.injection.non.contextual.broken.unsatisfied.UnsatisfiedInjectionIntoNonContextualComponentTest | 2.0
org.jboss.cdi.tck.tests.extensions.lifecycle.events.ejb.ContainerLifeCycleEventRuntimeInvocationTest | 2.0
org.jboss.cdi.tck.tests.event.observer.context.async.AsyncObserverMethodInvocationContextTest | 2.0
org.jboss.cdi.tck.tests.extensions.producer.remote.RemoteProducerTest | 2.0
org.jboss.cdi.tck.tests.lookup.injection.InjectionTest | 2.0
org.jboss.cdi.tck.tests.decorators.ordering.global.GlobalDecoratorOrderingTest | 2.0
org.jboss.cdi.tck.tests.context.request.RequestContextTest | 2.0
org.jboss.cdi.tck.tests.context.request.jaxrs.RequestContextTest | 2.0
org.jboss.cdi.tck.tests.context.application.disposer.ApplicationContextDisposerTest | 2.0
org.jboss.cdi.tck.tests.deployment.packaging.ear.MultiWebModuleWithExtensionTest | 2.0
org.jboss.cdi.tck.tests.alternative.selection.resource.ResourceAlternative04Test | 2.0
org.jboss.cdi.tck.tests.alternative.enterprise.SessionBeanAlternativeTest | 2.0
org.jboss.cdi.tck.tests.alternative.selection.enterprise.EnterpriseSelectedAlternative03Test | 2.0
org.jboss.cdi.tck.tests.implementation.simple.resource.broken.type.persistence.unit.ResourceDefinitionWithDifferentTypeTest | 2.0
org.jboss.cdi.tck.tests.interceptors.definition.enterprise.nonContextualReference.SessionBeanInterceptorOnNonContextualEjbReferenceTest | 2.0
org.jboss.cdi.tck.tests.implementation.initializer.ejb.EjbInitializerMethodTest | 2.0
org.jboss.cdi.tck.tests.context.passivating.broken.producer.field.enterprise.EnterpriseBeanWithIllegalDependencyTest | 2.0
org.jboss.cdi.tck.tests.implementation.enterprise.remove.EnterpriseBeanRemoveMethodTest | 2.0
org.jboss.cdi.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest | 2.0
org.jboss.cdi.tck.tests.implementation.simple.definition.ee.EnterpriseBeanNotDiscoveredAsManagedBeanTest | 2.0
org.jboss.cdi.tck.tests.event.broken.observer.remoteBusinessMethod.EJBAsyncObserverMethodRemoteBusinessMethodTest | 2.0
org.jboss.cdi.tck.tests.context.passivating.broken.enterprise.field.UnserializableSimpleInjectedIntoPassivatingEnterpriseBeanTest | 2.0
org.jboss.cdi.tck.tests.deployment.discovery.implicit.DefaultBeanDiscoveryModeTest | 2.0
org.jboss.cdi.tck.tests.alternative.enterprise.resource.ResourceAlternativeAvailabilityTest | 2.0
org.jboss.cdi.tck.tests.context.passivating.enterprise.NonPassivationCapableSessionBeanTest | 2.0
org.jboss.cdi.tck.tests.inheritance.specialization.enterprise.broken.name.SameNameTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.SelectedAlternativeSessionBeanInjectionAvailability02Test | 2.0
org.jboss.cdi.tck.tests.implementation.enterprise.definition.remote.RemoteInterfaceNotInAPITypesTest | 2.0
org.jboss.cdi.tck.tests.implementation.simple.resource.resource.InjectionOfResourceTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.InterModuleLookup02Test | 2.0
org.jboss.cdi.tck.tests.implementation.producer.field.definition.enterprise.EnterpriseProducerFieldDefinitionTest | 2.0
org.jboss.cdi.tck.tests.extensions.registration.VisibilityOfBeanRegisteredByExtensionFromNonBeanLibraryTest | 2.0
org.jboss.cdi.tck.tests.context.conversation.servlet.ServletConversationTest | 2.0
org.jboss.cdi.tck.tests.context.conversation.filter.ConversationFilterTest | 2.0
org.jboss.cdi.tck.tests.interceptors.definition.broken.finalClassInterceptor.ee.FinalMethodClassLevelInterceptorTest | 2.0
org.jboss.cdi.tck.tests.lookup.injection.enterprise.SessionBeanInjectionOrderingTest | 2.0
org.jboss.cdi.tck.tests.event.observer.resolve.enterprise.ResolveEnterpriseEventObserverTest | 2.0
org.jboss.cdi.tck.tests.deployment.packaging.war.BeansDescriptorAlternativeLocationTest | 2.0
org.jboss.cdi.tck.tests.definition.scope.broken.tooManyScopes.ejb.producer.method.SessionBeanProducerMethodTooManyScopesTest | 2.0
org.jboss.cdi.tck.tests.event.observer.priority.transactional.TransactionalPriorityObserverTest | 2.0
org.jboss.cdi.tck.tests.implementation.enterprise.broken.singletonWithConversationScope.SingletonWithConversationScopeTest | 2.0
org.jboss.cdi.tck.tests.context.conversation.event.LongRunningConversationLifecycleEventTest | 2.0
org.jboss.cdi.tck.tests.context.passivating.broken.interceptor.enterprise.EnterpriseBeanWithNonPassivatingInterceptorTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.specialization.alternative.Specialization04Test | 2.0
org.jboss.cdi.tck.tests.context.conversation.LongRunningConversationPropagatedByFacesContextTest | 2.0
org.jboss.cdi.tck.tests.context.application.async.ApplicationContextAsyncListenerTest | 2.0
org.jboss.cdi.tck.tests.context.passivating.dependency.sessionbean.SessionBeanPassivationDependencyTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.specialization.SpecializationModularity06Test | 2.0
org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes.builtin.ProcessBeanAttributesNotFiredForBuiltinBean | 2.0
org.jboss.cdi.tck.tests.implementation.producer.method.definition.enterprise.EnterpriseProducerMethodDefinitionTest | 2.0
org.jboss.cdi.tck.tests.implementation.enterprise.broken.singletonWithRequestScope.SingletonWithRequestScopeTest | 2.0
org.jboss.cdi.tck.tests.vetoed.enterprise.EnterpriseVetoedTest | 2.0
org.jboss.cdi.tck.tests.definition.bean.types.enterprise.SessionBeanTypesTest | 2.0
org.jboss.cdi.tck.tests.context.session.event.SessionScopeEventTest | 2.0
org.jboss.cdi.tck.tests.implementation.simple.resource.ejb.EjbInjectionTest | 2.0
org.jboss.cdi.tck.tests.context.application.predestroy.ApplicationContextPreDestroyTest | 2.0
org.jboss.cdi.tck.tests.implementation.enterprise.broken.statelessWithApplicationScope.StatelessWithApplicationScopeTest | 2.0
org.jboss.cdi.tck.tests.context.application.event.ApplicationScopeEventMultiWarTest | 2.0
org.jboss.cdi.tck.tests.context.passivating.broken.enterprise.NonPassivationCapableEjbWithPassivatingScopeTest | 2.0
org.jboss.cdi.tck.tests.context.passivating.enterprise.invalid.StatefulSessionBeanTest | 2.0
org.jboss.cdi.tck.tests.decorators.builtin.transaction.BuiltinUserTransactionDecoratorTest | 2.0
org.jboss.cdi.tck.tests.implementation.producer.method.broken.enterprise.nonbusiness.ProducerMethodNotBusinessMethodTest | 2.0
org.jboss.cdi.tck.tests.context.passivating.dependency.resource.remote.ResourcePassivationDependencyTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.broken.DisabledProducerMethodInjectionNotAvailableTest | 2.0
org.jboss.cdi.tck.tests.context.request.event.timeout.RequestScopeEventTimeoutTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.specialization.alternative.Specialization03Test | 2.0
org.jboss.cdi.tck.tests.implementation.simple.resource.broken.name.ResourceDefinitionWithNameTest | 2.0
org.jboss.cdi.tck.tests.implementation.simple.resource.resource.staticProducer.InjectionOfResourceStaticProducerFieldTest | 2.0
org.jboss.cdi.tck.tests.context.session.listener.SessionContextHttpSessionListenerTest | 2.0
org.jboss.cdi.tck.tests.implementation.enterprise.broken.statelessInterceptor.InterceptorAnnotatedStatelessSessionBeanTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.specialization.SpecializationModularity02Test | 2.0
org.jboss.cdi.tck.tests.deployment.packaging.bundledLibrary.LibraryInWarTest | 2.0
org.jboss.cdi.tck.tests.context.activation.ActivateRequestContextinEETest | 2.0
org.jboss.cdi.tck.tests.context.passivating.broken.producer.method.enterprise.EnterpriseBeanWithIllegalDependencyTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.EnabledProducerMethodInjectionAvailabilityTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.InterModuleELResolutionTest | 2.0
org.jboss.cdi.tck.tests.lookup.injection.enterprise.SessionBeanInjectionTest | 2.0
org.jboss.cdi.tck.tests.deployment.packaging.ear.modules.EnterpriseArchiveModulesTest | 2.0
org.jboss.cdi.tck.tests.context.application.ApplicationContextTest | 2.0
org.jboss.cdi.tck.tests.deployment.packaging.installedLibrary.InstalledLibraryWarTest | 2.0
org.jboss.cdi.tck.tests.extensions.registration.TwoBeansOneClassTest | 2.0
org.jboss.cdi.tck.tests.definition.scope.enterprise.EnterpriseScopeDefinitionTest | 2.0
org.jboss.cdi.tck.tests.implementation.enterprise.broken.statelessWithConversationScope.StatelessWithConversationScopeTest | 2.0
org.jboss.cdi.tck.tests.implementation.enterprise.broken.statelessWithRequestScope.StatelessWithRequestScopeTest | 2.0
org.jboss.cdi.tck.tests.lookup.injection.non.contextual.ContainerEventTest | 2.0
org.jboss.cdi.tck.tests.context.conversation.event.notattached.DestroyConversationNotAssociatedWithCurrentRequestEventTest | 2.0
org.jboss.cdi.tck.tests.event.observer.transactional.custom.CustomTransactionalObserverTest | 2.0
org.jboss.cdi.tck.tests.context.passivating.dependency.resource.persistence.ResourcePassivationDependencyTest | 2.0
org.jboss.cdi.tck.tests.lookup.injection.persistence.PersistenceResourceInjectionTest | 2.0
org.jboss.cdi.tck.tests.implementation.simple.resource.broken.type.persistence.context.ResourceDefinitionWithDifferentTypeTest | 2.0
org.jboss.cdi.tck.tests.context.application.postconstruct.EagerSingletonPostConstructCallbackTest | 2.0
org.jboss.cdi.tck.tests.lookup.injection.non.contextual.InjectionIntoNonContextualComponentTest | 2.0
org.jboss.cdi.tck.tests.extensions.registration.BeanRegistrationByExtensionInWarLibraryTest | 2.0
org.jboss.cdi.tck.tests.deployment.packaging.bundledLibrary.LibraryMissingBeansXmlTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.specialization.SpecializationModularity05Test | 2.0
org.jboss.cdi.tck.tests.lookup.manager.provider.init.CDIProviderInitTest | 2.0
org.jboss.cdi.tck.tests.extensions.registration.BeanRegistrationByExtensionInNonBeanArchiveTest | 2.0
org.jboss.cdi.tck.tests.context.conversation.ManualCidPropagationTest | 2.0
org.jboss.cdi.tck.tests.context.application.postconstruct.SimpleBeanPostConstructCallbackTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.specialization.alternative.Specialization05Test | 2.0
org.jboss.cdi.tck.tests.implementation.simple.resource.broken.type.env.ResourceDefinitionWithDifferentTypeTest | 2.0
org.jboss.cdi.tck.tests.interceptors.definition.enterprise.jms.MessageDrivenBeanInterceptorInvocationTest | 2.0
org.jboss.cdi.tck.tests.definition.stereotype.interceptor.enterprise.EnterpriseStereotypeInterceptorBindingTest | 2.0
org.jboss.cdi.tck.tests.definition.scope.broken.tooManyScopes.ejb.SessionBeanTooManyScopesTest | 2.0
org.jboss.cdi.tck.tests.deployment.packaging.war.modules.WebArchiveModulesTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.specialization.alternative.Specialization02Test | 2.0
org.jboss.cdi.tck.tests.extensions.beanManager.beanAttributes.ejb.CreateBeanAttributesTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.SpecializedBeanInjectionNotAvailableTest | 2.0
org.jboss.cdi.tck.tests.implementation.enterprise.broken.genericStateless.GenericStatelessSessionBeanTest | 2.0
org.jboss.cdi.tck.tests.implementation.producer.field.definition.broken.enterprise.nonstatic.NonStaticFieldOfSessionBeanTest | 2.0
org.jboss.cdi.tck.tests.implementation.enterprise.broken.statelessDecorator.DecoratorAnnotatedStatelessSessionBeanTest | 2.0
org.jboss.cdi.tck.tests.event.observer.context.async.enterprise.EnterpriseSecurityContextPropagationInAsyncObserverTest | 2.0
org.jboss.cdi.tck.tests.lookup.injection.non.contextual.broken.ambiguous.AmbiguousInjectionIntoNonContextualComponentTest | 2.0
org.jboss.cdi.tck.tests.alternative.selection.enterprise.EnterpriseSelectedAlternative01Test | 2.0
org.jboss.cdi.tck.tests.lookup.clientProxy.incontainer.ClientProxyTest | 2.0
org.jboss.cdi.tck.tests.decorators.invocation.enterprise.EnterpriseDecoratorInvocationTest | 2.0
org.jboss.cdi.tck.tests.lookup.injection.non.contextual.CreationalContextForNonContextualTest | 2.0
org.jboss.cdi.tck.tests.context.conversation.ClientConversationContextTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.broken.DisabledProducerFieldInjectionNotAvailableTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.SpecializedProducerMethodInjectionNotAvailable02Test | 2.0
org.jboss.cdi.tck.tests.implementation.simple.resource.env.EnvInjectionTest | 2.0
org.jboss.cdi.tck.tests.context.session.SessionContextTest | 2.0
org.jboss.cdi.tck.tests.context.session.async.SessionContextAsyncListenerTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.SpecializedProducerMethodInjectionNotAvailableTest | 2.0
org.jboss.cdi.tck.tests.deployment.packaging.installedLibrary.InstalledLibraryEarTest | 2.0
org.jboss.cdi.tck.tests.definition.stereotype.enterprise.EnterpriseStereotypeDefinitionTest | 2.0
org.jboss.cdi.tck.tests.lookup.injectionpoint.broken.not.bean.InjectionPointTest | 2.0
org.jboss.cdi.tck.tests.context.request.event.jms.RequestScopeEventMessageDeliveryTest | 2.0
org.jboss.cdi.tck.tests.event.observer.inheritance.enterprise.EnterpriseObserverInheritanceTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.specialization.SpecializationModularity01Test | 2.0
org.jboss.cdi.tck.tests.event.broken.observer.remoteBusinessMethod.EJBObserverMethodRemoteBusinessMethodTest | 2.0
org.jboss.cdi.tck.tests.context.dependent.ejb.DependentContextEjbTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.specialization.SpecializationModularity04Test | 2.0
org.jboss.cdi.tck.tests.definition.stereotype.alternative.enterprise.EnterpriseStereotypeAlternativeTest | 2.0
org.jboss.cdi.tck.tests.interceptors.definition.inheritance_ee.InterceptorBindingInheritanceTest | 2.0
org.jboss.cdi.tck.tests.context.passivating.enterprise.valid.StatefulSessionBeanXmlDescriptorTest | 2.0
org.jboss.cdi.tck.tests.context.passivating.enterprise.invalid.StatefulSessionBeanXmlDescriptorTest | 2.0
org.jboss.cdi.tck.tests.context.request.async.RequestContextAsyncListenerTest | 2.0
org.jboss.cdi.tck.tests.implementation.disposal.method.definition.broken.enterprise.methodOnSessionBean.DisposalMethodOnSessionBeanTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.broken.DisabledSessionBeanInjectionNotAvailableTest | 2.0
org.jboss.cdi.tck.tests.definition.scope.broken.tooManyScopes.ejb.producer.field.SessionBeanProducerFieldTooManyScopesTest | 2.0
org.jboss.cdi.tck.tests.deployment.packaging.ejb.EJBJarDeploymentTest | 2.0
org.jboss.cdi.tck.tests.context.conversation.InvalidatingSessionDestroysConversationTest | 2.0
org.jboss.cdi.tck.tests.extensions.container.event.jms.ContainerEventTest | 2.0
org.jboss.cdi.tck.tests.interceptors.definition.lifecycle.enterprise.order.EnterpriseLifecycleInterceptorDefinitionTest | 2.0
org.jboss.cdi.tck.tests.deployment.packaging.bundledLibrary.LibraryInEarTest | 2.0
org.jboss.cdi.tck.tests.implementation.simple.resource.broken.type.ResourceDefinitionWithDifferentTypeTest | 2.0
org.jboss.cdi.tck.tests.alternative.selection.resource.ResourceAlternative01Test | 2.0
org.jboss.cdi.tck.tests.extensions.registration.BeanRegistrationByExtensionInEarLibraryTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.EnabledSessionBeanInjectionAvailabilityTest | 2.0
org.jboss.cdi.tck.tests.lookup.manager.provider.runtime.CDIProviderRuntimeTest | 2.0
org.jboss.cdi.tck.tests.decorators.builtin.principal.BuiltinPrincipalDecoratorTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.EnabledSessionBeanInjectionAvailability02Test | 2.0
org.jboss.cdi.tck.tests.lookup.clientProxy.integration.ClientProxyTest | 2.0
org.jboss.cdi.tck.tests.interceptors.definition.enterprise.simpleInterception.SessionBeanInterceptorDefinitionTest | 2.0
org.jboss.cdi.tck.tests.context.passivating.enterprise.valid.StatefulSessionBeanTest | 2.0
org.jboss.cdi.tck.tests.inheritance.specialization.enterprise.broken.twobeans.TwoBeansSpecializeTheSameBeanTest | 2.0
org.jboss.cdi.tck.tests.extensions.alternative.metadata.ejb.AlternativeMetadataTest | 2.0
org.jboss.cdi.tck.tests.decorators.invocation.ejb.EJBDecoratorInvocationTest | 2.0
org.jboss.cdi.tck.tests.implementation.builtin.broken.transaction.UserTransactionInvalidInjectionTest | 2.0
org.jboss.cdi.tck.tests.implementation.enterprise.definition.EnterpriseBeanViaXmlTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.interceptors.InterceptorModularityTest | 2.0
org.jboss.cdi.tck.tests.extensions.container.event.ContainerEventTest | 2.0
org.jboss.cdi.tck.tests.context.conversation.event.TransientConversationLifecycleEventTest | 2.0
org.jboss.cdi.tck.tests.interceptors.ordering.global.GlobalInterceptorOrderingTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.specialization.alternative.Specialization06Test | 2.0
org.jboss.cdi.tck.tests.inheritance.initializer.InitializerMethodInheritanceTest | 2.0
org.jboss.cdi.tck.tests.deployment.trimmed.enteprise.EnterpriseTrimmedBeanArchiveTest | 2.0
org.jboss.cdi.tck.tests.implementation.builtin.metadata.ee.BuiltinMetadataEEBeanTest | 2.0
org.jboss.cdi.tck.tests.extensions.interceptors.InterceptorExtensionTest | 2.0
org.jboss.cdi.tck.tests.context.application.event.ApplicationScopeEventTest | 2.0
org.jboss.cdi.tck.tests.context.passivating.broken.decorator.enterprise.EnterpriseBeanWithNonPassivatingDecoratorTest | 2.0
org.jboss.cdi.tck.tests.context.request.event.remote.RequestScopeEventRemoteTest | 2.0
org.jboss.cdi.tck.tests.interceptors.ejb.InterceptorInvocationTest | 2.0
org.jboss.cdi.tck.tests.context.jms.MessageDrivenBeanContextTest | 2.0
org.jboss.cdi.tck.tests.context.passivating.broken.interceptor.enterprise.field.EnterpriseBeanWithNonPassivatingInjectedFieldInInterceptorTest | 2.0
org.jboss.cdi.tck.tests.context.session.listener.shutdown.SessionContextListenerShutdownTest | 2.0
org.jboss.cdi.tck.tests.definition.stereotype.alternative.enterprise.EnterpriseStereotypeAlternativeSpecializeTest | 2.0
org.jboss.cdi.tck.tests.decorators.definition.lifecycle.DecoratorInstanceIsDependentObjectTest | 2.0
org.jboss.cdi.tck.tests.definition.bean.types.enterprise.illegal.BeanTypesWithIllegalTypeTest | 2.0
org.jboss.cdi.tck.tests.extensions.lifecycle.processInjectionTarget.ContainerEventTest | 2.0
org.jboss.cdi.tck.tests.deployment.packaging.visibility.VisibilityOfAnnotatedTypesFromExtensionInBravoBeanArchiveTest | 2.0
org.jboss.cdi.tck.tests.implementation.simple.resource.ejb.staticProducer.EjbInjectionStaticProducerFieldTest | 2.0
org.jboss.cdi.tck.tests.extensions.lifecycle.events.ContainerLifeCycleEventRuntimeInvocationTest | 2.0
org.jboss.cdi.tck.tests.implementation.simple.resource.broken.type.ejb.ResourceDefinitionWithDifferentTypeTest | 2.0
org.jboss.cdi.tck.tests.implementation.enterprise.broken.statelessWithSessionScope.StatelessWithSessionScopeTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.EnabledProducerMethodInjectionAvailability02Test | 2.0
org.jboss.cdi.tck.tests.implementation.simple.ee.components.JavaEEComponentsTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.SelectedAlternativeManagedBeanInjectionAvailabilityTest | 2.0
org.jboss.cdi.tck.tests.context.passivating.dependency.resource.persistence.DataSourcePassivationDependencyTest | 2.0
org.jboss.cdi.tck.tests.extensions.processBean.ejb.ProcessSessionBeanTest | 2.0
org.jboss.cdi.tck.tests.interceptors.definition.enterprise.interceptorOrder.SessionBeanInterceptorOrderTest | 2.0
org.jboss.cdi.tck.tests.decorators.builtin.http.session.BuiltinHttpSessionDecoratorTest | 2.0
org.jboss.cdi.tck.tests.context.request.postconstruct.SimpleBeanPostConstructCallbackTest | 2.0
org.jboss.cdi.tck.tests.context.passivating.broken.decorator.enterprise.field.EnterpriseBeanWithNonPassivatingInjectedFieldInDecoratorTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.SelectedAlternativeSessionBeanInjectionAvailabilityTest | 2.0
org.jboss.cdi.tck.tests.context.application.destroy.ApplicationContextDestructionTest | 2.0
org.jboss.cdi.tck.tests.implementation.enterprise.broken.singletonWithSessionScope.SingletonWithSessionScopeTest | 2.0
org.jboss.cdi.tck.tests.extensions.annotated.delivery.ejb.EnterpriseWithAnnotationsTest | 2.0
org.jboss.cdi.tck.tests.interceptors.definition.broken.finalClassInterceptor.ee.FinalMethodMethodLevelInterceptorTest | 2.0
org.jboss.cdi.tck.tests.alternative.selection.enterprise.EnterpriseSelectedAlternative02Test | 2.0
org.jboss.cdi.tck.tests.lookup.manager.jndi.ManagerTestEar | 2.0
org.jboss.cdi.tck.tests.implementation.builtin.servlet.ServletContainerBuiltinBeanTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.SpecializedBeanInjectionNotAvailable02Test | 2.0
org.jboss.cdi.tck.tests.extensions.lifecycle.processInjectionPoint.ee.ProcessInjectionPointFiredTest | 2.0
org.jboss.cdi.tck.tests.inheritance.specialization.simple.broken.extendejb.SpecializingBeanExtendsEnterpriseBeanTest | 2.0
org.jboss.cdi.tck.tests.lookup.dependency.resolution.broken.ambiguous.ear.MultiModuleSessionBeanAmbiguousDependencyTest | 2.0
org.jboss.cdi.tck.tests.deployment.packaging.visibility.JarToJarReverseAlphaVisibilityTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.EnabledProducerFieldInjectionAvailabilityTest | 2.0
org.jboss.cdi.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationTest | 2.0
org.jboss.cdi.tck.tests.event.observer.context.ObserverMethodInvocationContextTest | 2.0
org.jboss.cdi.tck.tests.event.observer.context.enterprise.SessionBeanObserverMethodInvocationContextTest | 2.0
org.jboss.cdi.tck.tests.context.conversation.inactive.InactiveConversationTest | 2.0
org.jboss.cdi.tck.tests.context.request.event.async.RequestScopeEventAsyncTest | 2.0
org.jboss.cdi.tck.tests.implementation.builtin.metadata.session.BuiltinMetadataSessionBeanTest | 2.0
org.jboss.cdi.tck.tests.context.application.ejb.ApplicationContextSharedTest | 2.0
org.jboss.cdi.tck.tests.implementation.builtin.BuiltInBeansTest | 2.0
org.jboss.cdi.tck.tests.context.conversation.determination.ConversationDeterminationTest | 2.0
org.jboss.cdi.tck.tests.lookup.typesafe.resolution.interceptor.ejb.EnterpriseResolutionByTypeTest | 2.0
org.jboss.cdi.tck.tests.event.observer.priority.contextLifecycleEvent.ee.RequestContextLifecycleEventObserverOrderingTest | 2.0
org.jboss.cdi.tck.tests.lookup.modules.specialization.alternative.Specialization01Test | 2.0
org.jboss.cdi.tck.tests.context.request.ejb.EJBRequestContextTest | 2.0
org.jboss.cdi.tck.tests.extensions.lifecycle.processBeanAttributes.ejb.VerifyValuesTest | 2.0
org.jboss.cdi.tck.tests.implementation.enterprise.definition.EnterpriseBeanDefinitionTest | 2.0
org.jboss.cdi.tck.tests.event.observer.transactional.roolback.TransactionalObserverRollbackTest | 2.0