May 11 saw JBoss release JBoss AS 4.2.0, which integrates many (if not all?) components for Java EE development into the JBoss AS 4.x line. From the announcement:

New features in JBoss AS 4.2 include:

• Tomcat 6.0, which adds support for JSP 2.1 and Servlet 2.5
• JavaServer Faces 1.2 integration
• JBoss Transactions (Arjuna) JTA 4.2.3 as the default transaction monitor
• The latest Enterprise JavaBeans (EJB) 3.0 implementation
• Support for Hibernate 3.2.3

Apologies for the late notice! Chances are that the JBoss folks told me while I was there, and I was so caught up with everything else that it just slid under the stack of things to do.

I didn't understand this choice of Jboss group! Why did they add J2EE 1.5 specs implementation into JBoss 4.2 if they've just released JBoss 5.0.0 Beta2? Should not JBoss 5.0 be the first and only J2EE 1.5 specs implementation?

JAX-WS is a pretty big piece that is still missing for Java EE 5 conformance.

JAX-WS is a pretty big piece that is still missing for Java EE 5 conformance.

I cannot comment on the TCK progress as per the TCK rules, I just find you assertion very surprising Alexis :)

Hi Emmanuel! The comment was for Java EE 5, not for JBoss in particular.

I didn't understand this choice of Jboss group! Why did they add J2EE 1.5 specs implementation into JBoss 4.2 if they've just released JBoss 5.0.0 Beta2? Should not JBoss 5.0 be the first and only J2EE 1.5 specs implementation?

Because their implementation is modular, and the 4.2 series does not have all of the pieces of a full jee 5 stack. JBoss 5.0 will have all of them when it is released someday.

I didn't understand this choice of Jboss group! Why did they add J2EE 1.5 specs implementation into JBoss 4.2 if they've just released JBoss 5.0.0 Beta2? Should not JBoss 5.0 be the first and only J2EE 1.5 specs implementation?

We wanted to make sure we had something usable out *now*, rather than forcing people to wait for JBoss 5 for JSF 1.2, EJB3, etc. We also wanted to have a fully supportable runtime platform for Seam applications available immediately.

We wanted to make sure we had something usable out *now*, rather than forcing people to wait for JBoss 5 for JSF 1.2, EJB3, etc. We also wanted to have a fully supportable runtime platform for Seam applications available immediately.

Though I'm a GlassFish user, I think it's a great decision. One of the things that led us to choose GF (and I'm not here to pick on JBoss AS) was full EE5-compliance. What that meant for us at the time, to be honest, was JSF 1.2 and EJB3. This move goes a long way to fixing that lack. So, as I start delving into Seam, I can use the latest 4.x tree without having to translate the tutorials to work under GlassFish or Tomcat (or OC4J). Thanks, JBoss! :)

That was my path too! Glassfish is a great AS eith full J2EE 1.5 compliance and I started developing EJB3! Glassfish has a great admin console tool, but I love JBoss too, so I ' m very happy JBoss gave us the chance with 4.2 series!

Gavin, Any chance of a Web-based Administration interface being added to JBoss? This is one of the main problems I'm currently experiencing limiting JBoss adoption with our customer base. They typically only have one or two operations staff overseeing all middleware and databases, and would much rather use much more complex app servers (e.g. Oracle or WebSphere) because they appear simpler, because of the nice admin interface... Chris.

Gavin,

Any chance of a Web-based Administration interface being added to JBoss? This is one of the main problems I'm currently experiencing limiting JBoss adoption with our customer base. They typically only have one or two operations staff overseeing all middleware and databases, and would much rather use much more complex app servers (e.g. Oracle or WebSphere) because they appear simpler, because of the nice admin interface...

Chris.

Take a look at JBoss ON. Yes, I know its paid but the guys has to earn money some way. Alejandro

I didn't understand this choice of Jboss group! Why did they add J2EE 1.5 specs implementation into JBoss 4.2 if they've just released JBoss 5.0.0 Beta2? Should not JBoss 5.0 be the first and only J2EE 1.5 specs implementation?

With JBoss 5.x we are changing a lot of core architecture - kernel, deployers, classloaders, profile service, deployment repository, managed metatype, ... But before all this falls into place, you still want to provide an existing production solid platform for all the great products developed during this shift.

Cool stuff. Probably a testament to the container's modular architecture that this can be back-ported so nicely. Maybe that isn't the proper terminology but you get the idea.