GH-59 - Fixed typos in reference documentation.

"ApplicationEventPublisher" is the class in the sample code, not "ApplicationEventListener". Clarified default serialization.
This commit is contained in:
Karsten Silz
2022-10-26 08:51:00 +02:00
committed by Oliver Drotbohm
parent 3f77067ce9
commit 2f5549da75
3 changed files with 4 additions and 4 deletions

View File

@@ -32,7 +32,7 @@ It also means that we will have to touch the class whenever we would like to int
We can change the application module interaction as follows:
.Publishing an application event via Spring's `ApplicationEventListener`
.Publishing an application event via Spring's `ApplicationEventPublisher`
[source, java]
----
@Service
@@ -109,7 +109,7 @@ For details, please consult the <<appendix.schemas, schema overview>> in the app
Each log entry contains the original event in serialized form.
The `EventSerializer` abstraction contained in `spring-modulith-events-core` allows plugging different strategies for how to turn the event instances into a format suitable for the datastore.
Spring Modulith provides a Jackson based implementation through the `spring-modulith-events-jackson` artifact, which registers a `JacksonEventSerializer` consuming an `ObjectMapper` through standard Spring Boot auto-configuration by default.
Spring Modulith provides a Jackson-based JSON implementation through the `spring-modulith-events-jackson` artifact, which registers a `JacksonEventSerializer` consuming an `ObjectMapper` through standard Spring Boot auto-configuration by default.
[[events.starters]]
== Spring Boot Event Registry Starters

View File

@@ -5,7 +5,7 @@ The application module model created via `ApplicationModules` can be used to cre
Spring Modulith's `Documenter` abstraction can produce two different kinds of snippets:
* C4 and UML component diagrams describing the relationships between the individual application modules
* A so called __Application Module Canvas__, a tabular overview about the module and the most relevant elements in those (Spring beans, aggregate roots, events published and listened to as well as configuration properties).
* A so-called __Application Module Canvas__, a tabular overview about the module and the most relevant elements in those (Spring beans, aggregate roots, events published and listened to as well as configuration properties).
[[documentation.component-diagrams]]
== Generating Application Module Component diagrams

View File

@@ -11,7 +11,7 @@ To activate the instrumentation add the following runtime dependency to your pro
<groupId>org.springframework.modulith</groupId>
<artifactId>spring-modulith-observability</artifactId>
<version>{projectVersion}</version>
<scope>runtime</scope
<scope>runtime</scope>
</dependency>
----