Just 6 months after JBoss AS 6 was released, JBoss AS 7 (codename Lightning) is now available. Congratulations and a big thank you to the JBoss AS team and community. JBoss AS 7 is a major release in every respect and will become the technology underpinning for much of what we do at JBoss for the next decade. I believe it also represents a shift in the way developers will think about enterprise Java and it opens up new possibilities for deployment that were unthinkable 5 years ago due to technical and economic limitations.

If you’ve been following the AS 7 candidate releases (and AS 6 before it) then you already know that AS 7 includes some significant new features. I’m not going to list them all; but here are the highlights:

Developer Productivity

• Startup-time and memory utilization have been significantly reduced which leads to a much more productive developer experience – no more coffee breaks during deployments and restarts.This required some significant rethinking and a fair amount of innovation (something we’re good at apparently)
• The Java EE 6 Web Profile provides a much leaner, less complex platform for developers who focus purely on the web-tier – less to learn, fewer design choices – increased developer productivity
• More flexible and powerful modular classloader – less time debugging and configuring classpaths; more time writing applications
• Testable by Design with Arquillian with out of container testing for the business logic so developers can be more productive while delivering better quality applications.

Price / Performance

• It’s probably a little early to claim significant performance gain over the competition right now but request path performance is a goal and the hard work of tuning and performance improvements starts now, One early indicator will hopeful give you a sense of what we’d like to achieve is the recent SPECjms2007 submission from Red Hat. SPECjms is a pretty narrowly focussed benchmark and not all the JMS vendors are represented, that said this is pretty significant for us as it is the first public benchmark submission from JBoss and good practice for future activities

Operational Ease of Use

• Some of the more significant advances in JBoss AS 7 are around the operational ease of use. The configuration has been completely refactored around a multi-node domain model, though the simple single-instance view has been maintained for developer use as well
• There are stable, easy to use management APIs – so AS 7 deployments can be completely automated from Java or any other scripting environment.
• New shiny, task oriented domain console that also allows you to manage multiple, distributed nodes.

Anyway – time to stop reading and start playing : learn more about JBoss AS 7 here and get the bits here and provide feedback on community site.

Next post – how AS 7 relates to Red Hat’s commercial, fully supported distribution – JBoss Enterprise Application Platform 6.

So thanks for the opportunity to explain some of this.

First the obvious disclaimer – yes I work for Red Hat. Specifically I am the Director of Product Management for JBoss Enterprise Application Platforms and as such responsible for the product roadmap and technical direction of JBoss branded products like JBoss EWS, EAP and EWP.

So let me explain Red Hat’s model – something we call the Fedora / RHEL model internally. Red Hat provides subscriptions for use of its Enterprise distributions. A subscription provides the following (in no particular order) :

• long-term world-class technical support – and we do it very well (PDF report)
• long-term application compatibility
• long-term stability and predictability
• long-term partner certifications
• legal assurance
• long-term provision of security patches, performance enhancements bug fixes and RFEs

It may seem contrary if you’re used to the traditional model of “buying bits” but in our model, the provision of the bits is somewhat secondary; it’s something we have to do to support the value outlined above. For example, partners will only certify their applications and products if we have some way of identifying specific releases – supporting a continuous stream of releases is impractical. We can only provide application compatibility if we focus on specific identified releases.

So, one of the entitlements of a subscription is access to the supported binary distributions of a product – this is the thing to which we can apply all the other things I’ve outlined above.

For all of Red Hat’s products there are one or more upstream Open Source projects. In the case of JBoss EAP – the JBoss AS project is the primary components but JBoss EAP also includes Seam, mod_cluster, Apache CXF to name a few. Some of the projects that Red Hat uses in it commercial platforms are essentially Red Hat (or JBoss) projects – we provide the majority of developers, drive the roadmap and the release cadence (eg. JBoss AS, Seam, Hibernate), for others we’re merely one collaborator among many (eg. Apache CXF, OpenJDK, Apache HTTP).

