Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Moving from Hibernate to EclipseLink: Some First Impressions

DZone's Guide to

Moving from Hibernate to EclipseLink: Some First Impressions

· Performance Zone
Free Resource

Download our Introduction to API Performance Testing and learn why testing your API is just as important as testing your website, and how to start today.

Generally speaking, it has been a lot of work to remove all the non-JPA Hibernate stuff from the code before I could even compile with EclipseLink. Typically, these have been cache annotations (which I will now need from EclipseLink since standards are poor in this area), and I had some instances of ScrollableResult that I had to remove.

Hibernate seemed to apply more defaults than EclipseLink does. I had to add @Temporal to my date fields, whereas Hibernate was happy with a plain date. For queries I had to touch almost all of them while adding aliases, whereas Hibernate was happy without (select from Class C where c.name vs. select from Class where name). All in all it took me about a day for a project with around 100 queries and 50 domain objects. Now I am investigating the multi-tenancy features of EclipseLink, and I think I will give some feedback when I get feedback on my bugzillas :)

Find scaling and performance issues before your customers do with our Introduction to High-Capacity Load Testing guide.

Topics:

Published at DZone with permission of Thomas Kratz, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}