New features in JBoss AS 4.2 include: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.
- 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
-
JBoss 4.2 released - integrates key bits of Java EE into 4.x (12 messages)
- Posted by: Joseph Ottinger
- Posted on: May 24 2007 09:04 EDT
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:Threaded Messages (12)
- Strange choice by Nicola Nardino on May 24 2007 10:44 EDT
- Re: Strange choice by Alexis Moussine-Pouchkine on May 24 2007 11:01 EDT
-
Re: Strange choice by Emmanuel Bernard on May 24 2007 11:52 EDT
- Re: Strange choice by Alexis Moussine-Pouchkine on June 07 2007 05:30 EDT
-
Re: Strange choice by Emmanuel Bernard on May 24 2007 11:52 EDT
- Re: Strange choice by Jesse Sightler on May 24 2007 11:08 EDT
- Re: Strange choice by Gavin King on May 24 2007 11:33 EDT
-
Re: Strange choice by Jason Lee on May 24 2007 03:14 EDT
- Right choice by Nicola Nardino on May 25 2007 03:54 EDT
-
Re: Strange choice by Chris Nappin on May 25 2007 08:15 EDT
- Re: Strange choice by Alejandro Montenegro on May 25 2007 09:40 EDT
-
Re: Strange choice by Jason Lee on May 24 2007 03:14 EDT
- Re: Strange choice by Ales Justin on May 25 2007 05:32 EDT
- Re: Strange choice by Alexis Moussine-Pouchkine on May 24 2007 11:01 EDT
- Re: JBoss 4.2 released - integrates key bits of Java EE into 4.x by George Coller on May 25 2007 15:03 EDT
-
Strange choice[ Go to top ]
- Posted by: Nicola Nardino
- Posted on: May 24 2007 10:44 EDT
- in response to Joseph Ottinger
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? -
Re: Strange choice[ Go to top ]
- Posted by: Alexis Moussine-Pouchkine
- Posted on: May 24 2007 11:01 EDT
- in response to Nicola Nardino
JAX-WS is a pretty big piece that is still missing for Java EE 5 conformance. -
Re: Strange choice[ Go to top ]
- Posted by: Emmanuel Bernard
- Posted on: May 24 2007 11:52 EDT
- in response to Alexis Moussine-Pouchkine
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 :) -
Re: Strange choice[ Go to top ]
- Posted by: Alexis Moussine-Pouchkine
- Posted on: June 07 2007 05:30 EDT
- in response to Emmanuel Bernard
Hi Emmanuel! The comment was for Java EE 5, not for JBoss in particular. -
Re: Strange choice[ Go to top ]
- Posted by: Jesse Sightler
- Posted on: May 24 2007 11:08 EDT
- in response to Nicola Nardino
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. -
Re: Strange choice[ Go to top ]
- Posted by: Gavin King
- Posted on: May 24 2007 11:33 EDT
- in response to Nicola Nardino
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. -
Re: Strange choice[ Go to top ]
- Posted by: Jason Lee
- Posted on: May 24 2007 15:14 EDT
- in response to Gavin King
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! :) -
Right choice[ Go to top ]
- Posted by: Nicola Nardino
- Posted on: May 25 2007 03:54 EDT
- in response to Jason Lee
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! -
Re: Strange choice[ Go to top ]
- Posted by: Chris Nappin
- Posted on: May 25 2007 08:15 EDT
- in response to Gavin King
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. -
Re: Strange choice[ Go to top ]
- Posted by: Alejandro Montenegro
- Posted on: May 25 2007 09:40 EDT
- in response to Chris Nappin
Gavin,
Take a look at JBoss ON. Yes, I know its paid but the guys has to earn money some way. Alejandro
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. -
Re: Strange choice[ Go to top ]
- Posted by: Ales Justin
- Posted on: May 25 2007 05:32 EDT
- in response to Nicola Nardino
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. -
Re: JBoss 4.2 released - integrates key bits of Java EE into 4.x[ Go to top ]
- Posted by: George Coller
- Posted on: May 25 2007 15:03 EDT
- in response to Joseph Ottinger
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.