Today is Monday, 4th July 2022

Archive for June, 2010

Case Study: Migrating from ASP.NET to Google Web Toolkit

Chris Ramsdale interviewed Matthias Büchner, Software Engineer at digital security company, Gemalto. In the blog post, Matthias shares his team’s experience with migrating their application from ASP.NET to Google Web Toolkit.

In summary, his team was pleased with GWT and they liked the following features:

  • Developing in a single language: Java. Their previous code base consisted of ASP.NET, JavaScript and CSS.
  • Compile time checks, debugger and using a professional IDE
  • Support for unit tests, integration tests and mock objects

A very good read if you are still evaluating GWT. See the blog post for details.

JPA 2: New Features

JPA 2 was released in December 2009. The release includes the following new features:

  • Standardize useful properties (hints, caching)
  • Fill in ORM mapping gaps
  • Make object modeling more flexible
  • Offer simple cache control abstraction
  • Allow advanced locking settings
  • Provide more hooks for vendor properties
  • Add API for better tooling support
  • Enhance JP QL query language
  • Support Java API based query language
  • Integrate with established validation standards

Mike Keith of Oracle has an excellent presentation on the new features of JPA 2. Mike is an authority on subject and is a member of the JPA JCP Expert Group. Mike is also the author of Pro JPA 2: Mastering the Java Persistence API (Apress).

Additional Resources

JSR 317: Java Persistence 2.0

Oracle TopLink reaches End-of-Life

End-of-life is a euphenism for a project/product that is “discontinued, unsupported and dead” 🙂

I have used Oracle TopLink for the past 10 years on various projects. It was one of the first ORM frameworks that “got it right”. Unfortunately, it was a commercial product that was out of the reach of most developers ($$$). Once comparable open-source projects came along such as Hibernate and iBatis, then it was really hard to justify the price of Oracle TopLink.

As a result, Oracle has decided to open-source TopLink and provide the source code to the EclipseLink project. So “TopLink” as a product name will fade in the sun set. EclipseLink will pick the best parts of TopLink and move forward.

The following blurb is posted on the Oracle TopLink site.

Oracle TopLink is a leader in the JPA community delivering the JPA 1.0 reference implementation with TopLink Essentials and now developing the JPA 2.0 reference implementation with EclipseLink.

As of Oracle TopLink 11g, TopLink Essentials has been replaced with EclipseLink JPA. EclipseLink JPA implements JPA 1.0 and is responsible for delivering the persistence framework.

Note: EclipseLink supports JPA 2.0 as of Dec 2009.

Oracle TopLink (R.I.P.).