Support Forums: Message List - The wise work manager for context-based scoping

good day

Thu, 16 May 2013 02:39:10 -0400

context-based scoping is easily manageable http://www.bartendertrainingsource.com

insights

Thu, 03 Jan 2013 08:08:07 -0500

context-based scoping is necessary for me

stork club newsreel

agree

Thu, 03 Jan 2013 07:54:08 -0500

i agree with you Bill

buffalo search engine optimization

Re: The wise work manager for context-based scoping

Tue, 23 Jan 2007 09:51:34 -0500

On Bills comment. Commonj had to work on Java 1.4 so no concurrent stuff and the concurrent JSR wasn't final when we did it in any case. Doug did make some changes for us in his JSR to accomodate 236/237 and I was very grateful for that...

Re: The wise work manager for context-based scoping

Tue, 23 Jan 2007 09:42:58 -0500

On Bills comment. Commonj had to work on Java 1.4 so no concurrent stuff and the concurrent JSR wasn't final when we did it in any case. Doug did make some changes for us in his JSR to accomodate 236/237 and I was very grateful for that cooperation....

Re: The wise work manager for context-based scoping

Mon, 22 Jan 2007 13:55:33 -0500

In IBM WebSphere, it is called Asynchronous Bean (I think this name describes the behavior better than Work Manager). It has been available in WebSphere for about 3 years now. ...

why a new API?

Mon, 22 Jan 2007 13:51:26 -0500

I looked at this JSR over a year ago and one thing that popped up at me is why are we creating another API for spawning threads when one already exists in java.util.concurrent? Since java.util.concurrent already has a very nice, battled-tested SPI, why...

OLAP not OLTP

Mon, 22 Jan 2007 10:06:57 -0500

I think the main point here is that I'm dealing with OLAP and not OLTP. The way most software in this space functions is that you query one database and that database works out how it queries 32 different nodes for you. That is the complexity is pushed...

Re: Transaction context across threads

Mon, 22 Jan 2007 09:36:22 -0500

Would you really want to use the same transaction context (XA) to query 32 databases? Can you describe the business level transactional semantics so that we can suggest an optimal resource transaction mapping. ...

Transaction context across threads

Mon, 22 Jan 2007 09:10:24 -0500

One thing that I did ask about a while ago to the Spring team was about how to use this API for getting a transaction context to be passed to multiple threads. The application in question is an analytic application. If I have say 32 nodes in a cluster...

Re: The wise work manager for context-based scoping

Mon, 22 Jan 2007 08:57:40 -0500

I actually thought one of the (additional) important benefits of the WorkManager API was the event mechanisms as well as the co-ordination of the multiple units of work via the waitForXXX methods. I rarely just run an asynchronous task ("fire...

Re: Put the Thread Pool in the JDK

Mon, 22 Jan 2007 07:12:48 -0500

Why is the Work Manager API part of Java EE and not just part of Java SE? Most apps need to use multi-threading in some capacity.

...

Re: The wise work manager for context-based scoping

Mon, 22 Jan 2007 06:38:43 -0500

All an application really needs is a straightforward way to kick off an asynchronous task...

...

Re: The wise work manager for context-based scoping

Mon, 22 Jan 2007 03:48:51 -0500

Interesting... It is pretty close to the JCA 1.5 Work Management Contract...

...

Re: The wise work manager for context-based scoping

Mon, 22 Jan 2007 01:09:30 -0500

We use JMS for thread spawning: The starting thread (e.g. SLSB) sends n JMS messages which contain the spawn information to n MDBs (message facades) and this creates n spawned threads (e.g. in SLSBs). ...