- Why convert nonstandard data types?
- How to embed POJOs inside entities
- How to define relationships between entities
- Using revisions and timestamps to version entities
- How to define common entity ancestors
- How to map
Maps of basic and embedded values
- Using multiple tables to store entities
- Constructing programmatic triggers
- Using load time weaving to lazy load simple properties
WROX.COM CODE DOWNLOADS FOR THIS CHAPTER
- Advanced-Mappings Project
- Customer-Support-v18 Project
NEW MAVEN DEPENDENCIES FOR THIS CHAPTER
There are no new Maven dependencies for this chapter. Continue to use the Maven dependencies introduced in all previous chapters.
So far you’ve done some cool things with JPA. From simple lookups to complex queries to advanced searching, you’ve thoroughly explored the Java Persistence API and its CRUD capabilities.
So what’s left? Well, you’ve only touched the surface on the ways you can map objects to database tables. So far your entities have been very straightforward, containing only basic types that the JPA provider can directly and unambiguously convert to and from relational database field types. In reality, your entities will not be so trivial. You have already ...