FW: [concurrency-interest] Executors and J2EE Work frameworks

Doug Lea dl@cs.oswego.edu
Fri, 12 Dec 2003 19:21:32 -0500

Nearly everyone agrees that it will be useful and important to have an
asynch execution framework available in J2EE as well as J2SE.  Among
the main goals at this point is to ensure that APIs are as consistent
as possible across J2SE and J2EE. (For those not familiar with J2EE:
they cannot be exactly the same because J2EE tasks must all run within
context (transaction, security etc) settings maintained by
containers. So both Executors managing threads and Futures maintaining
task context must be controlled by containers. And instead of making
concrete implementations available there must be some mechanism for
applications to ask containers to produce or access one.)

I volunteered today to serve on the JSR236/7 expert groups (assuming
they are accepted), and try to help ensure consistency etc.  The
ultimate APIs might look more like JSR166's than do those in the JSR
proposals. Or maybe not, if there turn out to be good reasons to make
them different.  In the mean time, if you are a J2EE user, you can
help by trying to find any obstacles that might be remaining in our
APIs before changes become impossible (very soon!)