Details
-
Feature Request
-
Resolution: Won't Do
-
Optional
-
None
-
None
-
None
-
None
-
Medium
-
0
-
0%
Description
In May 2004 IBM and BEA introduced v1.1 of their Work Manager API (aka commonj). The specification defines a concurrent programming API for JEE. (see also http://ftpna2.bea.com/pub/downloads/commonj/Commonj-TimerAndWorkManager-Specification-v1.1.pdf )
In particular it introduces the waitForAll(jobs) and waitForAny(jobs) methods to the WorkManager. The methods take a list of Work Items as input which are scheduled for execution. waitForAll() blocks until all the jobs in the list have been finished. waitforAny() blocks until one job of the list has finished.
I know this is not part of the JCA spec, but I think this functionality would really add to the usefulness of the WorkManager. After all the WorkManager should be the preferred way to have applications execute multiple work items concurrently under the control of the container (in order to avoid using Thread directly)... Besides this additions seem to be considered a de-facto standard (as stated in http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3929568 for example)