Wednesday Sep 24, 2008

How portable is your Java EE application? Ask the Verifier!

Verifier screenshot

In times of interesting discussions around support and monetization of Open Source, the value of standard APIs is as strong as ever. So Sekhar's latest entry on Java EE verification tools should be of interest to many, wether they use GlassFish or not.

The "verifier" tool validates a Java EE application against a set of assertions to produce a report on the level of portability of the application. It is accessible via a command-line tool bundled in every copy of GlassFish, in NetBeans, and also available as an ANT task. One could use the ANT approach in a continuous build environment or simply archive the results in the VCS to track down when non-portable modifications are introduced.

Finally, you can apply those very same checks at deploy-time in GlassFish using the --verify=true option of the asadmin deploy option or simply check the "Run Verifier" box in the graphical admin tool.

Monday Sep 11, 2006

Portability of Java EE 5 Applications

House moved over a bridge

Adam argues that Java EE 5 applications are More Portable than in earlier (lesser!) releases. Part of this is the natural progression in the specs. Part of this is the Plugability of the JavaPersistence API implementations: in his case he is switching back and forth between Hibernate/JBoss and TopLinkEssentials/GlassFish.

Check here for other Java Persistence entries, and, if you are interested in portability of your apps, you may want to read about the AVK (see [1] and [2]).

Monday Apr 17, 2006

Elvis, Meet Portability

Elvis Impersonators

We may need a category just for Elvis Postings... Recently Brian started with Cay's Elvis Meets GlassFish article and Joined Elvis with NetBeans. Now, Brian has expanded on that by showing how the Java standards, and their support in an IDE like NetBeans, provide Portability on JBoss.

Portability is exactly why Java standards are important to the customer, although you may need to pay some attention to be sure no implementation dependencies creep in; you don't want to unwillingly use an Elvis Impersonator!