Java EE 6 with Fine Beers - Introduction

Moving Pictures
I'm going to register experiences of migrating an enterprise application from Glassfish V2 to V3.

I believe that each successful migration effort has to be celebrated with a Brazilian beer. As I don't upgrade Java EE versions every day, I'm going to toast with gourmet beers. I sincerely expect to be contested by beer connoisseurs in the case I'm wrong.

It all begun when our infrastructure decided to upgrade servers to a newer set of aligned open source software versions. Guess what, JDK 5 and Glassfish V2 that had served us so well were pointed out to be replaced by Open JDK 6 and Glassfish 2.1.1. That's a picture of what we have to move:

• ~ 60 Session Beans (6 SOAP endpoints)
• ~ 50 JPA Entities
• ~ 36 Servlets
• ~ 10 JSF Managed Beans / 14 Facelets view components
• An every week increasing number of Messaged Driven Beans

I knew the theory: GF 2.1.1 is Java EE 5 compatible, so the migration is supposed to be smoth. And I also knew that theory and practice are the same only in theory. Therefore, the best to be done was to prepare a migration plan. It was December 2009, Java EE 6 had been finished, and Glassfish V3 had been released as final version. At that point I realized that we could take advantage of migration effort and move to V3, unleashing development with Java EE 6 goodies.

So lets move on to Java EE 6 with Glassfish V3

• Beer #1 goes to Partial Migration with Remote JMS.
• Beer #2 goes to Mojarra 2.0 with RichFaces
• Beer #3 may goes to Glassfish packaging restrictions
• Beer #4 may goes to ...

Stay tuned ...