Mitchell Herrijgers
Mitchell Herrijgers
This PR renames the `EntityModel` to `EntityMessagingMetamodel` and gives related classes a similar treatment. When we talk about a model in AF, we talk about the user's entities and how...
This PR changes the `EntityBuilder` to the `EntityModule`, and allows annotation-based configuration for event-sourced entities via said modules. The `EntityModule` is now an encapsulated configuration `Module` that contains all the...
This PR introduces the `AnnotatedEntityModel`, which allows users to define a `SimpleEntityModel` or `PolyMorphicEntityModel` fully with annotations. ## Overview of changes introduced and role There are many classes involved in...
In Axon Framework 5 we are changing the way entites (formerly aggregates) are defined. Even though we are primarily focusing on Event-Sourcing, state-stored entities need to remain working as well....
While implemented a new way to construct `EventCriteria`, as follows: ```java EventCriteria criteria = EventCriteria .match() .eventTypes("StudentRegistered") .withTags(Tag.of("student", "studentA")) .or() .eventTypes("StudentAssignedToCourse", "CourseRegistered") .withTags(Tag.of("course", "courseB")) ``` However, in the current API...
With the current change of the `ParameterResolverFactory` and `ParameterResolver` only requiring a `ProcessingContext`, the `AnnotationBasedEventCriteriaResolver` can be changed. Right now, it has its own custom reflection logic, which can be...
When using the DLQ functionality, we store failing events into the (relational) database. This works great when there are problems like `NullpointerException`s. The message is correctly stored in the database....
### Enhancement Description During the development of Axon Framework 5 we have defined components on the configurer. This works great, as we only have to define it in one place....
With the introduction of Axon Framework 5, many things have changed. We need to support these new things in the plugin as well. There are several things to think of...