geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <>
Subject Re: Geronimo and JSR-237 WorkManager API for App Servers
Date Wed, 22 Jun 2005 20:14:36 GMT
I saw only a very early draft of this JSR, which IMO had the fatal  
defect of not explaining the semantics of transactions when using the  
thread pool.  Has the current version of the spec added any discussion  
of transactions?

david jencks

On Jun 22, 2005, at 1:04 PM, Tyagi, Rahul wrote:

> Hello Team!!
> Recent version of leading app servers are supporting "JSR-237 Work  
> Manager for Application Server". I believe JSR-237 is simple and  
> powerful API for writing robust parallel processing application for  
> managed environment. Prior to that developers used to open non managed  
> threads for accomplishing parallel processing in J2EE container, ,  
> Obviously which is not a recommended way!!
> I think JSR-237 is a major step in writing scalable parallel  
> processing application within managed environment.
> I am curious whether we have plan to support JSR-237 in future  
> releases of Geronimo, If community see benefit of adding JSR-237 to  
> Geronimo I can volunteer to implement JSR-237 for Geronimo.
> Thanks,
> Rahul Tyagi
> *********************************************************************** 
> ****************************
> The information in this email is confidential and may be legally  
> privileged.  Access to this email by anyone other than the intended  
> addressee is unauthorized.  If you are not the intended recipient of  
> this message, any review, disclosure, copying, distribution,  
> retention, or any action taken or omitted to be taken in reliance on  
> it is prohibited and may be unlawful.  If you are not the intended  
> recipient, please reply to or forward a copy of this message to the  
> sender and delete the message, any attachments, and any copies thereof  
> from your system.
> *********************************************************************** 
> ****************************

View raw message