Weblogic or JBoss? [closed]

I suspect the reason Weblogic gets chosen is a pleasant sales person comes to visit a manager with money to spend, gives him the sales pitch and hey-presto, the company is using Weblogic. I don't know if the JBoss support contract comes with a sales force, but would be surprised if it did and that the playing field has leveled in that respect.

In my experience, other than the pretty console you get with Weblogic (which isn't worth forking out the license fees for) there's not much between the 2. I suspect these days JBoss has market share (just guessing that), which in my book that translates into more help available online, etc when you're stuck on something.

It's also worth considering that the Weblogic licenses (last time I saw them) where the usual server-side terms - per-processor, per-box, etc. This will limit you in scalability terms because with JBoss you can keep adding hardware without occurring extra cost, while with Weblogic your licenses will need upgrading too.

Whichever you choose you're going to be able to build your system on top of them without too much trouble, but my preference would be JBoss.

I really like WebLogic. I'll suspend the licensing cost for the moment and just say that in their heyday they were the best Java EE app server on the market, hands down. BEA had a lot of extremely talented people developing their code, and it showed. If money was not part of the equation, and I had an employer that insisted on spending money that wasn't mine, I'd still choose WebLogic over WebSphere or JBOSS or Glassfish or anything else on the market.

I'm saddened by Oracle's purchase. I think that the talent has leaked away, and Oracle has no clear idea of what they want to do with WebLogic. They've been stuck on version 10.1 for a few years now.

    <prejudice-ahead>
Glassfish sounds like it's a much better effort from Sun, but their history says they write great standards and lousy implementations.  I don't consider Glassfish to be a viable alternative.
    </prejudice-ahead>

WebSphere is a typical IBM project: twice the cost, half the functionality, poor documentation, and you have to buy all their nonsense (e.g., Eclipse based IDEs) to use it.

JBOSS isn't bad, but only because the price difference is so strongly in its favor.

I'd rather recommend Spring, Tomcat and ActiveMQ as an excellent alternative. If EJBs are absolutely required, add OpenEJB to that mix.

2018 update: My affection for Java EE as a standard and its app server implementations has cooled in the last nine years. I think a better answer is to go with Spring Boot. Deploy an executable JAR on a JVM and never worry about a Java EE app server again.