Friday Jul 26, 2013

Oracle Grants TCKs for EclipseLink and Virgo

The TCK is a key piece of the puzzle in strongly safeguarding compatibility for anything Java. Generally speaking, companies that make money from compatible Java technology implementations have to pay license fees to run the TCK. This license fee is one of the few sources of money that helps pay the bills for the JCP/TCK process itself.

Nonetheless, Sun and now Oracle has always had a way to grant TCK scholarships for (primarily open source) non-profits and academic institutions. For example, Apache and OW2 have long had Java EE TCK scholarships to certify Geronimo and JOnAS. Oracle recently extended the gesture of good will to the open source community by granting TCK scholarships to the Eclipse Foundation for certifying EclipseLink and Virgo.

Most of you are probably already familiar with EclipseLink - it's the open source JPA reference implemention seeded via a code contribution from Oracle TopLink. You probably are not that familiar with Virgo in comparison - it's an open source Java application server from the Eclipse Foundation. Most of you will probably remember that Virgo was created when SpringSource decided to donate dm Server to the Eclipse Foundation a few years ago. Thanks to the TCK scholarship, Virgo will now aim to become another great Java EE Web Profile application server choice for you instead of just a focus on OSGi and Spring.

This is what Mike Milinkovich, executive director of the Eclipse Foundation, had to say about the grant: "It is important for the Eclipse Foundation to provide our community with the tools they need to enhance developer productivity. As a key contributor to EclipseLink and other projects, Oracle has been a strong supporter of our efforts. Through the Oracle Compatibility Testing Scholarship Program the Eclipse Foundation now has access to the resources we need to achieve Java EE Web Profile compatibility both for Java EE 6, as well as the forthcoming Java EE 7".

You can read about the details in this official press release.

Thursday Jun 09, 2011

"GlassFish is Business Class"

Here's a new article by Harald Wellmann titled "Java EE 6 Server Comparison" discussing a non-trivial Java EE 6 application (relying on the Web Profile) running on three certified and open source implementations: GlassFish, JBoss, and Resin.


Harald's detailled analysis of the issues faced with relevant bug reports (some progress already on the GlassFish side since this post a few days ago) and links to forum discussions makes for a pragmatic and useful article which also features some performance numbers.

Now of course the comments about GlassFish are not all rosy, but the constructive criticism in this series of blogs is a great way to weigh in and have your voice be heard in the community and certainly at Oracle. It also shows the progress made by GlassFish since version 3.0 (released late 2009) with soon an update to our second generation Java EE 6 product (3.1.1).

The Executive Summary for the series is short and sweet : "Glassfish is Business Class, JBoss is Baroque, Resin is Zen". Onward to First Class!

Wednesday May 18, 2011

Caucho's Resin now Java EE 6-certified (Web Profile)

Caucho's Resin application server has achieved Java EE 6 Web Profile Compliance. Congratulations to the team on reaching this milestone! Resin is an interesting case because it's actually a new player in the Java EE arena taking the opportunity of the new Java EE 6.0 Web Profile specification to achieve compatibility.

As a reminder, the Web Profile includes Servlet 3.0 (of course), but also JSF 2.0, EJB 3.1 lite, CDI 1.0, Bean Validation 1.0, JPA 2.0, JTA and other supporting technologies. By betting on this rich set of technologies, web developers are free to chose the runtime of their choice, and that now includes Caucho's Resin.

Resin AppServer

Note that Resin shares with GlassFish and WebLogic the same JPA (EclipseLink) and JSF (Mojarra) implementations while implementing their own JMS broker (an optional technology in addition to the Web Profile) and of course CanDI, their CDI implementation.

Caucho has also posted a roadmap document indicating that Resin 4.0.18 will be a certified "beta release" with 4.1 being the "stable release" soon after. Resin is available in open source (GPLv2) version as well as via a professional and enterprise editions.

Tuesday Feb 16, 2010

Java EE 6 momentum, stretching the Jersey boundaries and a bit of GlassFish


Java EE 6 adoption and overall momentum is still going strong. In the past few days there's been a InfoQ piece on how compelling EJB 3.1 are, a blog post by the Caucho folks around the Java EE 6 Web Profile which they intend to support soon in their Resin product, while Mert has a detailed step-by-step "Getting Started with Java EE 6" document featuring a demo application focusing on JSF (using PrimeFaces), CDI, among other things.

Meanwhile on the JAX-RS/Jersey side of the house, Dustin has been busy writing blog posts with the latest one about "Jersey/JAX-RS Method Designators" illustrating the importance of clean error handling. Going beyond the specification, there's also been a lot of community discussion about potential hypermedia and HATEOAS (Hypermedia as the Engine of Application State) support with exploratory work by Santiago. This page is a good place to start reading about this.

On the GlassFish side, one of the new features in v3 has been to extend the ability to create a platform service to the Windows OS. Byron has this additional blog entry on "Making GlassFish v3 Platform Services Survive Logoff". While on the GlassFish v2.x side of things, Byron also discusses offline configuration at a cluster level.