[CONCURRENCY_EE_SPEC-21] Add default objects similar to EE5.20 and EE5.21 Created: 10/Dec/12 Updated: 27/Dec/12 Resolved: 27/Dec/12
|Fix Version/s:||Public Review|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
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.
|Comment by anthony.lai [ 11/Dec/12 ]|
need to work with Java EE 7 spec lead to incorporate these default objects into the Java EE 7 Platform spec.
|Comment by anthony.lai [ 27/Dec/12 ]|
Added requirement to Java EE Product Provider to provide default ManagedExecutorService, ManagedScheduledExecutorService, ContextService, and ManagedThreadFactory.