Since it first started as a small grassroots open source project in the late nineties, JBoss AS has come a long way. It is now one of the foremost open source Java EE application servers, if not one of the leading application servers outright. JBoss AS has always been vital to fulfilling the Java EE promise of choice, vendor neutrality and portability alongside the likes of Java steward Oracle’s own GlassFish and WebLogic. Throughout the years, the JBoss community has had strong contributions to Java EE itself, including to the EJB 3, JPA, CDI, Bean Validation, JAX-RS and JSF specifications.
Now JBoss AS is being renamed to WildFly. The renaming is essentially an effort to distinguish the open source, community version of JBoss AS from JBoss EAP (JBoss Enterprise Application Platform/JBoss Enterprise Middleware), the commercial offering from Red Hat.
The renamed application server already has its’ own launch page. The project retains the JBoss AS focus on Java EE (WildFly 8 is aimed at Java EE 7), lightweight development, innovation and community. We can all wish WildFly all the best and hope it continues to be a driving force behind the Java EE community.
All views voiced are my own, not necessarily Oracle’s.