JBossESB - EventManager Action
Sometimes you want a service that allows you to do a pub-sub that is independent of the underlying transport (i.e., is not tied to JMS). One of our consulting engineers had that requirement with a company and this is the initial result: an EventManager Action.
This Action accepts two types of Message:
control messages (subscribe, unsubscribe)
event messages (typed and can be wild-carded)
In order to send a control message, the format is as follows:
place either SUBSCRIBE or UNSUBSCRIBE as the value for the named Body item org.jboss.soa.esb.actions.event.opcode
place the name of a topic (event) the endpoint wants to be informed about as the value for the named Body item org.jboss.soa.esb.actions.event.type. You can use to mean "any event".
send the message and ensure that ReplyTo or From (in that order) are set: this will be the address used to route any events.
In order to send an event message, the format is as follows:
place EVENT as the value for the named Body item org.jboss.soa.esb.actions.event.opcode
place the name of the event as the value for the named Body item org.jboss.soa.esb.actions.event.type
optionally place true or false as the value for the named Body item org.jboss.soa.esb.actions.event.message. If true, then the message you send will be distributed to registered endpoints. Otherwise (false) a new message will be sent that simply comprises the event name in org.jboss.soa.esb.actions.event.type
This is a basic implementation and not intended for high throughput. That may change in the future if there is sufficient need, as could the feature set (e.g., adding finer grained topic control).