@@ -78,6 +78,8 @@ There's an example {build}[Gradle build] included in the example program.
78
78
=== Configuration
79
79
80
80
:xml: https://github.com/hibernate/hibernate-reactive/blob/master/example/src/main/resources/META-INF/persistence.xml
81
+ :configuration-properties: https://docs.jboss.org/hibernate/orm/5.4/userguide/html_single/Hibernate_User_Guide.html#configurations
82
+
81
83
82
84
Hibernate Reactive is configured via the standard JPA `persistence.xml`
83
85
document which must be placed, as usual, in the `/META-INF` directory.
@@ -92,9 +94,11 @@ The only configuration specific to Hibernate Reactive is the persistence
92
94
93
95
Otherwise, configuration is almost completely transparent. Configure
94
96
Hibernate exactly as you usually would, noting that most configuration
95
- properties related to JDBC or JTA aren't relevant in the context of
96
- Hibernate Reactive.
97
+ properties directly related to JDBC or JTA aren't relevant in the context
98
+ of Hibernate Reactive.
97
99
100
+ A full list of configuration properties recognized by Hibernate may be
101
+ found in the {configuration-properties}[documentation for Hibernate ORM].
98
102
Configuration properties of particular interest include:
99
103
100
104
- `javax.persistence.jdbc.url`, the JDBC URL of your database,
@@ -149,6 +153,8 @@ TIP: But for now, just leave these three settings alone.
149
153
150
154
=== Enabling the second-level cache
151
155
156
+ :second-level-cache: https://docs.jboss.org/hibernate/orm/5.4/userguide/html_single/Hibernate_User_Guide.html#caching
157
+
152
158
Hibernate Reactive supports second-level cache implementations that
153
159
perform no blocking I/O.
154
160
@@ -180,6 +186,9 @@ TIP: Don't forget that you need to explicitly mark each entity that will
180
186
be stored in the second-level cache with the `@Cache` annotation from
181
187
`org.hibernate.annotations`.
182
188
189
+ You can find much more information about the second-level cache in the
190
+ {second-level-cache}[documentation for Hibernate ORM].
191
+
183
192
== Writing the Java code
184
193
185
194
With that out of the way, we're all set to write some Java code!
@@ -218,6 +227,8 @@ of framework code.
218
227
219
228
=== Mapping entity classes
220
229
230
+ :mapping-annotations: https://docs.jboss.org/hibernate/orm/5.4/userguide/html_single/Hibernate_User_Guide.html#annotations
231
+
221
232
We won't have much to say about the entity classes here, simply because
222
233
the principles behind mapping entity classes in Hibernate Reactive,
223
234
along with the actual mapping annotations you'll use, are all identical
@@ -253,8 +264,10 @@ You're quite free to mix and match:
253
264
`javax.persistence` with
254
265
- the advanced mapping annotations in `org.hibernate.annotations`.
255
266
256
- Most mapping annotations are already supported in Hibernate Reactive,
257
- though there are still a handful of limitations at this time.
267
+ A full list of object/relational mapping annotations may be found in the
268
+ {mapping-annotations}[documentation for Hibernate ORM]. Most mapping
269
+ annotations are already supported in Hibernate Reactive, though there are
270
+ still a handful of limitations at this time.
258
271
259
272
=== Identifier generation
260
273
@@ -525,6 +538,8 @@ have very specific requirements.
525
538
526
539
=== A reminder about performance
527
540
541
+ :association-fetching: https://docs.jboss.org/hibernate/orm/5.4/userguide/html_single/Hibernate_User_Guide.html#fetching
542
+
528
543
As always, achieving high performance in ORM means minimizing the number
529
544
of round trips to the database. This goal should be uppermost in your
530
545
mind whenever you're writing data access code with Hibernate. The most
@@ -548,6 +563,9 @@ second-level cache, batch fetching, subselect fetching, bulk update and
548
563
delete queries, and direct execution of native SQL are all things that
549
564
can help reduce the number of queries sent to the database.
550
565
566
+ You can find much more information about association fetching in the
567
+ {association-fetching}[documentation for Hibernate ORM].
568
+
551
569
=== Transactions
552
570
553
571
The `withTransaction()` method performs work within the scope of a database
0 commit comments