Well, I think implementing this would be great.  I'd like to know:
- whether WorkManager could use our thread pool gbean or if we should replace uses of the thread pool gbean with WorkManager or some other relationship - whether the J2CA WorkManager should use the jsr-23 WorkManager or vice versa or neither

Our transaction manager is rather aggressively single threaded, so currently any jsr-237 implementation is going to have to not propagate transactions between threads. We need to look at the advanced transaction services spec (activity service?) to see what they have to say about this also. I'd be delighted to talk more about this issue.... next week ;-)

thanks
david jencks

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


You can assume WorkManager to be a container managed thread pool. Using WorkManager one can schedule work workManager.schedule(Work work) and schedule would get a thread from container managed thread pool and process the work (Work implements java.lang.Runnable). It has capability to add dependency of work completion on other work. Work has life cycle and user can define listener for listening to those work life cycle events.

David Jencks Wrote

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?

So far this specification do not state anything for managing transaction. But i think we need to enhance that part. I personally believe in both approach standardize first then implement Or Innovate/implement first and then standardize, In our case we need to follow later :)...

To avoid security message probably i would start using my personal email ID for this email list.

Thanks,

Rahul


-----Original Message-----
From: Aaron Mulder [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 22, 2005 3:40 PM
To: [email protected]
Subject: Re: Geronimo and JSR-237 WorkManager API for App Servers


On Wed, 22 Jun 2005, Tyagi, Rahul wrote:
...
I think JSR-237 is a major step in writing scalable parallel processing
application within managed environment.

Can you give us some more detail on what JSR-237 requires from the app
server?

Also, the footer block below needs to go!  :)

Thanks,
        Aaron

*********************************************************************** **************************** 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. *********************************************************************** ****************************


Reply via email to