Abstract
Entities do not persist themselves when they are created. Nor do they remove themselves from the database when they are garbage-collected. It is the logic of the application that must manipulate entities to manage their persistent lifecycle. Jakarta Persistence provides the EntityManager interface for this purpose in order to let applications manage and search for entities in the relational database.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Similar content being viewed by others
Notes
- 1.
Martin Fowler, Patterns of Enterprise Application Architecture. Boston: Addison-Wesley, 2002.
- 2.
Deepak Alur, John Crupi, and Dan Malks, Core J2EE Patterns: Best Practices and Design Strategies, Second Edition. Upper Saddle River, N.J.: Prentice Hall PTR, 2003.
- 3.
Deepak Alur, John Crupi, and Dan Malks, Core J2EE Patterns: Best Practices and Design Strategies, Second Edition. Upper Saddle River, N.J.: Prentice Hall PTR, 2003.
- 4.
Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides, Design Patterns: Elements of Reusable Object-Oriented Software. Boston: Addison-Wesley, 1995.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2022 The Author(s), under exclusive license to APress Media, LLC, part of Springer Nature
About this chapter
Cite this chapter
Jungmann, L., Keith, M., Schincariol, M., Nardone, M. (2022). Entity Manager. In: Pro Jakarta Persistence in Jakarta EE 10. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-7443-9_6
Download citation
DOI: https://doi.org/10.1007/978-1-4842-7443-9_6
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-7442-2
Online ISBN: 978-1-4842-7443-9
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)