Use a proper configuration class name in docs.
Original pull request: #635.
This commit is contained in:
committed by
GitHub
parent
092e31e890
commit
fc8cdbe864
@@ -6,9 +6,9 @@ This example demonstrate basic usage of JDBC based repositories.
|
||||
|
||||
* The `SimpleEntityTests` demonstrate CRUD operations for an entity without references, just simple properties of various types.
|
||||
|
||||
* The `CategoryContext` shows how to configure an application context so that Spring Data JDBC can create repositories.
|
||||
* The `CategoryConfiguration` shows how to configure an application context so that Spring Data JDBC can create repositories.
|
||||
|
||||
* The `ApplicationListener` registered in `CategoryContext` demonstrate how to react to events published by Spring Data JDBC and how entities can get manipulated in such event listeners.
|
||||
* The `ApplicationListener` registered in `CategoryConfiguration` demonstrate how to react to events published by Spring Data JDBC and how entities can get manipulated in such event listeners.
|
||||
|
||||
=== AggregateTests
|
||||
|
||||
@@ -27,4 +27,4 @@ This is achieved by providing a custom `NamingStrategy` which maps both to the s
|
||||
|
||||
* `LegoSetRepository` has methods that utilize `@Query` annotations.
|
||||
|
||||
* Note that `Model` is a value class, i.e. it is immutable, and doesn't have an ID.
|
||||
* Note that `Model` is a value class, i.e. it is immutable, and doesn't have an ID.
|
||||
|
||||
Reference in New Issue
Block a user