<< Back to previous view

[CONCURRENCY_EE_SPEC-36] Define new execution property constants in ManagedTask interface to support app portability Created: 23/Apr/14  Updated: 23/Apr/14

Status: Open
Project: concurrency-ee-spec
Component/s: None
Affects Version/s: 1.0
Fix Version/s: None

Type: New Feature Priority: Major
Reporter: f.rowe Assignee: Unassigned
Resolution: Unresolved Votes: 0
Remaining Estimate: 30 minutes
Time Spent: Not Specified
Original Estimate: 30 minutes

Tags:
Participants: f.rowe

 Description   

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"






Generated at Fri Apr 25 01:42:51 UTC 2014 using JIRA 4.0.2#472.