To add another twist to this.... What I was thinking re scheduling was to have a "ScheduledEventProvider" (e.g. <sevent-provider> that generates scheduled events). With that, you could then have a "ScheduledEventListener" (<sevent-listener>) which listens to the <sevent-provider>. The <sevent-listener> could be configured with a MessageComposer in the same way all (or at least some) of the other listeners can be configured with a composer (org.jboss.soa.esb.listeners.message.MessageComposer impl) that does whatever is needed. So, taking the WSListener as an example, it would actually be implemented as a MessageComposer that sits on a <sevent-listener> and when triggered (asked to "compose"), it goes off and makes the SOAP invocation and uses the result to compose the org.jboss.soa.esb.message.Message payload to be processed by the service pipeline (or whatever). Just another option :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065671#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...