Congratulations to the whole AS team on the release of version 6! JBoss AS 6 is a Java EE 6 compliant application server, so it includes built-in support for many of the technologies we talk about here: CDI, JPA 2, Bean Validation, EJB 3.1, JSF 2.0, Servlets 3.0, along with many major enhancements in other areas.

29. Dec 2010, 19:33 CET | Link

Congratulations! :)

I hope JBoss 6 will also soon appear on the Oracle Java EE Compatibility page:

29. Dec 2010, 20:19 CET | Link

As a side note, I'm also happy to announce in behalf of the whole Codehaus CARGO team that CARGO includes complete support for JBoss 6 Final, see the details on ... For those who don't now, Codehaus CARGO is a thin wrapper that allows you to manipulate Java EE containers in a standard way; available as a free open source project, independent of any Java EE server vendor.

You can indeed use CARGO in order to:

Launch integration tests of your existing Java EE applications on JBoss 6 Compare the behavior of your Java EE applications on JBoss 5.x and 6 Remotely deploy your applications on JBoss 6 servers (be it clustered or not) Cargo provides the following Tools and APIs: A Java API to start/stop/configure Java Containers and deploy modules into them A Java API to parse/create/merge Java EE Modules Ant tasks, Maven 1, Maven 2 plugins

Give a try:

31. Dec 2010, 11:31 CET | Link

Odd that JBoss AS 6 is going final with one of the core components still being at CR1 status i.e. Weld 1.1 .

Regardless, its great to see another Java EE 6 application server out in the wild.

31. Dec 2010, 11:54 CET | Link
Peter wrote on Dec 31, 2010 05:31:
Odd that JBoss AS 6 is going final with one of the core components still being at CR1 status i.e. Weld 1.1 .

There were two (linked) factors which drove this decision

  1. Weld targets multiple runtime environments (JBoss AS, GlassFish, Tomcat, Jetty, GAE, Java SE), and so whilst CR1 works well in JBoss AS there were still some issues to iron out for GlassFish (mainly due to the different approaches to classloading and the way Java EE injection is performed)
  2. JBoss AS6 targets the web profile, whilst GlassFish V3.1 targets the full full profile, so the criteria for including a Weld release are somewhat different.

I agree this wasn't an ideal situation, but given the very close releases of AS6 and GlassFish V3.1 (about 2 weeks apart) there was no real way around it :-(

07. Jan 2011, 10:57 CET | Link


We are evaluating migrate to JBoss-6 from JBoss-4.2 but we found the Metro Web Service Stack is not avaliable in JBoss-6. Now, the web service stack is based in Apache CFX.

How can he use the Metro Web Service Stack in JBoss-6? It can be used?

Any help or comment will be very appreciated.

08. Jan 2011, 15:51 CET | Link
Ales Justin