geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor" <>
Subject Re: Concurrency Utilities for Java EE
Date Fri, 07 Mar 2008 21:17:40 GMT
I just checked in the implementation of the Concurrency Utilities for
Java EE draft specification into svn. You can get the code from or browse
it via

There are still a few things missing from this implementation like
transaction or OpenEJB support, etc. In fact, to get this
implementation working with Geronimo right now you have to apply the
geronimo.trunk.patch file in the root directory.

I also have some test code (that I didn't check in yet) that shows how
these concurrency utilities would be used in an application.

Quick description of the key modules:

geronimo-concurrent_spec - the spec API
geronimo-concurrent-management - Geronimo-specific management interfaces (JMX)
geronimo-concurrent-core - basic implementation of the API. It does
not have any dependencies on Geronimo.
geronimo-concurrent - Geronimo-specific implementation of the API.
Extends the basic implementation and provides integration with
geronimo-concurrent-builder - processes resource-env-ref references in
DDs and annotations.


On Thu, Feb 14, 2008 at 12:06 PM, Jarek Gawor <> wrote:
> Folks,
>  For the past few weeks I've been working on the Concurrency Utilities
>  for Java EE specification implementation. The Concurrency Utilities
>  for Java EE specification is a draft specification (see
> for more info)
>  that is supposed to replace the JSR-236 (Timer API) and JSR-237 (Work
>  Manager API) specifications and become part of Java EE 6.  The
>  Concurrency Utilities for Java EE specification basically extends the
>  java.util.concurrent.Executor API and adds managed environment
>  qualities to the tasks executed via the Executor. That is, the
>  background tasks can execute with the same environment as the
>  application that started it.
>  I have a little bit of code but it's definitely not complete or fully
>  functional and still needs a lot of work (e.g. better integration with
>  Geronimo, etc.). I would like to donate this code to Geronimo, and
>  continue to work on it there as a community.
>  Now, the cool thing is that this implementation might become the
>  official Reference Implementation (RI) for this spec. I've talked with
>  the IBM co-spec lead and there is a good chance of that happening if
>  we also commit to writing a TCK for it. And I think that would be a
>  great opportunity for Geronimo to show some leadership in the Java EE
>  spec area.
>  Even if the RI thing does not work out or this specification does not
>  become part of Java EE 6, I still think this functionally would be a
>  good addition to Geronimo.
>  What do people think? Thoughts, any concerns?
>  Jarek

View raw message