@@ -68,7 +68,7 @@ We can inject the `EntityManagerFactory` -
68
68
[[bootstrap-jpa-compliant-PersistenceUnit-configurable-example]]
69
69
.Injecting a specific `EntityManagerFactory`
70
70
====
71
- [source, JAVA , indent=0]
71
+ [source, java , indent=0]
72
72
----
73
73
include::{example-dir-boot}/BootstrapTest.java[tags=bootstrap-jpa-compliant-PersistenceUnit-configurable-example]
74
74
----
@@ -79,7 +79,7 @@ Because there is only one `<persistence-unit/>` defined, we can also omit the na
79
79
[[bootstrap-jpa-compliant-PersistenceUnit-example]]
80
80
.Injecting the default `EntityManagerFactory`
81
81
====
82
- [source, JAVA , indent=0]
82
+ [source, java , indent=0]
83
83
----
84
84
include::{example-dir-boot}/BootstrapTest.java[tags=bootstrap-jpa-compliant-PersistenceUnit-example]
85
85
----
@@ -104,7 +104,7 @@ and either -
104
104
[[example-bootstrap-jpa-compliant-EntityManagerFactory]]
105
105
.Application bootstrapped `EntityManagerFactory`
106
106
====
107
- [source, JAVA , indent=0]
107
+ [source, java , indent=0]
108
108
----
109
109
include::{example-dir-boot}/BootstrapTest.java[tags=bootstrap-jpa-compliant-EntityManagerFactory-example]
110
110
----
@@ -118,7 +118,7 @@ Jakarta Persistence 3.2 also introduced a new way for applications to build the
118
118
[[example-bootstrap-standard-PersistenceConfiguration]]
119
119
.Using PersistenceConfiguration
120
120
====
121
- [source, JAVA , indent=0]
121
+ [source, java , indent=0]
122
122
----
123
123
include::{example-dir-boot-jpa}/PersistenceConfigurationTests.java[tags=example-bootstrap-standard-PersistenceConfiguration]
124
124
----
@@ -130,7 +130,7 @@ which exposes additional conveniences.
130
130
[[example-bootstrap-standard-HibernatePersistenceConfiguration]]
131
131
.Using HibernatePersistenceConfiguration
132
132
====
133
- [source, JAVA , indent=0]
133
+ [source, java , indent=0]
134
134
----
135
135
include::{example-dir-boot-jpa}/PersistenceConfigurationTests.java[tags=example-bootstrap-standard-HibernatePersistenceConfiguration]
136
136
----
@@ -254,7 +254,7 @@ If you wish to alter how the `BootstrapServiceRegistry` is built, that is contro
254
254
[[example-bootstrap-native-BootstrapServiceRegistry]]
255
255
.Controlling `BootstrapServiceRegistry` building
256
256
====
257
- [source, JAVA , indent=0]
257
+ [source, java , indent=0]
258
258
----
259
259
include::{example-dir-boot}/BootstrapTest.java[tags=example-bootstrap-native-BootstrapServiceRegistry]
260
260
----
@@ -266,7 +266,7 @@ You will almost always need to configure this registry, which is done through `o
266
266
[[example-bootstrap-native-StandardServiceRegistryBuilder]]
267
267
.Building a `BootstrapServiceRegistryBuilder`
268
268
====
269
- [source, JAVA , indent=0]
269
+ [source, java , indent=0]
270
270
----
271
271
include::{example-dir-boot}/BootstrapTest.java[tags=example-bootstrap-native-StandardServiceRegistryBuilder]
272
272
----
@@ -289,7 +289,7 @@ This mapping information might be in the form of XML, annotations or both.
289
289
[[example-bootstrap-native-MetadataSources]]
290
290
.Building a `MetadataSources`
291
291
====
292
- [source, JAVA , indent=0]
292
+ [source, java , indent=0]
293
293
----
294
294
include::{example-dir-boot}/BootstrapTest.java[tags=example-bootstrap-native-MetadataSources]
295
295
----
@@ -300,7 +300,7 @@ Also, all methods on `MetadataSources` offer fluent-style call chaining -
300
300
[[bootstrap-native-metadata-source-example]]
301
301
.Configuring a `MetadataSources` with method chaining
302
302
====
303
- [source, JAVA , indent=0]
303
+ [source, java , indent=0]
304
304
----
305
305
include::{example-dir-boot}/BootstrapTest.java[tags=example-bootstrap-native-MetadataSources-chained]
306
306
----
@@ -315,7 +315,7 @@ If you have specified everything as settings, or you are ok with the default beh
315
315
[[example-bootstrap-native-Metadata-no-builder]]
316
316
.Using `MetadataSources#buildMetadata`
317
317
====
318
- [source, JAVA , indent=0]
318
+ [source, java , indent=0]
319
319
----
320
320
include::{example-dir-boot}/BootstrapTest.java[tags=example-bootstrap-native-Metadata-no-builder]
321
321
----
@@ -327,7 +327,7 @@ Optionally, we can obtain a `MetadataBuilder` from `MetadataSources` which can b
327
327
[[example-bootstrap-native-MetadataBuilder]]
328
328
.Using `MetadataBuilder`
329
329
====
330
- [source, JAVA , indent=0]
330
+ [source, java , indent=0]
331
331
----
332
332
include::{example-dir-boot}/BootstrapTest.java[tags=example-bootstrap-native-Metadata-using-builder]
333
333
----
@@ -355,7 +355,7 @@ link:{doc-javadoc-url}/org/hibernate/boot/Metadata.html#buildSessionFactory--[`M
355
355
[[example-bootstrap-native-SessionFactory-no-builder]]
356
356
.Using `SessionFactoryBuilder`
357
357
====
358
- [source, JAVA , indent=0]
358
+ [source, java , indent=0]
359
359
----
360
360
include::{example-dir-boot}/BootstrapTest.java[tags=example-bootstrap-native-SessionFactory-no-builder]
361
361
----
@@ -366,7 +366,7 @@ Or a `SessionFactoryBuilder`, obtained from `Metadata`, may be used to configure
366
366
[[example-bootstrap-native-SessionFactoryBuilder]]
367
367
.Using `SessionFactoryBuilder`
368
368
====
369
- [source, JAVA , indent=0]
369
+ [source, java , indent=0]
370
370
----
371
371
include::{example-dir-boot}/BootstrapTest.java[tags=example-bootstrap-native-SessionFactory-using-builder]
372
372
----
@@ -380,7 +380,7 @@ A common use case for `Integrator`, for example, is to hook in custom event list
380
380
[[example-bootstrap-event-listener-registration]]
381
381
.Configuring an event listener
382
382
====
383
- [source, JAVA , indent=0]
383
+ [source, java , indent=0]
384
384
----
385
385
include::{example-dir-boot}/BootstrapTest.java[tags=bootstrap-event-listener-registration-example]
386
386
----
0 commit comments