The upstream Open Source projects is where the innovation happens – the focus of many of the Open Source projects driven by Red Hat is to act as technology incubators. Releases for projects like JBoss AS are frequent, experimental features are released, refined and re-released. That’s the focus – agility, speed, innovation. There’s never been any promise, implicit or otherwise that any given release is suitable for running your business critical applications. In fact we make it pretty clear on JBoss.org :

OK, so let’s dig into the relationship between project (or community) releases and platform releases. I’ll use JBoss AS (project) / JBoss EAP (platform) as examples as they are among the most widely downloaded / deployed :

Let’s take the JBoss AS 5 branch which was the foundation of the most recent JBoss EAP 5 family. JBoss AS 5 was focussed on a couple of big things : i) providing a new level of modularity via the Microcontainer 2.0; and ii) providing a Java EE 5 certified container. JBoss AS 5.0.1 was released in February 2009, followed a few months later by 5.1.0.

JBoss AS 5.1.0 met our functional criteria for JBoss EAP so that is what we picked up for our ‘productization’ process and JBoss AS 5.1.0 essentially became the Alpha Release for JBoss EAP 5.

The productization process is really not dissimilar to the kind of process you’d see in any other software company – we bring in all the major components, refine the dependencies, remove duplicates, perform additional testing above and beyond the community / project testing – focussing on security, performance, scalability, failure, longevity and the component integration points. We also look at documentation and the certification of third-party products like databases, Operating Systems, JVMs and other Application that work with JBoss. During this process we also run a traditional Early Access Program (aka Alpha, Beta) – this augments the attention the individual components receive during their own community release cycles. We’re fortunate to have some very willing customers who are able to apply significant resources to push our technology very hard using real-life applications and operational scenarios – often finding issues that are very hard to flush out in QE or during community release cycles.

The result of this process is an Enterprise Platform GA that differs from the upstream binary release we started with. First, we bundle additional components – like APR (Apache Portable run-time), Seam, mod_cluster, Apache CXF. And the core JBoss AS we include has a large number of fixes to address the security, performance and other issues identified during the productization process.

But that’s just the start.

JBoss EAP is supported for 7 years and with every additional minor or micro release we further improve the performance, security and stability of the Enterprise Platform. We’ve now released 2 micro and one minor release of JBoss EAP – that’s about 150 top-level issues in total. While the issue rate will slow over time – we’ll still be in a position to fix issues and respond to new security threats in 2016.

All those fixes are made available upstream and will ultimately make there way in to upstream binary releases but what the upstream project can’t guarantee is that those fixes will be isolated from more substantial changes and improvements – community releases typically don’t distinguish compatible bug fixes from more intrusive changes that provide the innovation.

OK so what happens to the community project once we’ve delivered an application platform? Well in the case of AS 5.0, from a Red Hat contributor perspective – the work was complete and Red Hat’s developers moved on to the next wave of innovation in AS 6 and AS 7. The goal of AS 6 is to deliver a Java EE 6 Web Profile implementation, the goal of AS 7 is to tackle the operational use-cases with a new domain model and console.

So to summarize this rather long post – if you want to deploy your business critical applications and receive long term support from Red Hat then the JBoss Enterprise Platforms are what I would recommend – if you’re more interested in seeing how those platforms will evolve and more interested in emerging technology but willing to take on more risk then upstream projects are where you should be looking. It all a matter of assessing the risk.

I’ve been a mostly happy OO user for the most part of the last decade (ever since my then employer – Sun acquired StarOffice) – it’s really been the only office application I’ve used consistently at home and at work and I’ve used it across many operating systems – Winders, many Linux variants and OS/X. I haven’t use the ‘other’ popular office suite for more than a decade.

But I have been grumbling more than usual lately about the various annoying bugs and inconsistencies and have moved a lot of my professional use to proprietary tools like OmniGraffle and Keynote. Even though I’d consider myself as an OO power user – OO is not just looking extremely dated but I find other tools on the Mac *way* more productive and that unfortunately trumps my desire to support Open Source.

I don’t think it will be long before I drop OO completely.

But maybe there’s a glimmer of hope. With Oracle’s takeover of the Open Office project (courtesy of Sun) and their clumsy handling of open source communities it seems there has been a mass defection from the Oracle controlled OO project to The Document Foundation. Maybe this is the kind of shake-up the OO needs – here’s hoping.

