Tab Sweep : JBoss

From the “release early and often” files :

JBoss Messaging 2.0 beta is out. According to JBM lead, Tim Fox – New features include, performance, performance, performance, flexible clustering, seamless high-availability, large message support. See Tim’s announcement for details.

Thomas Diesler has some thoughts on how the JBoss Microcontainer could fully implement the OSGi spec. It will be interesting to see the results of this and it will be a great example of the power and flexibility of the JBoss architecture. JBossOSGi 1.0.0 Beta2 was released last week.

If you are eager to try out Eclipse 3.5 / Galileo and want to explor the upcoming features in JBoss Tools / JBDS you now can – JBoss Tools 3.1.0.M1 is available. See what’s new and noteworthy.

The recently released Seam 2.1.2 includes improved support for JAX-RS (RESTful web services) – more details here.

Finally, we have a free online seminar tomorrow (June 10th) at 9am EDT, 3pm CEST which covers Web Beans (JSR-299 / JCDI – Java Contexts and Dependency Injection). More details here.

Final thoughts on JavaOne 2009

As expected, JavaOne was interesting. For the first time in 12 years I actually attended more than a couple of sessions; but that isn’t why it was interesting. It was interesting because we witnessed the ceremonial passing of the Java One torch from Sun to Oracle and a fairly public goodbye from Schwartz and McNealy.

By all standards it was a pretty lightly attended Java One – I expected it to be a lot lighter given the economy, the uncertainty around Java and the Bacon Fever – so I was actually pleasantly surprised. Outside of Sun itself – I think JBoss was probably the largest software vendor on the pavilion floor – that says something.

Despite the low attendance overall – we had very solid attendance at our mini-theatre sessions – I think ours was one of the few booths that drew a crowd (without having to give stuff away) – so all in all it was a good show for us.

I’d be very surprised if this wasn’t the the last Java One; and as the crews started dismantling the pavilion – I felt like I should be trying to rip down a sign or banner – some memento to remind me of the fun times I’ve had at Java One over the years.

A lot of people were questioning the future of Java at the show (as usual) but I still firmly believe it’s going to be safe enough for the next 20 or 30 years – more than long enough for most of us. I don’t think Oracle will do anything stupid; though given the size and complexity of Sun I think they’re bound to make mistakes – it’s up to us to tell them when they do and to help resolve them.

As anyone who knows Java One – it’s about the people you meet – not the content. And so it is with Java – it’s about the people / community / ecosystem – at the end of the day – no single company has really owned Java for a long time.

Update : My pictures and Marek Goldmann’s pictures on Flickr.

JBoss Open Choice

Earlier this week we announced a couple of things. First, a change in our platform strategy, second some new products to implement that strategy. We felt we had to give that strategy a name and “Open Choice”, while unoriginal, best illustrated what we’re doing. And what we’re doing is expanding our support to include Open Source technologies  beyond what we’ve typically supported and beyond the JBoss constellation.

This is a reaction to a) customer demand; and b) the realization that not all the cool stuff is created by JBoss. What we’re also doing is reacting to market demand. Java EE, while hugely successful is not the only game in town any more.

j2ee-spring1

We want to ensure that our customers get to choose whatever frameworks, languages, development models they want without causing major disruption for the operations people who have to manage the applications for the other 90% of the application lifecyle (ie. outside development). We also want to remove the risk of deploying new developer oriented tech. by providing a stable, consistent operational footprint (JBoss) to run the resulting apps.

Note – I normally don’t use Job Trends data in isolation to make serious decisions, but it’s convenient and lazy way to find what keywords are trending.

So yes, this is a reactive move; we’re reacting to customer demand and market pressure – we’re really not reacting to anything that Spring Source is doing. I’ll post another blog explaining what we’re including in our Web Framework Kit and why; but Spring Framework is included for much the same reason as struts – they’re mature technologies and both are very widely deployed :

spring-struts

It’s no secret that a big chunk of our business comes from our much larger but less nimble competitors and we have to ensure that migration is a simple and low risk proposition.

spring

As the chart shows (if you have any faith in the data) – Spring Framework usage is fairly evenly distributed across the Java container landscape. By making JBoss a better place to run Spring (among other things) – I believe that we can change this landscape dramatically.

This really isn’t about Spring Source – in fact we don’t even compete with Spring Source. Our sights are set much higher.

New – JBoss MASS – Migration Analysis Tool

jbossmass_logo_450px

It’s been just over 3 months since we created the JBoss MASS project and today we’re announcing the first major code contribution – The Migration Analysis Tool (MAT) was created by Mitch Mocle and team at Middleware Connections. The tool is used as a starting point for estimating the effort required to migrate a group of J2EE applications  from an Oracle/BEA WebLogic environment to a JBoss AS / JBoss EAP environment.

