In Chapter 6, Clustering with HornetQ, we learnt how to set up and dial with a cluster formed by one or more machines. We have also seen that on the same standalone HornetQ server, it is possible to create and use different queues (both core and JMS).
Such a configuration setup allows great flexibility and expands the different possibilities that an administrator or a coder has; to implement a high frequency message delivery system. Nevertheless, for the moment, if we want to send different types of messages to different queues you are forced to create sessions and producers on different queues.
HornetQ offers the possibility of setting up filters that work on the server side, so that it is possible to apply filters based on the messages, without any changes in the client logic.
The JMS specification allows the selector to act this way so that the HornetQ implementation works in this way, but the HornetQ filtering functionality, based on the implementation...