TCK Challenge ContextPropagationTests#testContextualFunction, JNDI search in unchanged APPLICATION context

[aubi]

Specification:

Jakarta Concurrency 3.0.0

Challenged test(s):

ee.jakarta.tck.concurrent.spec.ContextService.contextPropagate.ContextPropagationTests#testContextualFunction

TCK version:

3.0.1

Tested implementation:

Payara 6 (branch)

Description

Similar situation to #224, the test should set APPLICATION to be cleared, but it is in unchanged. It then tests JNDI lookup for java:module and expects, that it is not available. For some servers, the current thread can be created from a servlet thread and inherits its invocation, e.g. the JNDI context is available and the test fails.

I will prepare a fix for the test.

[njr-11]

Reassigned to @smillidge per TCK process which says that challenges are to be resolved by the specification project lead. I added a thumbs up to the description to indicate that I'm in favor of accepting this challenge.