| EclipseLink as alternative to Hibernate in Swing App [message #384245] |
Thu, 11 December 2008 19:55  |
 David J Rericha
Messages: 13
Registered: July 2009 |
Junior Member |
|
|
Dear members,
I have developed a production Swing app in the medical field using
Hibernate as the persistence layer. Even though Hibernate is geared
towards web-apps, it has been very adaptable to the 2-tier world with one
exception: lazy-loading. Since lazy-loading is unsupported outside a
transaction in Hibernate, I have implemented a framework that always
maintains an open transaction with the current session. However, these
long transactions still do not stave off seemingly random
LazyInitializationException's when performing lazy-loads.
My question is will I run into the same problem with EclipseLink? From
what I garnered from the documentation, fetching in EclipseLink does not
need to be wrapped in an EntityManager transaction(1). Also, any
recommended implementation-patterns of EclipseLink in a GUI app would be
much appreciated.
Thanks,
David
1 - Das, Aditi. "Understanding JPA, Part 1: The object-oriented paradigm
of data persistence." JavaWorld.com, 01/17/08:
"EntityManager manages entities; it is responsible for their addition,
updating, and deletion. You can find an entity without a transaction;
however, add, update, and delete operations need to be within a
transaction."
|
|
|
] 
Search
Help
Register
Login
Home
