Comments for Sacha's Weblog

Comment on JBoss AS 5.0: Status by John Clingan

John Clingan — Tue, 08 Jul 2008 17:37:20 +0000

Peter, GlassFish passed the Java EE 5 TCK mid-2006.

John Clingan
GlassFish Product Line Manager

Comment on JBoss AS 5.0: Status by JBoss AS 5.0 RC1 σε μερικες μερες! | zero.gr

JBoss AS 5.0 RC1 σε μερικες μερες! | zero.gr — Sat, 05 Jul 2008 17:15:11 +0000

[...] Red Hat δια στόματος της Sacha Labourey (υπεύθυνη του τμήματος Jboss) ανακοίνωσε την [...]

Comment on JBoss AS 5.0: Status by JBoss plays the choice card « rand($thoughts);

JBoss plays the choice card « rand($thoughts); — Thu, 03 Jul 2008 17:19:10 +0000

[...] Geronimo, JBoss, Open Source, WebSphere | Tags: JBoss, Open Source, WebSphere | News from Sacha (and covered by InfoWorld) that JBoss Application Server 5.0 is close to GA kicked off a debate at [...]

Comment on JBoss AS 5.0: Status by Long-awaited JBoss AS 5.0 moves closer to release date | InfoWorld | News | 2008-07-02 | By Chris Kanaracus, IDG News Service

Wed, 02 Jul 2008 22:21:47 +0000

[...] AS5.0 RC1 just got frozen and will be released this week,” Labourey wrote. A second release candidate should be ready in six to seven weeks, and general availability will [...]

Comment on JBoss AS 5.0: Status by Sacha

Sacha — Wed, 02 Jul 2008 10:25:42 +0000

Peter,

The Glassifsh team did indeed a good job at generating buzz. However, from an product standpoint, we are clearly the best

Onward,

Sacha

Comment on JBoss AS 5.0: Status by laststation.net » Blog Archive » Status of JBoss AS 5

laststation.net » Blog Archive » Status of JBoss AS 5 — Wed, 02 Jul 2008 07:45:19 +0000

[...] I don’t want to jump to conclusions, but my gloomy prediction about next major release of JBoss Application Server might not be correct. For more information check out Sacha Labourey’s status update. [...]

Comment on JBoss AS 5.0: Status by Peter Bilyan

Peter Bilyan — Wed, 02 Jul 2008 04:54:25 +0000

I would like to see a comparison of JBoss to Glassfish - the latter seems to be getting lots of buzz, and all my Java developers friends are talking about how much farther ahead it is than JBoss. Is there a comparison you can point to? Does Glassfish pass the TCK?

Comment on JBoss AS 5.0: Status by Most Awaited JBoss 5.0 soon to come :) | Ranjan Kumar

Most Awaited JBoss 5.0 soon to come :) | Ranjan Kumar — Mon, 30 Jun 2008 11:11:38 +0000

[...] JBoss AS 5.0 status: http://sacha.labourey.com/2008/06/28/jboss-as-50-status/ [...]

Comment on JBoss AS 5.0: Status by Rich Sharples’ Blog » Blog Archive » JBoss AS 5.0 CR1 almost baked

Mon, 30 Jun 2008 01:44:12 +0000

[...] Sacha (JBoss’ CTO) has blogged his thoughts on AS 5 and recalls some of the history of it’s inception. Dimitris Adreadis (the JBoss AS lead developer) was interviewed on InfoQ and talks about some of the main features and his views on the prosposed Java EE 6 profiles and OSGi. [...]

Comment on JBoss AS 5.0: Status by Sacha

Sacha — Sun, 29 Jun 2008 18:14:39 +0000

Dimitris,

True. Actually, the MC+Friends can be seen as an extension of layer 1 for JBoss’s runtimes. Thanks to its SPIs (and growing), it non only provides bytecode and core-API abstraction but also enterprise-services abstraction. Bottom line, if we ever wanted to have JBoss Portal running in Weblogic, we would first port JBoss Portal to the MC and then provide a set of WebLogic MC SPIs-implementations. Once these WL-specific MC SPIs are made available, any MC-based runtime could then be hosted on WL, etc.

Ovidiu,

Dimitris is best to answer. But most of the work is around polishing, reducing the testsuite errors to 0, TCK to 100%, fixing known bugs, etc. The area that needs the most attention is the new profile service and its impact on closely related services (management) as well as the open source management console. EJB3, as the king consumer of SPIs is also closely watched: its central location (in term of SPI consumption) gives it pretty much a role of global AS/EE testsuite as well.

Detailed information can be found in JIRA: http://jira.jboss.com/jira/browse/JBAS?report=com.atlassian.jira.plugin.system.project:roadmap-panel

Cheers,

Sacha