Upgrade to GlassFish v3 - effortlessly


While GlassFish v3 offers a lot of new features (Java EE 6 and OSGi-based modularity being the most obvious ones), we take compatibility very seriously and want your existing applications currently running in GlassFish v2.1.x or GlassFish v3-Prelude to run unmodified in our latest release.

To that effect GlassFish can detect earlier versions of 'domain.xml' (the all-in-one config file for GlassFish) and upgrade it for you (when you start GlassFish v3 as one option). Please read Bobby's recent post for more on this.

The official documentation can be found in the upgrade guide. That document also covers the 'asupgrade' graphical tool (which ships with the appserver but which wasn't there in Prelude). If you want more technical details on the changes and why they were required, please read this piece. Remember that it was not supported to edit domain.xml by hand back then. It's still not supported today, but who would want to do that when you have 'asadmin', the web console, and now the RESTful API?

As a reminder, when we released GlassFish v3 on December 10th 2009 (together with Java EE 6), we had a blog storm with many many interesting posts about everything-GlassFish v3 which are summarized in previous entries: Part I and Part II.

Expanded from @glassfish.


Sounds easy:

Step -3: Install Glassfish v3.
Step -3.1: Go to sun.com and find the installer.
Step -3.2: Read 10 pages of documentation and still not know how to install it correctly
Step -3.3: Try and install it. It seemed to work, but won't start up because of some strange package dependency.
Step -3.4: Spend your morning googling obscure error messages
Step -3.5: Hey, it works! How'd I do that??
Step -2: Backup your existing v2 domain
Step -1: Startup Glassfish v3 with v2 domain
Step -1.1: Upgrade failed, see logs for more details...
Step -1.2: Spend your afternoon googling obscure error messages
Step -1.3: Dammit it all to hell!
Step -1.4: Oh wait, there's a flag that affects the config. It's hidden in an xml file, deep in a directory named neither "conf" nor "config".
Step 0: Startup Glassfish v3 with v2 domain

Done in ZERO STEPS! Hooray!

I do not believe in those 1 easy step anymore. It only works with clean install or simple application... Once you get to serious stuff, it is NEVER that easy...

Posted by gilles on January 21, 2010 at 11:04 PM PST #

Thanks Gilles. Did you file any bug in the process?

Posted by Alexis Moussine-Pouchkine on January 22, 2010 at 01:01 AM PST #

Post a Comment:
Comments are closed for this entry.