Skip to content

Commit fad407c

Browse files
arend-von-reinersdorffmp911de
authored andcommitted
Add missing space in reference documentation.
Closes spring-projects#2628
1 parent 277eaf1 commit fad407c

File tree

1 file changed

+11
-3
lines changed

1 file changed

+11
-3
lines changed

src/main/asciidoc/repositories.adoc

+11-3
Original file line numberDiff line numberDiff line change
@@ -989,7 +989,8 @@ class CustomizedUserRepositoryImpl implements CustomizedUserRepository {
989989

990990
NOTE: The most important part of the class name that corresponds to the fragment interface is the `Impl` postfix.
991991

992-
The implementation itself does not depend on Spring Data and can be a regular Spring bean.Consequently, you can use standard dependency injection behavior to inject references to other beans (such as a `JdbcTemplate`), take part in aspects, and so on.
992+
The implementation itself does not depend on Spring Data and can be a regular Spring bean.
993+
Consequently, you can use standard dependency injection behavior to inject references to other beans (such as a `JdbcTemplate`), take part in aspects, and so on.
993994

994995
Then you can let your repository interface extend the fragment interface, as follows:
995996

@@ -1006,7 +1007,10 @@ interface UserRepository extends CrudRepository<User, Long>, CustomizedUserRepos
10061007

10071008
Extending the fragment interface with your repository interface combines the CRUD and custom functionality and makes it available to clients.
10081009

1009-
Spring Data repositories are implemented by using fragments that form a repository composition. Fragments are the base repository, functional aspects (such as <<core.extensions.querydsl,QueryDsl>>), and custom interfaces along with their implementations. Each time you add an interface to your repository interface, you enhance the composition by adding a fragment. The base repository and repository aspect implementations are provided by each Spring Data module.
1010+
Spring Data repositories are implemented by using fragments that form a repository composition.
1011+
Fragments are the base repository, functional aspects (such as <<core.extensions.querydsl,QueryDsl>>), and custom interfaces along with their implementations.
1012+
Each time you add an interface to your repository interface, you enhance the composition by adding a fragment.
1013+
The base repository and repository aspect implementations are provided by each Spring Data module.
10101014

10111015
The following example shows custom interfaces and their implementations:
10121016

@@ -1058,7 +1062,11 @@ interface UserRepository extends CrudRepository<User, Long>, HumanRepository, Co
10581062
----
10591063
====
10601064

1061-
Repositories may be composed of multiple custom implementations that are imported in the order of their declaration. Custom implementations have a higher priority than the base implementation and repository aspects. This ordering lets you override base repository and aspect methods and resolves ambiguity if two fragments contribute the same method signature. Repository fragments are not limited to use in a single repository interface. Multiple repositories may use a fragment interface, letting you reuse customizations across different repositories.
1065+
Repositories may be composed of multiple custom implementations that are imported in the order of their declaration.
1066+
Custom implementations have a higher priority than the base implementation and repository aspects.
1067+
This ordering lets you override base repository and aspect methods and resolves ambiguity if two fragments contribute the same method signature.
1068+
Repository fragments are not limited to use in a single repository interface.
1069+
Multiple repositories may use a fragment interface, letting you reuse customizations across different repositories.
10621070

10631071
The following example shows a repository fragment and its implementation:
10641072

0 commit comments

Comments
 (0)