Enterprise Web Platform 5.0 Completes the JBoss Open Choice Trinity

DZone 's Guide to

Enterprise Web Platform 5.0 Completes the JBoss Open Choice Trinity

· Agile Zone ·
Free Resource

Today at EclipseCon, Red Hat announced the general availability of the third and final piece of the JBoss Open Choice strategy.  The newly released JBoss Enterprise Web Platform 5.0 joins the JBoss Enterprise Web Server and the JBoss Enterprise Application Platform in JBoss' mission to provide a modern application architecture that supports multiple Java frameworks, runtimes, and programming models.

The following Java application server products comprise the Open Choice strategy:

  • JBoss Enterprise Application Platform - for highly transactional Java EE applications
  • JBoss Enterprise Web Platform - for mid-sized, light and rich Java applications
  • JBoss Enterprise Web Server - for simple Java workloads that only require enterprise Apache Tomcat.

JBoss Enterprise Web Platform 5.0
The JBoss Enterprise Web Platform 5.0 implements the Java EE 6 Web Profile (inculdes CDI, JTA, JPA2, EJB 3.1 lite, Bean validation, managed beans, interceptors, JSF 2, Facelet, JSP, and Servlet 3) for a lightweight enterprise version of the JBoss Application Server.  The platform includes updated support for caching, clustering, high availability, REST, and basic web services (JAX-RS).  The platform also comes with the JBoss Web Framework Kit, which provides enterprise support for Google Web Toolkit, RichFaces, Apache Struts, and Spring Framework.

Motivations Behind the Open Choice Strategy
A blog post by Rich Sharple, the Director of Product Management for JBoss Application Platforms and Developer Tools, explains the motivations behind the Open Choice strategy:  "IT enterprises no longer use a single Java programming model."  Sharple said that JBoss chose to expand and improve its support for other open source technologies because of customer demand and due to "the realization that not all the cool stuff is created by JBoss."  The Spring Framework is a particular point of focus for JBoss.  "By making JBoss a better place to run Spring (among other things) – I believe that we can change this landscape dramatically," said Sharple.  With the Open Choice trinity, "customers get to choose whatever frameworks, languages, and 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)."

JBoss Microcontainer
Underneath each of the products in the Open Choice strategy is the JBoss Microcontainer, which is a refactoring of JBoss' JMX Microkernel.  The JBoss Microcontainer includes:

    •    All the features of the JMX Microkernel
    •    Direct POJO deployment (no need for Standard/XMBean or MBeanProxy)
    •    Direct IOC style dependency injection
    •    Improved lifecycle management
    •    Additional control over dependencies
    •    Transparent AOP integration
    •    Virtual File System
    •    Virtual Deployment Framework
    •    OSGi classloading

The JBoss Open Choice application platform product strategy leverages the JBoss Microcontainer to provide a single application platform core that gives developers the same set of common enterprise services for reliability, scalability, security and management, regardless of the selected programming model.  The Microcontainer's flexible, service-based architecture provides a consistent and modular series of enterprise deployment features for clustering, caching, transactions, web services, security and more.  The architecture will support these features for a variety of popular programing styles and frameworks, including POJOs, Java EE, the Spring Framework, OSGi, and RIA frameworks.

Red Hat also announced the simultaneous release of JBoss Developer Studio 3.0 and JBoss Enterprise SOA Platform 5.0 yesterday.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}