Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseLink/Examples/JPA/Migration/Hibernate/V3Annotations"
< EclipseLink | Examples | JPA | Migration | Hibernate
(→Entity Annotations) |
|||
Line 5: | Line 5: | ||
=== @org.hibernate.annotations.Entity === | === @org.hibernate.annotations.Entity === | ||
− | <source lang="java> | + | <source lang="java"> |
@org.hibernate.annotations.Entity( | @org.hibernate.annotations.Entity( | ||
selectBeforeUpdate = true, | selectBeforeUpdate = true, |
Revision as of 13:23, 15 July 2008
This example walks through the migration from Hibernate(TM) V3 using JPA + native annotations in combination with the native API to EclipseLink JPA.
Contents
Entity Annotations
@org.hibernate.annotations.Entity
@org.hibernate.annotations.Entity( selectBeforeUpdate = true, dynamicInsert = true, dynamicUpdate = true, optimisticLock = OptimisticLockType.ALL, polymorphism = PolymorphismType.EXPLICIT)
Custom Sequence Generator
In Hibernate a custom generator for sequence values can be defined and used as:
@Id @GeneratedValue(generator = "system-uuid") @GenericGenerator(name = "system-uuid", strategy = "mypackage.UUIDGenerator") public String getTransactionGuid()
With EclipseLink a custom sequence generator can be implemented and registered for use using the @GeneratedValue. See: How to use Custom Sequencing (ie. UUID) for more details.