Slashdot Mirror

← Back to Stories (view on slashdot.org)

Red Hat Spins Off JBoss 2.x As HornetQ

Posted by ScuttleMonkey on from the strip-mine-rename-and-release dept.

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."

4 of 50 comments (clear)

  1. Re:Yet another message passing system by nacturation · · Score: 5, Informative

    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.
  2. Re:POJO and message-oriented? by IBBoard · · Score: 4, Informative

    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).

  3. Re:Lets hope they fixed the major flows from 1.x by Hal_Porter · · Score: 4, Funny

    Heretic!

    Transaction safety is an evil practice of proprietary systems from the 1970's. It's not something we should be concerned with in the Web 2.0/Open Source world.

    --
    echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
  4. Clearing up a few inaccuracies by Tim+L+Fox · · Score: 5, Informative

    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