Spring/spring-data-commons
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Polishing.

Browse Source 
Replace self xrefs to <<…>> self reference syntax.

See #2912
This commit is contained in:
Mark Paluch
2023-08-31 14:26:38 +02:00
parent 8c342a56e8
commit 068c19f60f
2 changed files with 3 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
src/main/antora/modules/ROOT/pages/object-mapping.adoc
View File

@@ -78,13 +78,13 @@ For that we use the following algorithm:
1. If the property is immutable but exposes a `with…` method (see below), we use the `with…` method to create a new entity instance with the new property value. 1. If the property is immutable but exposes a `with…` method (see below), we use the `with…` method to create a new entity instance with the new property value.
2. If property access (i.e. access through getters and setters) is defined, we're invoking the setter method. 2. If property access (i.e. access through getters and setters) is defined, we're invoking the setter method.
3. If the property is mutable we set the field directly. 3. If the property is mutable we set the field directly.
4. If the property is immutable we're using the constructor to be used by persistence operations (see xref:object-mapping.adoc#mapping.object-creation[Object creation]) to create a copy of the instance. 4. If the property is immutable we're using the constructor to be used by persistence operations (see <<mapping.object-creation,Object creation>>) to create a copy of the instance.
5. By default, we set the field value directly. 5. By default, we set the field value directly.
[[mapping.property-population.details]] [[mapping.property-population.details]]
.Property population internals .Property population internals
**** ****
Similarly to our xref:object-mapping.adoc#mapping.object-creation.details[optimizations in object construction] we also use Spring Data runtime generated accessor classes to interact with the entity instance. Similarly to our <<mapping.object-creation.details,optimizations in object construction>> we also use Spring Data runtime generated accessor classes to interact with the entity instance.
[source,java] [source,java]
---- ----
@@ -299,7 +299,7 @@ Spring Data automatically tries to detect a persistent entity's constructor to b
The resolution algorithm works as follows: The resolution algorithm works as follows:
1. If there is a constructor that is annotated with `@PersistenceCreator`, it is used. 1. If there is a constructor that is annotated with `@PersistenceCreator`, it is used.
2. If the type is a xref:object-mapping.adoc#mapping.kotlin[Kotlin data cass] the primary constructor is used. 2. If the type is a <<mapping.kotlin,Kotlin data cass>> the primary constructor is used.
3. If there is a single static factory method annotated with `@PersistenceCreator` then it is used. 3. If there is a single static factory method annotated with `@PersistenceCreator` then it is used.
4. If there is a single constructor, it is used. 4. If there is a single constructor, it is used.
5. If there are multiple constructors and exactly one is annotated with `@PersistenceCreator`, it is used. 5. If there are multiple constructors and exactly one is annotated with `@PersistenceCreator`, it is used.

3
src/main/antora/modules/ROOT/pages/repositories.adoc
View File

@@ -1,6 +1,3 @@
:spring-framework-docs: {springDocsUrl}
:spring-framework-javadoc: {springJavadocUrl}
ifndef::store[] ifndef::store[]
:store: Jpa :store: Jpa
endif::[] endif::[]