|
From: <jas...@ma...> - 2004-10-28 17:01:07
|
On 28 Oct 2004, at 17:54, Eugene Kuleshov wrote: > Jason Carreira wrote: > >>> Are you suggesting to replace Spring with XWork? :-) > >> No, not at all... The project I was discussing uses Spring to wire >> everything together. I was just suggesting that you can have Action >> classes (really command objects) which don't have to know anything >> about JMS, and could even be reused across JMS, Web, or even command >> line. I like my components to be decoupled from the deployment >> technologies. > > Still can't see why XWork action wold be better then POJO's managed > by Spring. In my case MDB is basically delegating all processing to > given POJO's. > > I was thinking on doing somehow opposite thing. Use custom > interceptor, which will transparently serializes all parameters and > send them together with POJO name to JMS queue, which has pool of > consumers (MDB's in my case) that are asynchronously executing that > call on given POJO instance. :-) Unless I'm missing something, that sounds exactly like Spring JMS Remoting :). The only difference is to use pooling, we'd probably use 'message driven pojos'. James ------- http://radio.weblogs.com/0112098/ |