Define new execution property constants in ManagedTask interface to support app portability

[glassfishrobot]

Consider adding additional execution property constants to the ManagedTask interface to allow control of the propagation of the required contexts, jndi, classloader and security. This will support application portability between app server providers.
For example, we could add:
static final String JNDI_CONTEXT_SOURCE - Execution property to be returned in getExecutionProperties() or ContextService.createContextualProxy() to control how the Java™ EE Product Provider propogates the JNDI context to the task or proxy method of contextual proxy object be executed in. Valid values are: "CURRENT_THREAD", "DEFAULT", and "NONE"
static final String CLASSLOADER_CONTEXT_SOURCE - Execution property to be returned in getExecutionProperties() or ContextService.createContextualProxy() to control how the Java™ EE Product Provider propogates the classloader context to the task or proxy method of contextual proxy object be executed in. Valid values are: "CURRENT_THREAD", "DEFAULT", and "NONE"
static final String SECURITY_CONTEXT_SOURCE - Execution property to be returned in getExecutionProperties() or ContextService.createContextualProxy() to control how the Java™ EE Product Provider propogates the security context to the task or proxy method of contextual proxy object be executed in. Valid values are: "CURRENT_THREAD", "DEFAULT", and "NONE"

Affected Versions

[1.0]

[glassfishrobot]

@glassfishrobot Commented
Reported by f.rowe

[glassfishrobot]

@glassfishrobot Commented
This issue was imported from java.net JIRA CONCURRENCY_EE_SPEC-36

[glassfishrobot]

• Issue Imported From: https://github.com/javaee/concurrency-ee-spec/issues/36
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @alai8

[njr-11]

ContextServiceDefinition, which was added in Concurrency 3.0 / Jakarta EE 10 covered this requirement in a different way by allowing the equivalent to be configured in a standard way on ContextServiceDefinition. I'd recommend closing this as a duplicate unless anyone sees a need for doing the same thing via execution properties.