|
From: <jas...@ma...> - 2004-07-09 12:38:29
|
On 9 Jul 2004, at 13:10, Dmitriy Kopylenko wrote: > So Rod, James, > > as I'm trying to understand, what would be the purpose (use case) of > creating such a "deployment unit"? To be able to expose > application-level beans via JMX or expose Spring components itself > such as BeanFactory via JMX? Both :) You could deploy multiple spring applications / deployment units inside a single Geronimo container & hot swap them along with any other J2EE deployment unit (WAR, EAR, RAR or new ones like CARs or SARs). What with all the management stack & tools, I'm thinking it might be a neat idea for folks to develop in Spring (nice & simple, invisible lightweight container etc) then when they get into production, when their pointy haired bosses insist on running everything in standard configuration J2EE app servers, we just drop in the spring deployment units. i.e. allow Spring to have its own deployment unit for running stuff rather than having to stick with EARs or WARs. Of course EARs & WARs are supported too - this just allows an extra option - treating Spring as a peer of WARs and EARs inside Geronimo. > And also, what is the "lower-level" transaction management in > Geronimo? Is it JTS? i.e. having a custom transaction manager plugin for Spring which can take advantage of all the features available in Geronimo's transaction manager. James ------- http://radio.weblogs.com/0112098/ |