Hi Anthony,
Here is some feedback based upon Early Draft of JSR 236:
1). The first bullet in section 1.2 says " Preserve the fundamental
capabilities and integrity of the Java EE platform. " Even though may be
one of the goals but being the first bullet, it feels that is the
primary goal of this JSR. IMHO the second line in second bullet is the
primary goal instead which states " Provide a simple yet flexible API
for application component providers to design applications using
concurrency design principles."
Isn't the first bullet an implicit goal for all specifications anyway ?
2). There is a submit method for Runnable and Callable. But invokeAll is
only for Callable. Why ?
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.
4). 3.1.4 - Its not clear how/where these configuration attributes can
be specified.
5). AIU figure 3-1: each cube has a light blue box to indicate the task
being executed and another color to indicate the application that
initiated that task. Does the changed color of surrounding cube indicate
the changed context ?
6). I could not find any discussion around CDI-style
ManagedThreadExecutor. Is that coming or not planned ?
7). Do the tasks always need to create a new UserTransaction ? Will
setting Contextual-Callback propagate the transaction context from
container to the tasks run by the executor ?
What about security context ?
8). The spec talks about "execute" method where as the javadocs you
shared has "invoke". Which one is accurate ?
9). When the job is submitted, is it executed right away or dispatched
to a queue where it waits for execution ?
10). How is the thread pool configuration relates to a similar
configuration in application server runtime ?
Thanks
Arun
Thanks,
Arun
--
http://twitter.com/arungupta
http://blogs.oracle.com/arungupta