The following issue has been updated:

    Updater: Gianny DAMOUR (mailto:[EMAIL PROTECTED])
       Date: Sat, 6 Sep 2003 1:51 AM
    Comment:
Only new files. It has an orthogonal impact. Actually, I wanted to patch some 
core components (AbstractComponent, AbstractContainer) because there is a bug 
(another story) already reported by GERONIMO-14, and I have decided to play it 
"safe" by using only the Dependency service features.
    Changes:
             Attachment changed to patch-workManagement.jar
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=GERONIMO-73&page=history

---------------------------------------------------------------------
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=GERONIMO-73


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: GERONIMO-73
    Summary: WorkManager implementation
       Type: New Feature

     Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

    Project: Apache Geronimo
 Components: 
             core

   Assignee: 
   Reporter: Gianny DAMOUR

    Created: Sat, 6 Sep 2003 1:47 AM
    Updated: Sat, 6 Sep 2003 1:51 AM

Description:
This patch contains an implementation of the WorkManager spi. This 
implementation delegates the submitted work to three distinct executors - one 
for each synchronization policy. Each executor is a thread pool based on the 
Doug Lea's PooledExecutor.

The WorkManager and its WorkExecutors are MBeans and are deployed via the 
WorkManagement-service.xml file.

During the execution of a work, the WorkListener provided during a the work 
submission is duly notified.

A test case yielding the three distinct synchronization policy is also 
provided. This test case uses the WorkListener notifications in order to 
introspect the status of submitted works.

Gianny


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

Reply via email to