Re: [activemq-dev] Re: [Springframework-developer] Re: [activemq-dev] Re: message driven POJOs, a lightweight JCA container available

[Eugene K. <eu...@md...>]

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. :-)
   The only issue there is to detect in interceptor where POJO has been 
called from (skip interceptor if it is called from message 
consumer/MDB). Spring AOP documentation is saying that it is not 
recommended/slow to use control flow pointcuts, so other options would 
be to use custom pointcut or even AW or AspectJ.

   regards,
   Eugene