jeudi novembre 06, 2008

GlassFish v3 Prelude redéfinit le serveur léger

Quelle est votre définition d'un serveur léger? Un serveur qui ne fait pas d'EJB?
GlassFish v3 "Prelude" est désormais disponible et pourrait bien changer ce qu'on entend par "léger".

GlassFish v3 "Prelude" est standard et extensible (OSGi, HK2, Grizzly), propose un excellent temps de démarrage, le maintient de sessions entre redéploiements, un update center, un outillage (y compris pour Eclipse), une API "Embedded", et une large documentation.

Cette version tire son doux nom de "Prelude" du fait qu'elle anticipe la sortie l'année prochaine d'un version complète (conteneur EJB, clustering, etc...) et conforme Java EE 6. Pour comparer v3 Prelude à v2, c'est par ici.

Parmi les technologies disponibles sur l' "Update Center" (bin/updatetool ou simplement dans la console d'admin): on trouve JAX-RS 1.0 (version finale), Servlet 3.0, EJB 3.1, jRuby on Rails, et Groovy/Grails. GlassFish v3 Prelude est supporté en production pour les titulaires d'un abonnement GlassFish v2 Enterprise. Une offre dédié à "Prelude" existe également.

Il sera question de GlassFish v3 prelude la semaine prochaine à la conférence Open Source eXchange.

mercredi octobre 01, 2008

GlassFish v3 prelude favorite feature

Soon-to-be-released GlassFish v3 Prelude has lots of stuff to like but I think I just found my favorite feature: Retain session data during redeployment!

vendredi septembre 26, 2008

Bundling GlassFish v3 Prelude - XWiki (Part 1)

In previous blog posts about XWiki and GlassFish, I explained how to expose XWiki on the GlassFish v2 update center and how to deploy XWiki in a GlassFish container.

This was a while back and XWiki, now a GlassFish partner, has nicely moved forward to version 1.5.2 (Stable). At the same time GlassFish released an embedded API and will soon ship GlassFish v3 Prelude, a lightweight container.

Shipping XWiki and GlassFish v3 Prelude together actually makes sense. The download is much smaller (21MB) than it would have been with GlassFish v2 (65MB), but having now an embedded API for the GlassFish makes it a reasonable Jetty alternative. It can for instance be used to implement an evaluation bundle (similar to what the OpenSSO folks did: 85Mb, Java Web Start deployment included).

Using JavaDB this time (no need to add driver in XWiki's WEB-INF/lib directory): simply edit WEB-INF/hibernate.cfg.xml to uncomment and adjust the JavaDB section, add a sun-web.xml file with a context-root set to /xwiki and update the WAR archive (xwiki-enterprise-web-1.5.2.war in my case).

Using GlassFish v3 Prelude promoted build #25 (Sept 19th), I could easily deploy by copying the archive in the auto-deploy directory (domains/domain1/autodeploy).

This can lead to a simple ZIP archive with GlassFish v3 + XWiki 1.5.2 war sitting in the auto-deploy directory. Make sure also that you nuke the domains/domain1/.felix bundle cache to avoid OSGi bundle symbolic name issues. Unzipping, starting GlassFish and pointing to http://localhost:8080/xwiki does the job (simple enough for testing/evaluating). Startup with XWiki in the autodeploy directory takes 15 seconds on my machine. Starting with Xwiki already deployed takes 8 seconds.

The next step is to start using the GlassFish embedded API.

Thanks to XWiki CTO Vincent Massol for the quick turnaround answering my questions and bug reports.

lundi mars 26, 2007

GlassFish v3

I should probably be doing some sort of post-TechDays entry or something about my one-day escape to Oslo, but since GlassFish v3 is born, I'd suggest you take a look at it.