The tool produces detailed HTML reports covering Server Configuration, Deployed Applications and Class Dependencies. Read More on the MAT sub-project page.

This is an important first step. The goal of JBoss MASS is to provide a common place to develop tools for migrating to JBoss – if you have or are thinking of developing such a tool and think that Open Source collaboration might be a good way to enhance and maintain the technology – get in touch.

Tab Sweep : JBoss Mostly

Over the last ten years – every year has been proclaimed the year that Java dies. And every year people are proven wrong and I think that will continue to happen for another 20 or 30 years. To put it into perspective COBOL, another fairly sucessful language is 50 (fifty) years old this month. Other popular langauges : C – 37 years old, C++ – 26 years old, Java – a mere 14 years old. People are still running and maintaining COBOL, ditto C, C++, etc. These popular languages have taken decades to reach mainstream adoption and will be viable for decades to come.

JBoss AS 5.1 GA has been released. Downloads are looking pretty healthy and it’s good to see almost monthly releases now that the MC / re-architecture work is behind us. Release early, release often

It’s Java One time again, JBoss’ presence this year will probably be larger than last year – we have a lot to talk about and show – so swing by our sessions, our booths and join us at the JBoss Party. See you there – and follow @JBossNews on twitter for the latest Java One updates.

Sun seem to be getting increasingly desperate to build a business around their Java middleware – they’re attacking companies a fraction of a fraction of their size and continuing the fire sale. It’s going to be really interesting when Sun product lines get hit with Larry Ellison’s “fiduciary responsibility” stick. Weblogic wasn’t exactly cheap – and Oracle had to pile on a pretty hefty Tax to bring it in line with Oracle’s cost model. The disparity between Sun and Oracle pricing is *huge* and is going to require something more dramatic than a a mere 30% price increase.

Although Java One hasn’t started yet – for all the folks involved in planning and preparing – the work is (or should be) done. At Red Hat we already have our sight on the biggest Red Hat / JBoss event of the year – the co-located Red Hat Summit and JBoss World 2009 which is in Chicago, Septemer 1st to 4th.

2 Days in Provence

IMG_0257

Last week I spent a couple of days in Provence visting a (potential) customer. I stayed in the little village of Cassis to be precise; which is a pleasant little place though a bit of a tourist trap (ie. expensive but only half-decent food). If I’d been a bit more prepared I would have taken a real camera but unfortunately only had my iPhone (pictures on Flickr).

Among the things I learned on this trip i) never transit through Philly again; ii) if you want medium-rare in Provence you have to insist on “burnt to a crisp” anything below that is just raw meat; iii) raw meat doesn’t agree with me; nor me with it; iv) The Mediteranean has Fjords; only they’re made from limestone and called Calanques.

Truth happens

If you wander around any of Red Hat’s offices you might see this quote from Mahatma Gandhi :

“First they ignore you, then they laugh at you, then they fight you, then you win.” Or you may have seen this (exceptionally cool) video at one of our conferences :

Of course Gandhi wasn’t talking about JBoss or Red Hat or Open Source – but the quote is still very relevant to a company that has revolutionized the software industry. People and companies who once ignored or laughed at Linux, or JBoss’ original EJB server are now waking up to the reality that they are losing.

Given the recent presentations that JBoss’ only real competitors (IBM and Oracle) have been spreading around and the amount of work and energy they’re both expending to compete with JBoss – I think JBoss has reached a significant milestone – I think we’re at stage 3 of Gandhi’s steps to oppose the truth  – ” … then they fight you …”.

It’s flattering and inspiring to know that two companies who are literally hundreds of times the size of Red Hat are worried. Really worried. It also adds a huge amount of credibility to our business model and our technology.

What’s next ?

Tab Sweep : JBoss

Another couple of super-busy months here at JBoss. If anything the pace of new releases and new projects is increasing. Here are some of the more prominent Community announcements I managed to bookmark :

JBoss App Server 5.1.0 CR1 – 5.1 is a pretty big milestone – it includes the new Jopr powered embedded console  – something you’ll like but also something we really need some early feedback on. Also a preview of Web Beans / JSR-299. [release notes, downloads]

Data Integration goes Open Source – I missed the launch of the Teiid Project you can find out more on the project page.

This has been brewing for a while and Manik has finally announced Infinispan – I predict that this is going to  be a pretty disruptive technology. [home page, quick guide]

JBoss Tattletale is a new tool that will analyze your code and produce detailed dependency reports – for example highlighting duplicate jars / classes, missing jars / classes, etc. [downloads, project]

