Re: [Springframework-developer] Spring / Mule integration - step 1

[<jue...@we...>]

Hi Ross,
=20
Interesting stuff! Out of curiosity, are you using Mule yourself in a =
concrete application at Atlassian?
=20
Regarding getting notified of events published by Spring beans: Why not =
simply make the MuleEventManager implement the ApplicationListener =
interface? It would automatically receive all ApplicationEvents then =
(like any other ApplicationListener in the context), being able to =
process them accordingly (all other listeners will ignore events that =
they don't know anyway).
=20
So I don't really see a reason why you'd need to hook into the =
ApplicationEventMulticaster here. Please tell me if I missed your point =
:-)
=20
Juergen
=20

________________________________

Von: spr...@li... im Auftrag =
von Mason, Ross
Gesendet: Fr 28.05.2004 13:42
An: spr...@li...
Betreff: [Springframework-developer] Spring / Mule integration - step 1


Hi,
I'm writing some extensions to integrate Spring with Mule (Mule is an =
ESB - www.muleumo.org). I'm starting with an extension to Spring's =
ApplicationEvent implementation to allow beans to receive Mule events.
=20
Mule events can be sent over transports such as jms, http, smtp, pop3, =
tcp, etc so a bean in a Spring context could implement a =
JmsEventListener, pop3EventListener, etc to receive events published in =
Mule.  Plus the observer interface could expose subscription methods to =
enable Mule to publish to different subscriptions, i.e.
=20
public class JmsEventListener implements ApplicationEvent {
=20
    public void setSubscription(String subscription);
=20
    public String getSubscription();
}
=20
This would allow springs beans to receive Jms messages, emails, data =
over http. Mule handles the transformation of these events =
transparently.
=20
for publishing events, the application code could publish a MuleEvent =
with an endpoint and a transport  to the applicationContext, which could =
be recieved by a MuleEventManager bean.
=20
The problem is that I'm having trouble seeing how to change the way =
Spring manages events.  Ideally, the EventMulticaster on the =
AbstractApplicationContext would be accessible with getter and setter =
methods so that the 'MuleEventManager' bean could hook in it's own =
eventMulticaster that knows how to deal subscription events and how to =
manage MuleEvents published by Spring Beans.
=20
I think this sort of extension would add value to Spring, would you guys =
consider exposing the EventMulticaster?
=20
Cheers,
=20
Ross