|
From: Eugene K. <eu...@md...> - 2004-10-28 17:06:57
|
jas...@ma... wrote: >> 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'. Similar, but POJO defined only once in a local Spring context and from client point of view it is not different in both cases: MyBean b = (MyBean) SpringContext.getBean( "asyncPojo"); b.someMethod(); // executed asynchronously (no return) regards, Eugene |