Spring Persistence Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
=Repository= | =Repository= | ||
A repository is a Data Access Layer (or Persistence Layer) application component that intermediates interaction with a database: all database-related operations are done though the repository. | |||
Any repository implementation needs access to a persistence resource, depending on the persistence technology used. For example, a JDBC-based repository needs access to a [[DataSource#Overview|JDBC DataSource]], while a JPA-based repository needs access to an [[JPA Concepts#EntityManager|EntityManager]]. A repository can be configured with XML, or the corresponding Java class can be annotated with [[@Repository]]. | Any repository implementation needs access to a persistence resource, depending on the persistence technology used. For example, a JDBC-based repository needs access to a [[DataSource#Overview|JDBC DataSource]], while a JPA-based repository needs access to an [[JPA Concepts#EntityManager|EntityManager]]. A repository can be configured with XML, or the corresponding Java class can be annotated with [[@Repository]]. | ||
Revision as of 20:39, 14 October 2018
Internal
Overview
DAO
Repository
A repository is a Data Access Layer (or Persistence Layer) application component that intermediates interaction with a database: all database-related operations are done though the repository.
Any repository implementation needs access to a persistence resource, depending on the persistence technology used. For example, a JDBC-based repository needs access to a JDBC DataSource, while a JPA-based repository needs access to an EntityManager. A repository can be configured with XML, or the corresponding Java class can be annotated with @Repository.
Object IDs
- When persisting objects in a relational database, it is generally a good idea to have one field in the object that uniquely identifies the object. See Relational Databases.