Dealing with multiple messaging protocols in one OSGi environment will get much easier with the new upcoming Messaging Specification.
Nowadays, each messaging system brings its own API or drivers for dealing with similar situations. Even for the same protocols, there are multiple implementations. When you have to deal with work with different protocols, this situation can be a pain.
The Messaging Specification tries to harmonize most common use-cases like publish and subscribe, we all know very well. But beside that, it will also cover use-cases like Reply-To Behavior on the publishers side as well from the worker side. This all will happen without knowing the underlying protocol in detail.
You will see, how this all can fit in the service-oriented world of OSGi and how PushStreams and Promises leveraging the efficiency of handling data in such an API. The talk will also give an outlook of the specification's current state and show the potential of other possible use-cases you might never thought about ...