Clarify if interceptors in archive other than the intercepted class's archive should also share the class's enterprise naming context

[glassfishrobot]

To summarize, is the following scenario reasonable?

Simplified scenario: EAR:

• ejb-test.jar: @Priority(1000) @FooBinding FooInterceptor, @FooBinding
  • visible to test1.war
• test1.war: Foo, web.xml with
  • not visible to ejb-test.jar

The question is whether FooInterceptor in .jar should get injected (using @Resource) the env-entry resource declared in the war's web.xml

Test case at: https://github.com/cdi-spec/cdi-tck/blob/4de48c4ac2fed89d517d50ab3e89fef163ac258d/impl/src/main/java/org/jboss/cdi/tck/interceptors/tests/contract/interceptorLifeCycle/environment/jndi/InterceptorEnvironmentJNDITest.java

(Some people might say that this is not the intent.)

Affected Versions

[1.2]

[glassfishrobot]

Reported by bafco

[glassfishrobot]

bafco said: Interceptors Spec: 2.2.1 Interceptor Environment An interceptor class shares the enterprise naming context of its associated target class. Annotations and/or XML deployment descriptor elements for dependency injection or for direct JNDI lookup refer to this shared naming context.

Java EE Platform Spec.: EE.5.2 JNDI Naming Context

• EE.5.2.4 Sharing of Environment Entries Each application component defines its own set of dependencies that must appear as entries in the application component’s environment. All instances of an application component within the same application instance within the same container share the same environment entries.

[glassfishrobot]

This issue was imported from java.net JIRA INTERCEPTORS_SPEC-28