gaspersic/java-design-patterns
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

#1113 Link uml-reverse-mapper created class diagrams to readme, where needed

Browse Source
This commit is contained in:
Ilkka Seppälä
2019-12-07 20:01:13 +02:00
parent 0685a505d3
commit b09b100614
161 changed files with 246 additions and 64 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
repository/README.md
View File

@ -17,6 +17,7 @@ to minimize scattering and duplication of query code. The Repository pattern is
especially useful in systems where number of domain classes is large or heavy
querying is utilized.
## Class diagram
![alt text](./etc/repository.png "Repository")
## Applicability
@ -35,4 +36,4 @@ Use the Repository pattern when
* [Don’t use DAO, use Repository](http://thinkinginobjects.com/2012/08/26/dont-use-dao-use-repository/)
* [Advanced Spring Data JPA - Specifications and Querydsl](https://spring.io/blog/2011/04/26/advanced-spring-data-jpa-specifications-and-querydsl/)
* [Repository Pattern Benefits and Spring Implementation](https://stackoverflow.com/questions/40068965/repository-pattern-benefits-and-spring-implementation)
* [Repository Pattern Benefits and Spring Implementation](https://stackoverflow.com/questions/40068965/repository-pattern-benefits-and-spring-implementation)