Apparently it was Apache Web Server’s 15th birthday yesterday – congratulations to anyone who’s ever been involved in the project. I doubt any would have thought that 15 years on, Apache would have become the dominant Web Server on the Web and the foundation of one of the most successful and recognized Open Source forges. For a history of the Apache Web Server and the Apache Software Foundation, head over to the ASF Blog.

Red Hat has been a supporter of Apache Web Server for a long time and has shipped and supported a version in its Red Hat Enterprise Linux for as long as I’ve been noodling with it. Last year we started shipping a standalone, multi-platform distribution as well – JBoss Enterprise Web Server. Earlier today we released the latest version of it and expanded our support for Apache HTTP Server to 14 different Operating System / architecture combinations. The exact component versions are listed here and there’s more information in the Release Notes. If you’re deploying Apache HTTP or Tomcat at scale – Red Hat also supports management of Apache HTTP Server and Tomcat alongside all JBoss products via JBoss Operations Network.

The JBoss AS team moved to a more rapid and incremental release cycle with the 6.x family and the second milestone was released today (release notes, download, repo.). The release was lead by Brian Stansberry and new features include :

• Servlet 3.0 / JBoss Web 3.0
• JPA 2.0 / Hibernate 3.5
• JAX-RS 1.0 / RESTEasy 2.0
• Microcontainer 2.2

More detail in blogs from Ales, Brian, Steve and Rémy. Congratulations to Brian on another on-time release and good luck to Jason and team for the next milestone release in a couple of months time.

Zallinger’s “March of Progress” from wikipedia.

I’ve been part of the Java ecosystem for long enough to see and be part of every Java EE / J2EE release to date. I still have a Forte SynerJ box-set somewhere – we claimed it as the first fully integrated J2EE 1.2 App Server and IDE – that was around 1999 and I was part of Sun for every subsequent release up to Java EE 5.

With the final votes in for Java EE 6 and with the year and decade coming to an end – it seems a fitting time to look back and see how far the Java EE platform has evolved :

• J2EE 1.2 (1999) – announced just short of 10 years ago was the first attempt to create an umberalla specification to cover some existing web-tier, messaging and data access technologies (JDBC, Servlets, JTA, etc.) as well as the new middle tier technology – EJBs.
• J2EE 1.3 (2001) – was from my recollection the first broadly adopted and deployed version, it added Connectors (a standard way to connect to back-end ‘legacy’ systems), some rudimentary support for XML Web Services and a pluggable security layer. EJBs got a major overhaul.
• J2EE 1.4 (2003) – added JMX, a gaggle of specs. to support Web Services (JAXR, JAX-RPC). I think around this time – everyone had written their first App. using EJB’s and had learned that combined with CMP (Container Managed Persistence) they weren’t exactly getting the productivity boost they were hoping for. I think J2EE 1.4 was the “Vista” of Enterprise Java – over-engineered and ultimately underwhelming.
• Java EE 5 (2006) – A name change and some new hope – mandatory XML deployment descriptors gave way to annotations, persistence took a lesson from the de-facto ORM solution – Hibernate. There was an alternative to, ahem, RPC-style Web Services with the inclusion of JAX-WS.
• Java EE 6 (2009) – It’s been a while in the making and had a bad start but after ten years I think we now really see the start of a cohesive platform with a common programming model via CDI (JSR-299) and many of the criticisms leveled at the platform have been answered.

Java EE 6 also defines the new Web Profile – this is essentially a slimmed-down EE focussed on web applications. I think it’s much more than that – I think it’s an opportunity to really redefine the Enterprise Java platform and shed some of the legacy APIs. While the backward compatibility that EE dictates has been good – it’s also contributed to some bloat in the platform.

It’s interesting to see how the size of the Java EE spec. has changed over the years (assuming size of the spec. is a reasonable indicator of complexity)

