|
From: Eugene K. <eu...@md...> - 2004-10-27 16:10:49
|
James Strachan wrote: >> Then because it is using WorkManager's I wonder how it fits into >> exisitng J2EE container that does not support this API. I'm not >> convinced that it would be a good idea if component would do its own >> thread management (it woundn't be an issue for a single-noded Tomkat >> server, but could cause serious troubles on Weblogic or WebSphere >> clusters). >> >> So, it would be a good idea to capture some good practices where to >> use and where not to use this component. > > The WorkManager could come from a J2EE container; so the WorkManager is > just a property set on the JCAContainer which could be looked up via > JNDI. Plus we've a simple implementation based on the Geronimo codebase > but with some of the Geronimo dependencies removed to make it easy to > use in just Spring - if we were deploying inside Geronimo we could just > use its inbuilt & JMX managed implementation. Or a commercial J2EE > container would come with its own WorkManager implementation managed by > the container. I wonder if there would be any use of this container on J2EE 1.3 compliant containers where is no standard WorkManager API available. regards, Eugene |