Hi,
I've created Guava Event Bus component [3].
It can be used both on the consumer and producer side. The idea behind
it is to allow client applications using Google Guava [1] and Event
Collaboration [2] to transparently integrate their code with the Camel
infrastructure.
The nice thing here is that client application can stay unaware of
using Camel as the transport and routing layer. Client depends only on
Guava libraries.
__________________
Consumer use case:
from("guava-eventBus:busName?eventClass=com.example.MyNotification").to("seda:eventQueue");
Event bus consumer collects events incoming to the message bus and
forward them to the Camel infrastructure.
__________________
Producer use case:
from("direct:fireEvent").to("guava-eventBus:busName");
Producer is used send body of Camel messages to the Guava event bus
(so that client application listeners can consume them).
_______________________
Could somebody take a look at it and hopefully submit it to the trunk? :)
Laters.
[1]
http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/eventbus/package-summary.html
[2] http://martinfowler.com/eaaDev/EventCollaboration.html
[3] https://issues.apache.org/jira/browse/CAMEL-5341
--
Henryk Konsek
http://henryk-konsek.blogspot.com
