Issue Details (XML | Word | Printable)

Type: Task Task
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: anthony.lai
Reporter: anthony.lai
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.

Add default objects similar to EE5.20 and EE5.21

Created: 10/Dec/12 11:31 PM   Updated: 27/Dec/12 07:18 PM   Resolved: 27/Dec/12 07:18 PM
Component/s: None
Affects Version/s: None
Fix Version/s: Public Review

Time Tracking:
Not Specified

Participants: anthony.lai

 Description  « Hide

I really like the idea of default instances that would be consistent with other resource types in EE 7 as Anthony pointed out. For the majority of apps, this would provide a simple, zero-configuration way to use ManagedExecutorService/ScheduledExecutorService/ContextService/ThreadFactory that is easily and straightforwardly overridable by the deployer. Writing this up would just involve copying from EE 7 section 5.20 or 5.21 and replacing with the JSR 236 resource types, but on top of that I would recommend that we standardize a minimum set of contexts that must be propagated by the default instances, provided the container supports those contexts. Naming/classloader/security as mentioned previously would make sense.

anthony.lai added a comment - 27/Dec/12 07:15 PM

Added requirement to Java EE Product Provider to provide default ManagedExecutorService, ManagedScheduledExecutorService, ContextService, and ManagedThreadFactory.

anthony.lai added a comment - 11/Dec/12 09:48 PM

need to work with Java EE 7 spec lead to incorporate these default objects into the Java EE 7 Platform spec.