I asked this question earlier along with another, but the thread became focused on the other question.
Apache Camel is a VERY interesting project. It looks like HornetQ would be simplified and become more powerful if the routing logic was a separate subsystem, rather than spread throughout the HornetQ code.
Have the committers thought of a Camel like subsystem? Or perhaps integrating with Apache Camel itself?
HornetQ, from my perspective as a developer of financial market systems, is more than just a messaging queue. The ability to define routs, transports, etc. is at least as important. HornetQ+Camel would basically solve countless problem for financial market developers.
There's nothing stopping you from you using HornetQ with Camel AFAIK, although I have never tried it.
This is something we should look at in the future - make sure it works fine with Camel. Create some wikis etc