• J2EE 1.2 weighed in at just 140 pages;
• J2EE 1.3 added about another 25% (174 pages);
• J2EE 1.4 increased it by almost 40% (246 pages)
• Java EE 5 actually bought the page count down by 10%;
• and the last draft of the Java EE 6 spec. I read only added about 6% (236 pages) – despite some pretty major enhancements.

Despite several rounds of consolidation and various acquisitions – vendor support has remained impressive. There were 18 J2EE 1.2 certified servers, and even seven years later there were still 13 (for Java EE 5). I’d be surprised if there weren’t at least 10 vendors supporting Java EE 6 at some point – even after Oracle has assimilated BEA and Sun.

Despite its huge adoption, Java EE and the process by which it is defined (the JCP) has drawn a lot of criticism. Releases have often fallen short of expectations, been perceived as overly complex or taken too long to deliver; but despite the criticisms nobody can deny that Java EE has been a huge success. Java EE is not just a specification – its grown into an entire category of the software industry. I can think of no other technology that has bought so many competing vendors together to define such a broad and widely use platform.

I’m sure the JCP isn’t perfect and I’m sure vendor politics gets in the way of progress from time to time and Sun’s stewardship of Java hasn’t been flawless but step back and try to imagine what our industry would be like without an open and collaborative Java ecosystem. It will be interesting to see whether Oracle take a different approach (as they’ve suggested in the past) when they become the new stewards of Java. Let’s hope hey continue to encourage collaboration and diversity.

The various expert groups that define the Java platform is not, as many suggest, completely controlled by big vendors. My own company Red Hat is not an industry behemoth, there are divisions and offices within companies like IBM and Oracle that are bigger than Red Hat and JBoss, the middleware business unit of Red Hat is only a part of the entire company. Despite that – Red Hat has demonstrated yet again it’s willingness to punch way above it’s weight and has had an influence on Java EE disproportionate to it’s size. Congratulations to Gavin King, Pete Muir, Sacha Labourey. Emmanuel Bernard, etc for tirelessly pushing for simplicity in the EE platform.

JBoss AS 6 Milestone 1 is out and includes some of the key Java EE 6 features. Releases seem to be coming pretty frequently so you’ll see more EE 6 feature appearing over time.

• Open Source is mainstream and it’s being used extensively to support customer facing, business and mission critical functions.
• Reduced TCO and no up-front license cost are still the major drivers for open source adoption but they’re closely followed by - vendor independence (and specifically MS independence), Quality, Innovation and Convenience / Flexibility. Or as Forrester [1] put it “OSS isn’t just cheap – it’s good and cheap”.
• The main inhibitors to adoption – ‘security’ and ‘lack of support’ and risk of patent / copyright infringement seem to be much less of a concern than a year ago. The suggestion seems to be that these risks are offset by working with commercial open source vendors or experienced System Integrators.
• The rate of Open Source adoption differs between categories of software – Application Development, Server OSes, Databases and Middleware have high adoption whereas Reporting / BI, SOA, Desktop and Security – adoption is much lower but adoption is moving rapidly up the stack.
• North America and Canada are  still behind Europe (excluding the UK) in adopting OSS; adoption is higher in larger organizations; and different industries are adopting OSS at different rates for different areas in the stack.
• Technology isn’t the only thing being adopted – principles and governance of open source is also being adopted in IT and development organizations. This is something I’ve already witnessed a few times.

OK, a little bit more detail from each of the reports.

The first report was prepared for Bull by Forrester [1], and specifically focusses on European and North American companies who have already adopted OSS. I especially like the following, so forgive the repetition :

OSS isn’t just cheap — it’s good and cheap. Only a minority of respondents said that OSS hasn’t met their quality expectations. A vast majority (i.e., 92%) said that their quality expectations have been met or even exceeded. The satisfaction regarding cost was on a similar level at 87%.”

The second report is Actuate’s annual Open Source survey [2]

I’ve only read the North American report and a I presume there’s more detail specific to France, UK and Germany. The report drills down into established open source technologies – Linux, Eclipse, Tomcat and JBoss and it’s nice to see JBoss included along with other Open Source mega-brands like Apache, Linux, MySQL and Eclipse . JBoss adoption in North America is 14.7% and Germany 22.1%  but in France it’s much lower at only 5.7% – while other technologies remain pretty constant. Any thoughts as to why JBoss adoption is so much lower in France or whether this is a bug in the survey  ?