The latest release of Jopr (2.2) is out – Jopr is the upstream project for JBoss Operations Network (see below). There are a shedload of UI enhancements, support for JBoss EWS and Performance improvements among other things.

Also a nice article on JBoss Cloud over on DZone.

On the JBoss Enterprise side of the house :

JBoss Operations Network 2.2 is out and JON receives a pretty decent makeover (see Greg’s post on some of the major enhancements) – product page is here.

One of the new capabilities of JON 2.2 is support for JBoss Enterprise Web Server (EWS) which was also released a few weeks ago – more on that in a future post.

If you’re currently stuck with Oracle Weblogic or IBM Websphere and need help getting off – here’s an opportunity you can’t ignore.

Sorry for the length of this post – I need to do this more frequently. The next couple of months are going to be even more hectic and you can follow the @JBossNews via Twitter. Finally, something from the happy news files – we’re still hiring.

Snoracle

I’d like to think of myself as an informed prognosticator having worked for Sun for almost 9 years; but this is prognostication nonetheless. I missed my chance to say what I thought of an IBM acquisition but I’ll start by saying – I think I preferred it – it probably would’ve been a better outcome for the things I care about.

The things I care about are the people I know who still work for Sun, the Java ecosystem, and many of Sun’s Open Source projects that I directly or indirectly benefit from – specifically MySQL (this post will live in MySQL), OpenJDK and OpenOffice.

It still seems like a strange merger – sure, Sun and Oracle have a huge shared installed based – Sun Servers + Solaris + BEA + Oracle DBMS was the killer enterprise stack for a decade – that alone gives Oracle a vice-like grip on existing customers; but that’s about the past – not the future. I think someone did the analysis and realized it’s a marginally positive move – so I don’t think this is the big technology vision realized that Oracle are trying to promote.

I’m sure a lot of people at Sun and customers of Sun are glad the uncertainty has come to an end but unfortunately it hasn’t. I’m guessing that it will take until the end of the year before Oracle tells the world what they’re keeping and what they’re dropping. FWIW – here’s my informed guess :

Storage / Servers – the press-briefing made the merger sound like it was all about the hardware (servers and storage). I just don’t see Oracle as a hardware company and they have more to loose than gain by pissing HP off. I wouldn’t be at all surprised if some or all the hardware got sold off to HP, Fujitsu, etc. And I think Oracle could probably recover $3.5-4 bn of their $5bn outlay by doing so.

NetBeansI’m not changing my mind – it’s done for. Oracle has two Java IDEs already – they don’t need a third. Oracle will pick up some great tools developers to write a migration tool but that’s about it.

OpenOffice – Oracle doesn’t like M$ but I doubt they can find a fiscally rational reason to carry the torch for Open Source and at the end of the day Oracle are doing this because it makes financial sense. I think Oracle will expect “the community” to pick up the slack.

Solaris – I think they’ll milk the legacy installed base (which is huge) but the innovation won’t continue. I think there’s an interesting opportunity for Oracle to manage the migration of the last of the Solaris holdouts to Linux. They could do this by GPLing Solaris and moving some of the Solaris features to Linux; or more likely to an Oracle proprietary OS built on Linux.

Middleware – Oracle have everything Sun has – and Oracle are by and large market leaders with large market and revenue share. Sun have one or two products that might survive and certainly some components. Oracle inherit a commitment to continue to produce the Java EE RI (and others) so Glassfish *might* survive – but Oracle have demonstrated that they don’t have appetite to maintain many products in the same market (see how quickly OC4J got killed after the BEA acquisition ?)

MySQL – I think Oracle will continue to do what Sun did somewhat accidentally – namely slowly kill it off.

Java – I’m confident that Oracle won’t fix the JCP and won’t sacrifice control for the good of the ecosystem. I also think the JCP will become a battlefield for IBM and Oracle and we’ll all be the worse for it.

OpenJDK – no-body needs two JDK’s to maintain – I think Oracle would have to move some of the monitoring / diagnostics from JRockit into a proprietary OpenJDK-based platform. JRockit has a small market share but some nice features for enterprise customers.

Cloud – not that there’s much there there but I don’t expect to see Larry eating his words.

Virtualization – I don’t really understand Oracle’s virtualization strategy other than the feeling that Larry Ellison is unlikely to entertain anything that looks like it might actually save customers money on licenses.

Spring

Spring happens pretty quickly in North Carolina; it arrives overnight and is over in a month. The speed at which everything bursts into life is incredible. So, yet again I’m a little late updating this blog’s header image.

Mainly for my own purposes – the images I use for the header are in this Fickr Set. The Spring image is a close up of a Japanese Maple in our front garden waking up after Winter.

See also Autumn and Winter (I never got around to Summer last year – this year maybe).