|
From: Colin S. <col...@ex...> - 2004-05-29 00:55:55
|
Ben Alex wrote: >>I am in the thick of things at work so can't really put >>enough thought into this to comment much, but I would prefer >>to hold this until after >>1.0.3 is out... >> >> > >I just wanted to chime in here and mention what Ross is working towards is >strategically very useful for Spring users. > >By simply adding Mule (which BTW is now configurable directly from a Spring >ApplicationContext) Spring users will have the ability to receive events >from external sources (JMS, DB, HTTP etc), then transform them into native >ApplicationEvents and publish them in the ApplicationContext, and then send >ApplicationEvent replies to the ApplicationContext and have Mule send them >off to external sources. So Mule acts as an adapter between >ApplicationEvents and the external world. Mule can also be used directly to >take advantage of the growing library of Mule objects that perform message >transformation etc. > >I recently added some ApplicationEvent support to Acegi Security CVS (login >success/password fail events), and am about to embark on a Swing GUI built >on top of Spring where it will be used again. It's nice for these sort of >internal-to-the-ApplicationContext usages, but if I want to publish a >CustomerOrder to a remote CustomerOrderConsumer, it will be nice when Mule >can deliver it for me. > >Best regards > > Sorry, my typo. I meant to say until after _1.0.2_ is out, not 1.0.3! I think the Mule stuff is very interesting and potentially usefull as well. I was just trying to make sure Juergen doesn't try to add any more code for 1.0.2. :-) Colin |