On 07.12.2012 22:35, Arun Gupta wrote:
> Thanks Anthony!
>
> Including users alias to the response as I cannot respond to the EG alias.
>
> cil
>
> On 12/4/12 5:42 PM, Anthony Lai wrote:
>> Hi Arun,
>>
>> Thanks for the feedback! I did not get your mail through the users
>> mailing list either, but your mail does show up in the users mailing
>> list archive. Not sure why. I am replying to the experts mailing list
>> so both experts and users list subscribers could read this as well.
>>
>> Please see comments below. Thanks.
>>>
>>> 2). There is a submit method for Runnable and Callable. But invokeAll
>>> is only for Callable. Why ?
>> That is because the ManagedExecutorService interface extends from
>> java.util.concurrent.ExecutorService in Java SE, which does not have
>> invokeAll for Runnable.
>>>
>>> 3). Examples in 3.1.4.1.1, .2 and .3 do not show ThreadUse property
>>> in the table. Section 3.2.4.1.1, .2, and .3 do show that property.
>> I think it makes sense to have the ThreadUse property in
>> ManagedThreadFactory as well. But we are reviewing the configuration
>> sections. Currently these sections contain example configuration
>> attributes. It was brought up to the expert group that we should try
>> to define a few required attributes and remove optional ones from the
>> spec.
>>>
>>> 4). 3.1.4 - Its not clear how/where these configuration attributes
>>> can be specified.
>> It would be depend on each application server.
> I think a portable way of specifying this attributes would be useful -
> either as annotations or may be in web.xml.
>
> In general, Java EE 6 moved away from deployment descriptors. Providing
> both a declarative and programmatic way to define these attributes will
> be useful.
+1
A CDI stereotype would be really cool.
Cheers
Philippe