Pitfalls and practical Use-Cases: Toplink, Hibernate, Eclipse Link, Ibatis ...
Posted
by Martin K.
on Stack Overflow
See other posts from Stack Overflow
or by Martin K.
Published on 2009-04-06T09:09:14Z
Indexed on
2010/05/06
1:08 UTC
Read the original article
Hit count: 408
I worked a lot with Hibernate as my JPA implementation. In most cases it works fine! But I have also seen a lot of pitfalls:
- Remoting with persisted Objects is difficult, because Hibernate replaces the Java collections with its own collection implementation. So the every client must have the Hibernate .jar libraries. You have to take care on LazyLoading exceptions etc. One way to get around this problem is the use of webservices.
- Dirty checking is done against the Database without any lock.
- "Delayed SQL", causes that the data access isn't ACID compliant. (Lost data...)
- Implict Updates >> So we don't know if an object is modified or not (commit causes updates).
Are there similar issues with Toplink, Eclipse Link and Ibatis? When should I use them? Have they a similar performance? Are there reasons to choose Eclipse Link/Toplink... over Hibernate?
© Stack Overflow or respective owner