diff --git a/src/docs/asciidoc/40-events.adoc b/src/docs/asciidoc/40-events.adoc index 5d15fb69..aa11e46e 100644 --- a/src/docs/asciidoc/40-events.adoc +++ b/src/docs/asciidoc/40-events.adoc @@ -129,7 +129,7 @@ To actually write the event publication log, Spring Modulith exposes an `EventPu You select the persistence technology to be used by adding the corresponding JAR to your Spring Modulith application. We have prepared dedicated <> to ease that task. -The JDBC-based implementation can create a dedicated table for the event publication log when the respective configuration property is enabled. +The JDBC-based implementation can create a dedicated table for the event publication log when the respective configuration property (`spring.modulith.events.jdbc-schema-initialization.enabled`) is set to `true`. For details, please consult the <> in the appendix. [[events.serialization]] diff --git a/src/docs/asciidoc/90-appendix.adoc b/src/docs/asciidoc/90-appendix.adoc index 980778c2..56af7153 100644 --- a/src/docs/asciidoc/90-appendix.adoc +++ b/src/docs/asciidoc/90-appendix.adoc @@ -86,6 +86,9 @@ a|* `spring-modulith-docs` [[appendix.schemas]] == Event publication registry schemas +The JDBC-based event publication registry support expects the following database schemas to be present in the database. +If you would like Spring Modulith to create the schema for you, set the application property `spring.modulith.events.jdbc-schema-initialization.enabled` to `true`. + [[appendix.schemas.h2]] === H2