congratulations for your great book "JBoss in Action" . It helps a lot to initially get into JBoss AS, for beginners as well as "migrators" like me.
But I have a question.
my company competes against product offerings from Oracle. Currently we try to beat WebLogic Server with a JBoss application server infrastructure. Next to the fact, that JBoss has virtually no licensing costs, what feature-driven arguments (unlike "big community", "no costs", etc.) could we bring against Oracle WebLogic?
WebLogic offers a lot more implementation details and has more or less all feature implemented we have at the JBoss community wishlist:
Are there any features which are truely unique for JBoss AS5 and can't be found in other commercial products like WebLogic? Just to give some more ideas, what I'm targeting on. One really cool JBoss feature is to remove unwanted/unused services like:
* mail service
* http invoker
and so on. In contrast, the WebLogic mSA only supports to modes WLX and WLS:
* WLS: EJB, JMS, Connector, Clustering, Deployment, Management, and Diagnostics
* WLX: The Services EJB, JMS & JCA are NOT loaded
so the JBoss microcontainer, truley allows finer control of core components.
I'm pretty sure there are some features in JBoss which commercial tools do not offer. However, it's pretty tedious to find some nice feature of JBoss always in WebLogic manuals.
I'm sorry, but it has been many years since I have used WLS so I cannot offer a comparison between it an JBoss AS. The best I can offer is to read chapter 1 and from there compare JBoss AS with what you know about WLS. A google search might yield other opinions. But usually the price and its open source-ness are the top selling points.
many thanks for your comments. It's hard to find people which are as deep in both products. but the fact, that I can't find people who can name me "superior features" is maybe also a sign, that JBoss more or less tries to follow up commercial offerings. I'm not opening a OSS vs. payware discussion here, but comparing JBoss and its functionality does not really highlight many unique "selling points". Unfortunately.
Honestly, for me as an end user or a developer using JBoss AS or any other application server, instead of looking for "superior features" in those products, i would first look at what my application needs and then see which one provides those features and which one provides it in a better way. So what exactly does your application need? And are you looking for better features as an developer or as an end user?
Jaikiran Pai wrote:Honestly, for me as an end user or a developer ...
that's an excellent point. Of course application needs are first. Unfortunately I often saw that decisions on the JEE infrastructure are made first, without respecting the actual requirements of the application. All that is sooo typical especially in large enterprises, where statements like "it costs nothing, it can't be as good" are floating around.
I'm looking for features adressing these roles: developer, operations as well as business people (I think you mean that by "end user"?).
It's not really useful to compare products at the JEE specification-implementation level. It only makes sense to compare products at their "implementation details"-level as well as added-value in terms of efficiency or innovation. I thought about 7 groups where I would expect features, which are distinct enough to really characterize JEE middleware products. So basically what I'm looking for are features in these categories:
1) developers productivity (role: dev)
2) server configuration and deployment (role: oam)
3) monitoring and analyses (role: oam)
4) troubleshooting and tuning (role: oam, dev)
5) integration (middleware) connectivity (role: oam, dev, business)
6) scaling and high availability (role: oam and business)
I don't want to break down each group, but in-a-short the only value-add features I can see for JBoss are in 1) (JBoss IDE, Plugins) and maybe in 4) (microcontainer, transparency).
Thomas Havemeister wrote:but in-a-short the only value-add features I can see for JBoss are in 1) (JBoss IDE, Plugins) and maybe in 4) (microcontainer, transparency).
Do you see more?
I would add #2 - server configuration and deployment, too to that list since its way too simple to do that on JBoss AS. But yes, it again depends on your preference. I have been using JBoss since its 3.x version and i find it easy to change some xml files or configurations to get the server configuration/deployment done. I consider this easy. However, for someone who likes a more UI approach, then JBoss did not have an inbuilt admin console until recently. But with the recent release of JBossAS 5.1.0 CR1, it now has an admin console too (i must note that, this admin console is a plain web application which was compatible with JBossAS-4.2.x too, but wasn't shipped by default).
For #3, i have heard about JON which actually is a paid product and suitable for production environments.