The third and fourth tomes are from IDC [3,4] The first part outlines the key drivers and inhibitors to the adoption of Open Source.  The second part has some very nice detail on how open source technology is ‘acquired’ and how it’s supported and serviced. It demonstrates how a tiny little company called  Red Hat has managed to compete with and in many cases lead some much more established (ie. older) and significantly larger companies in the distribution and support of Open Source technology. That said – you can’t help but accept that without huge companies like IBM, Oracle and HP – distributing and supporing Open Source technology – it wouldn’t be as successful or as established as it is today.

As I keep saying – money makes the world go round and that’s true for the world of Open Source too.

[1] Open Source Paves The Way For The Next Generation Of Enterprise IT, Forrester Consulting, November 2008

[2] ACTUATE / Survey Interactive :Annual Open Source Survey, North America Edition, 2008

[3] IDC 2008 Industry Adoption of Open Source Software, Part 1 : Usage Drivers and Inhibitors

[4] IDC 2008 Industry Adoption of Open Source Software, Part 2 : Project Adoption

And that, so I’ve been told, was a guiding principal behind the re-architecture of JBoss AS 5.0.0 which was released last week. We don’t know what kinds of applications and services people will be deploying in five years time; we don’t know what frameworks, languages or programming models they’ll be using but we do know that they’ll need to access some ‘core services’ such as data-access, transactions, caching, clustering, messaging, deployment, management, monitoring, etc. And we know we need a modular and flexible core to bind those services together in ways that make sense for the languages and programming paradigms and deployment topologies of the future.

We also know that a single monolithic developer platform for all applications and all customer workloads is not going to be sufficient. At the same time inflicting multiple platforms on the operations organizations who are responsible for the 90% of the application lifecycle that isn’t development is also unreasonable. The operations people see the platform very differently from developers – they don’t want to a new operational footprint everytime a new framework or language comes along – they want stability and consistency.

If this all sounds like vacuous marketing drivel – let’s take a real-life lucid example. Bob McWhirter has been integrating Rails and JBoss using the power of the AS 5 architecture. He’s written some custom deployers, created some shims and a little glue code to integrate existing services and the results are pretty interesting. A powerful Rails environment – without too many compromises for the Ruby developer yet at the same time something that the operations people will be happy with too – ie. a standard JBoss run-time that behaves just like the other JBoss deployments whether they’re Java EE / Seam based or Spring or POJOs. And check out the “web” configuration – another example of what’s not only possible but actually pretty straightforward to acheive with the Microcontainer and modularized services in AS 5.

I think the next couple of years will demonstrate that AS 5.0 has been a wise investment as other vendors will struggle to retool and stretch their run-times to meet customer demands for increased choice and flexibility.

Seam 2.1 was released a couple of weeks ago and in fact there’s already an update (Seam 2.1.0 SP1). Major updates in Seam 2.1 are :

identity management framework with ACL style permissions, an Excel reporting module, an embellished and more flexible seam-gen, first class support for Wicket, built-in support for URL rewriting and a technology preview of JAX-RS (REST) support through the RESTeasy project.

The really big news last week was that JBoss ON (Operation Network) has finally been open sourced as the Jopr project (I’m trying to like the name – honest). JBoss ON is a sophisticated management platform for the JBoss Middleware stack and it’s based on Project RHQ (A collaboration between Red Hat and Hyperic).

There’s a subproject of Jopr called Embedded Jopr which is the basis of the new console for JBoss App Server – this is a significant improvement over the current Web Console and JMX Console and should be a welcome addition to users who are familiar with IBM WAS and Oracle WLS. This first version only suport JBoss AS 4.2 (ie. EAP 4.3) but work is underway to support AS 5.0.

I’d recommend downloading and having a quick play – it takes just a few minutes to get up and running (even for me).  If you don’t have the time there are some screenshots and a short (15 min) video here. There’s also more detail on Ian Springers blog.