The <repositories /> element triggers the setup
of the Spring Data repository infrastructure. The most important attribute
is base-package which defines the package to scan for Spring
Data repository interfaces.[3]
Table A.1. Attributes
| Name | Description |
|---|---|
base-package | Defines the package to be used to be scanned for repository
interfaces extending *Repository
(actual interface is determined by specific Spring Data module) in
auto detection mode. All packages below the configured package
will be scanned, too. Wildcards are allowed. |
repository-impl-postfix | Defines the postfix to autodetect custom repository
implementations. Classes whose names end with the configured
postfix will be considered as candidates. Defaults to
Impl. |
query-lookup-strategy | Determines the strategy to be used to create finder
queries. See the section called “Query lookup strategies” for
details. Defaults to create-if-not-found. |
named-queries-location | Defines the location to look for a Properties file containing externally defined queries. |
consider-nested-repositories | Controls whether nested repository interface definitions
should be considered. Defaults to
false. |