JBoss World 2009 September 4, 2009
Posted by Sacha in English, IT, JBoss.trackback
Even though I left RHT a few months back, I remained in close touch with the team there and it is with a great pleasure that I attended JBoss World 2009 this week in Chicago.
For the first time ever, JBoss World and Red Hat Summit happened at the same time under the same roof. Better, a unique pass enabled attendance to either sessions. While this approach had some risks, it has been very well executed: both conferences kept their pedigree while enabling cross-pollination (I’ve myself attended several RHEL-related sessions). From an attendance standpoint, I’ll wait for the official number, but I’ve heard the number of 1′600 persons which isn’t bad at all in the current economy.
On the JBoss front, this year was pretty reasonable in terms of announcements. Things I’ll remember from this year:
- The long awaited EAP 5 has been released (yes, I know, it was about time)
- Bill Burke initiated the REST-* initiative, aiming at defining a set of middleware services API on top of REST (read: WS-* for IQ<180)
- RHT initiated the Deltacloud effort aiming at standardizing an abstraction layer for IaaS cloud providers
- and last but not least, the GateIn project was released to the public!
The last news is actually very important and generated quite a bit of noise since i) it is clearly a big jump for JBoss Portal users and ii) will shed quite a bit of light on Exo Platform, a talented company whose codebase was merged with JBoss Portal. Project merge are always risky but the result that has been achieved in just a few months of work is simply amazing – look at the snapshots.
Since I’ve left the conference one day before it closes, I’ll miss tonight party but I think it is much safer this way – one party was enough 
Onward,
Sacha
Tu indiques dans ton billet que Jboss 5.0 EAP est sortie mais il n’y a toujours pas de binaires disponibles sur le site de Jboss (sauf la beta).
Petite question :
Pourquoi Jboss 5.0 EAP ne fonctionnera pas avec le JDK 1.5
alors que Jboss 5.1 AS sur laquelle est basée la 5.0 EAP supporte le JDK 1.5 et 1.6 ?
Est ce parce que Jboss 5.0 EAP sera en partie compatible Java EE 6 ?
Il y a toujours certaines entreprises ou entreprises qui utilisent le JDK 1.5 et celà risque de poser problème pour les migrations dans des grands comptes.
Source : Jboss 5.0 EAP 5Entreprise) ne supporte que le Jdk 1.6
https://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0.BETA/html/Installation_Guide/Getting_Started.html#Pre_Requisites-Hardware_and_Operating_System_Requirements
Source : Jboss 5.1 AS (communautaire) supporte le JDK-1.5 et 1.6
Source http://www.jboss.org/file-access/default/members/jbossas/freezone/docs/Installation_And_Getting_Started_Guide/5/html/Getting_Started.html#Pre_Requisites-Hardware_and_Operating_System_Requirements
Source : Jboss contient des standards de Java EE 6
Extrait : “The 5.0 release is designed to provide flexibility through support for multiple Java programming and component models including Plain Old Java Objects, Java EE 5 and various upcoming standards in the 6 version, Spring Framework, OSGi, and Google Web Toolkit. The platform also supports a number of Rich Internet Application frameworks and dynamic languages such as Ruby and Groovy.”
http://www.networkworld.com/news/2009/090109-redhat-jboss.html?hpg1=bn
Merci par avance pour la réponse.
Yannick, sorry for replying in English, my school-boy French isn’t quite up to a decent reply.
JDK 1.5 support in JBoss EAP 5.0 isn’t a priority because it’s entering it’s EOL next month (at least Sun’s impl. which is what most customers use). We’ll continue to support JDK 1.5 in EAP 4.3 as long as we can – but at some point we would advise customer to move off and onto something that is supported.
You won’t see EAP 5.0 GA on the CSP today. We’re making an limited availability release (FCS) available to a selected number of customers first and we hope to roll out the EAP 5.0 GA shortly after we’ve successfully deployed in those environments.
Hope this helps.
Rich Sharples
PM Director, JBoss Red Hat
OTOH, there seems to be an incompatibility that prevents us from using @Webserviceref due to stax-api being in java6 and also in jboss, but in a different version.
regardes tu tes mails linkedin ?