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

1 of 50 comments (clear)

  1. And why should we care? by Antique+Geekmeister · · Score: 1, Offtopic

    Seriously. If all it is is a 'messaging protocol', why can't we just use UUCP or, say, something whose underlying compiler is stable? I've been having tremendous issues with having to install subtlely different JVM's for different applications because they cannot keep straight where the JVM's are installed, how to name them, or whether they are compatible with one different appliations. (Sun is no help with this, by the way: the 'write once, run everywhere' model for Java has been more of a 'write once, run nowhere' one this last year due to version drift.) If I see one more application installer overwrite '/etc/profile' by manually setting JAVA_HOME to its own desired location, it's going to get ugly in my workspace.

    Java has been useful for large protocols and projects where programmers like to say "and then a miracle occurs" when they hand off processing to other programmers, but for performance sensitive, business critical, programs? I'm just not seeing the reason for it. And this particular field is suffering, badly, from having far too many "application servers".

    The one obvious advantage of JBoss is that it is LGPL. And that is not a small feature. But is it really needed? OK, so it has a Tomcat 5.5 component. Tomcat 6 has been out for years, and and Topmcat 5 should have been dropped about 2007.