Slashdot Mirror
Red Hat Spins Off JBoss 2.x As HornetQ
Several sources are reporting that Red Hat has spun off the 2.x release of the JBoss messaging protocol as HornetQ. The 1.x version of JBoss is still being supported in maintenance mode and will continue to be known by its original name. "HornetQ is an open source project to build a multi-protocol, embeddable, high performance, clustered, asynchronous messaging system. HornetQ is an example of Message Oriented Middleware. [...] HornetQ is designed with flexibility in mind: It's elegant POJO based design has minimal third party dependencies: Run HornetQ as a stand-alone messaging broker, run it in integrated in your favorite JEE application server, or run it embedded inside your own application. It's up to you."
Just what the world needed.
Is there something special about this that the 101 others around can't do or is it just a Me-Too product for Redhat?
JBoss MQ goes back to 2002 and was renamed to JBoss Messaging and is now being renamed to HornetQ. Given that it's been around for so long, you should instead ask most of your 101 other ones why they are Me-Too products.
Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
Yeah, right. Go look up the 2 main ones used in the Fortune 100s - Websphere (formally) MQ Series and Tibco EMS and see how long they've been around.
I never claimed JBoss MQ has been around longest. Your initial statement was that there were 101 others and JBoss MQ is a Me-Too product for Redhat. Unless you can prove that there were 101 that came before JBoss MQ, your initial statement is bullshit.
Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
And in case people wonder what POJO is (it seems to be tagged but not answered at the moment) they're Plain Old Java Objects (i.e. standard Java objects with no additional attributes or post-processing beyond what happens to any other class).
I wouldn't call Knuth lazy even if the 4th volume of his Art of Computer Programming is a bit late. While you wait for it, the 3rd edition of Introduction to Algorithms is available on Amazon. Please be patient!
Hello all-
Just to correct a few misconceptions / errors here:
1) HornetQ is not a "messaging protocol" as the title states, it's a messaging system, a MoM (see http://en.wikipedia.org/wiki/Message-oriented_middleware), other examples of MoMs are WebsphereMQ, Tibco EMS, ActiveMQ etc
2) HornetQ is a completely different project to JBoss Application Server - it shares zero code with JBoss AS. So any comments about JBoss Application Server start-up time are not relevant to HornetQ
3) HornetQ is a rebranding of the JBoss Messaging 2.0 codebase by JBoss. The HornetQ codebase is almost completely different to JBoss Messaging 1.x and JBoss MQ codebase, so any comments about JBoss Messaging 1.x or JBoss MQ are not really relevant either.
All of the above are actually explained in the FAQ, but I thought I'd re-iterate them here.
Disclosure: I'm Tim Fox the project lead for HornetQ
Hello all-
Just to correct a few misconceptions / errors here:
(I'm reposting as first time it seems to have lost my comment)
1) HornetQ is not a "messaging protocol" as the title states, it's a messaging system, a MoM (see http://en.wikipedia.org/wiki/Message-oriented_middleware), other examples of MoMs are WebsphereMQ, Tibco EMS, ActiveMQ etc
2) HornetQ is a completely different project to JBoss Application Server - it shares zero code with JBoss Application Server. So any comments about JBoss Application Server start-up time don't apply to HornetQ - HornetQ starts up very fast!
3) HornetQ is a rebranding of the JBoss Messaging 2.0 codebase by JBoss. The HornetQ codebase is almost completely different to JBoss Messaging 1.x and the old JBoss MQ codebase, so any comments about JBoss Messaging 1.x or JBoss MQ are not really relevant either, they're different systems.
All of the above are actually explained in the FAQ, but I thought I'd re-iterate them here.
Disclosure: I'm the project lead for HornetQ