Executive summary
AxonIQ/AxonFramework falls short of our standard for production, held back most by its Production Readiness lens, the way the code is tested, built, released and run. It scores 65 out of 100 and is rated Adequate, and all 44 of its critical findings are security problems.
Production Readiness, at 52, is the weakest lens and counts most in the score. The best first steps are adding automated security scanning and moving to versioned database migrations, each worth about 4 points. Raising Production Readiness to 70 would lift the score to about 72.
Thirty-one pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Eight secrets can leak from the build pipeline, and two pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline. Pinning each tool to an exact version, limiting each secret to its own step and passing outside input through environment variables would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the pipeline step that runs a download without checking it needs each download checked against a known checksum first.
The product code is 177,770 lines, about €660,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Production Readiness rose from 52 to 70, the lowest score rated Strong, the score would rise from 65 to about 72.
New since the last survey: 64 findings
- God Classes · ClassTooLong: WorkPackage messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/WorkPackage.java
- Code Duplication · Duplicated block (19 lines × 2) examples/spring-cloud/springboot3/src/main/java/org/axonframework/examples/springcloud/UniversityApplication.java
- Cohesion (LCOM4) · Low cohesion: Builder (LCOM4 20) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java
- Test Quality · No assertions: givenCoursesNotFullyBookedInFaculty_ThenNoNotificationSent examples/university-demo/src/test/java/org/axonframework/examples/demo/university/faculty/automation/allcoursesfullybookednotifier/WhenAllCoursesFullyBookedThenSendNotificationAxonFixtureTest.java
- Test Quality · No assertions: givenCourseCreatedAndRenamed_WhenChangeCapacity_ThenSuccess examples/university-demo/src/test/java/org/axonframework/examples/demo/university/faculty/write/changecoursecapacity/ChangeCourseCapacityAxonFixtureTest.java
- Test Quality · No assertions: givenCourseCreated_WhenChangeCapacityToTheSameName_ThenSuccess_NoEvents examples/university-demo/src/test/java/org/axonframework/examples/demo/university/faculty/write/changecoursecapacity/ChangeCourseCapacityAxonFixtureTest.java
- Test Quality · No assertions: givenCourseCreated_WhenChangeCapacity_ThenSuccess examples/university-demo/src/test/java/org/axonframework/examples/demo/university/faculty/write/changecoursecapacity/ChangeCourseCapacityAxonFixtureTest.java
- Test Quality · No assertions: givenStudentEnrolledInFaculty_WhenEnrollStudentInFaculty_ThenNothing examples/university-demo/src/test/java/org/axonframework/examples/demo/university/faculty/write/enrollstudent/EnrollStudentInFacultyFixtureTest.java
- Test Quality · No assertions: givenStudentNotEnrolledInFaculty_WhenEnrollStudentInFaculty_ThenStudentEnrolledInFaculty examples/university-demo/src/test/java/org/axonframework/examples/demo/university/faculty/write/enrollstudent/EnrollStudentInFacultyFixtureTest.java
- Test Quality · No assertions: givenCourseCreatedAndRenamed_WhenRenameCourse_ThenSuccess examples/university-demo/src/test/java/org/axonframework/examples/demo/university/faculty/write/renamecourse/RenameCourseAxonFixtureTest.java
- Test Quality · No assertions: givenCourseCreated_WhenRenameCourseToTheSameName_ThenSuccess_NoEvents examples/university-demo/src/test/java/org/axonframework/examples/demo/university/faculty/write/renamecourse/RenameCourseAxonFixtureTest.java
- Test Quality · No assertions: givenCourseCreated_WhenRenameCourse_ThenSuccess examples/university-demo/src/test/java/org/axonframework/examples/demo/university/faculty/write/renamecourse/RenameCourseAxonFixtureTest.java
- Test Quality · No assertions: studentAlreadySubscribedAnotherCourse examples/university-demo/src/test/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseAxonFixtureTest.java
- Test Quality · No assertions: studentSubscribedIfAnotherOneAlreadySubscribed examples/university-demo/src/test/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseAxonFixtureTest.java
- Test Quality · No assertions: successfulSubscription examples/university-demo/src/test/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseAxonFixtureTest.java
- Test Quality · No assertions: successfulSubscriptionMessageObject examples/university-demo/src/test/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseAxonFixtureTest.java
- Test Quality · No assertions: successfulSubscription examples/university-demo/src/test/java/org/axonframework/examples/demo/university/faculty/write/subscribestudentmulti/SubscribeStudentToCourseAxonFixtureTest.java
- Test Quality · No assertions: successfulUnsubscribe examples/university-demo/src/test/java/org/axonframework/examples/demo/university/faculty/write/unsubscribestudent/UnsubscribeStudentFromCourseAxonFixtureTest.java
- Test Quality · No assertions: unsubscribeAfterUnsubscription examples/university-demo/src/test/java/org/axonframework/examples/demo/university/faculty/write/unsubscribestudent/UnsubscribeStudentFromCourseAxonFixtureTest.java
- Test Quality · No assertions: unsubscribeWithoutStudentBeingSubscribed examples/university-demo/src/test/java/org/axonframework/examples/demo/university/faculty/write/unsubscribestudent/UnsubscribeStudentFromCourseAxonFixtureTest.java
- Test Quality · No assertions: aHandledEventStillTransformsThroughAChainThatRegistersADrop examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/chain/DropTest.java
- Test Quality · No assertions: systemHeartbeatIsDroppedByTheAssembledChain examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/chain/DropTest.java
- Test Quality · No assertions: withoutTheDropAHeartbeatWouldReachHandlers examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/chain/DropTest.java
- Test Quality · No assertions: multiHopTransformationPreservesInputMetadata examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/chain/MetadataPreservationTest.java
- Test Quality · No assertions: v1CoursePublishedReachesHandlerAsV3 examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/chain/MultiHopChainTesterTest.java
- Test Quality · No assertions: v2CoursePublishedReachesHandlerAsV3 examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/chain/MultiHopChainTesterTest.java
- Test Quality · No assertions: v3CoursePublishedPassesThroughUnchanged examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/chain/MultiHopChainTesterTest.java
- Test Quality · No assertions: renameCanChangeBothNameAndVersionInOneStep examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/chain/RenameTest.java
- Test Quality · No assertions: renameCanChangeTheVersionOnly examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/chain/RenameTest.java
- Test Quality · No assertions: renamedCourseOfferedFlowsThroughTheVersionChainToTheCurrentShape examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/chain/RenameTest.java
- Test Quality · No assertions: bumpingTheVersionWhileKeepingTheNameIsAllowed examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/chain/RenameViaTransformRejectedTest.java
- Test Quality · No assertions: bumpingTheVersionViaPredicateIsAllowed examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/chain/RenameViaTransformRejectedTest.java
- Test Quality · No assertions: exactMatchWinsOverAnOverlappingPredicateWhenTheExactIsRegisteredFirst examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/chain/SemanticMatchingTest.java
- Test Quality · No assertions: exactMatchWinsOverAnOverlappingPredicateWhenThePredicateIsRegisteredFirst examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/chain/SemanticMatchingTest.java
- Test Quality · No assertions: thePredicateAppliesOnlyToVersionsNoExactMatchClaims examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/chain/SemanticMatchingTest.java
- Test Quality · No assertions: commandWithoutARegionFallsBackToTheUnknownRegion examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/seed/RequestRegionBackfillIntegrationTest.java
- Test Quality · No assertions: historicRegistrationIsReadBackWithTheRegionTheCommandRunsIn examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/seed/RequestRegionBackfillIntegrationTest.java
- Test Quality · No assertions: historicCourseListedWithSeatsIsFoundWhenEnrollSourcesByASplitProducedType examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/seed/TypeFilteredSourcingUpcastIntegrationTest.java
- Test Quality · No assertions: historicCourseOfferedIsFoundWhenEnrollSourcesByTheRenamedType examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/seed/TypeFilteredSourcingUpcastIntegrationTest.java
- Test Quality · No assertions: historicCoursePublishedV1IsUpcastedWhenEnrollStudentSourcesTheCourse examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/seed/TypeFilteredSourcingUpcastIntegrationTest.java
- Test Quality · No assertions: readsCourseOfferedAsCoursePublishedWithThePayloadUnchanged examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/transformations/CourseOfferedToCoursePublishedTest.java
- Test Quality · No assertions: liftsV1PayloadToV2 examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/transformations/CoursePublishedV1ToV2Test.java
- Test Quality · No assertions: liftsV2PayloadToV3 examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/transformations/CoursePublishedV2ToV3Test.java
- Test Quality · No assertions: combinesFirstAndLastNameIntoFullName examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/transformations/StudentRegisteredV1ToV2Test.java
- Test Quality · No assertions: liftsUnversionedAnnouncementToV1 examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/transformations/SystemAnnouncementLegacyUpliftTest.java
- Test Quality · No assertions: dropsSystemHeartbeatSoNoEventIsProduced examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/transformations/SystemHeartbeatDropTest.java
- Test Quality · No assertions: liftsBetaV0_5ToV1 examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/transformations/WelcomeMessageBetaCleanupTest.java
- Test Quality · No assertions: liftsBetaV0_7ToV1 examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/transformations/WelcomeMessageBetaCleanupTest.java
- Test Quality · No assertions: liftsBetaV0_9ToV1 examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/transformations/WelcomeMessageBetaCleanupTest.java
- Test Quality · No assertions: aForeignEventWithAMatchingVersionPassesThroughUntouched examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/transformations/WelcomeMessageBetaCleanupTest.java
- Test Quality · No assertions: liftsBetaV0_5ToV1 examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/transformations/WelcomeMessageBetaCleanupWithoutPreFilterTest.java
- Test Quality · No assertions: liftsBetaV0_9ToV1 examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/transformations/WelcomeMessageBetaCleanupWithoutPreFilterTest.java
- Test Quality · No assertions: aForeignEventWithAMatchingVersionIsExcludedByThePredicatesNameGuard examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/transformations/WelcomeMessageBetaCleanupWithoutPreFilterTest.java
- Test Quality · No assertions: enrollingAnAlreadyEnrolledStudentIsANoOp examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/write/enrollstudent/EnrollStudentAxonFixtureTest.java
- Test Quality · No assertions: enrolsStudentWhenCourseIsOpenAndStudentRegistered examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/write/enrollstudent/EnrollStudentAxonFixtureTest.java
- Test Quality · No assertions: publishesNewCourse examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/write/publishcourse/PublishCourseAxonFixtureTest.java
- Test Quality · No assertions: republishingTheSameCourseIsANoOp examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/write/publishcourse/PublishCourseAxonFixtureTest.java
- Test Quality · No assertions: updatesCapacityOnPublishedCourse examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/write/updatecoursecapacity/UpdateCourseCapacityAxonFixtureTest.java
- Test Quality · No assertions: updatingToTheSameRangeEmitsNoEvent examples/university-message-transformation/src/test/java/org/axonframework/examples/demo/coursecatalog/catalog/write/updatecoursecapacity/UpdateCourseCapacityAxonFixtureTest.java
- Test Quality · No assertions: propagatesEmitUpdateContextOntoUpdatesSuppliedAfterTheSpanEnded messaging/src/test/java/org/axonframework/messaging/queryhandling/tracing/TracingQueryBusTest.java
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Change Coupling · Change-coupling hub: MappedMessageStream.java → EmptyMessageStream.java, FailedMessageStream.java, FluxMessageStream.java, OnErrorContinueMessageStream.java messaging/src/main/java/org/axonframework/messaging/core/MappedMessageStream.java
- Change Coupling · Change-coupling hub: OnNextMessageStream.java → ConcatenatingMessageStream.java, FailedMessageStream.java, FluxMessageStream.java, OnErrorContinueMessageStream.java messaging/src/main/java/org/axonframework/messaging/core/OnNextMessageStream.java
Fixed since the last survey: 20 findings
- Cohesion (LCOM4) · Low cohesion: Builder (LCOM4 19) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java
- Test Quality · No assertions: sequenceNumberParameterResolverHandlesPrimitive messaging/src/test/java/org/axonframework/messaging/eventhandling/annotation/AnnotatedParameterResolverFactoryTest.java
- Test Quality · No assertions: sequenceNumberParameterResolverIsReturnedOnlyWhenAppropriate messaging/src/test/java/org/axonframework/messaging/eventhandling/annotation/AnnotatedParameterResolverFactoryTest.java
- Test Quality · No assertions: timestampParameterResolverIsReturnedOnlyWhenAppropriate messaging/src/test/java/org/axonframework/messaging/eventhandling/annotation/AnnotatedParameterResolverFactoryTest.java
- Test Quality · No assertions: nestedOrCriteriaSurvivesTheRoundTrip messaging/src/test/java/org/axonframework/messaging/eventstreaming/EventCriteriaFlattenRoundTripTest.java
- Test Quality · No assertions: orCombinedCriteriaSurvivesTheRoundTrip messaging/src/test/java/org/axonframework/messaging/eventstreaming/EventCriteriaFlattenRoundTripTest.java
- Test Quality · No assertions: tagAndTypeCriteriaSurvivesTheRoundTrip messaging/src/test/java/org/axonframework/messaging/eventstreaming/EventCriteriaFlattenRoundTripTest.java
- Test Quality · No assertions: tagOnlyCriteriaSurvivesTheRoundTrip messaging/src/test/java/org/axonframework/messaging/eventstreaming/EventCriteriaFlattenRoundTripTest.java
- Test Quality · No assertions: typeOnlyCriteriaSurvivesTheRoundTrip messaging/src/test/java/org/axonframework/messaging/eventstreaming/EventCriteriaFlattenRoundTripTest.java
- Churn × Complexity Hotspots · Hotspot: messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java
- Churn × Complexity Hotspots · Hotspot: messaging/src/main/java/org/axonframework/messaging/tracing/configuration/MessagingTracingConfigurationEnhancer.java messaging/src/main/java/org/axonframework/messaging/tracing/configuration/MessagingTracingConfigurationEnhancer.java
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Change Coupling · Change-coupling hub: MappedMessageStream.java → ConcatenatingMessageStream.java, EmptyMessageStream.java, FailedMessageStream.java, FluxMessageStream.java, OnErrorContinueMessageStream.java messaging/src/main/java/org/axonframework/messaging/core/MappedMessageStream.java
- Change Coupling · Change-coupling hub: OnNextMessageStream.java → ConcatenatingMessageStream.java, EmptyMessageStream.java, FailedMessageStream.java, FluxMessageStream.java, OnErrorContinueMessageStream.java messaging/src/main/java/org/axonframework/messaging/core/OnNextMessageStream.java
- Change Coupling · Change coupling: ConcatenatingMessageStream.java ↔ DelayedMessageStream.java messaging/src/main/java/org/axonframework/messaging/core/ConcatenatingMessageStream.java
- Change Coupling · Change coupling: DelayedMessageStream.java ↔ OnErrorContinueMessageStream.java messaging/src/main/java/org/axonframework/messaging/core/DelayedMessageStream.java
- Change Coupling · Change coupling: RetryingCommandBus.java ↔ TracingCommandBus.java messaging/src/main/java/org/axonframework/messaging/commandhandling/retry/RetryingCommandBus.java
- Change Coupling · Change coupling: InterceptingCommandBus.java ↔ TracingCommandBus.java messaging/src/main/java/org/axonframework/messaging/commandhandling/interception/InterceptingCommandBus.java
- Change Coupling · Change coupling: SimpleContext.java ↔ SimpleEntry.java messaging/src/main/java/org/axonframework/messaging/core/SimpleContext.java
Rebuild cost: about €660,000 · Estimate
| Cost to rebuild | €220,000 to €1,100,000, for 3,679 to 11,671 hours of work, about 4.6 person-years for 2 to 9 engineers |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 65. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Large: 177,770 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 common | 2 common.tx | 3 common.infra | 4 messaging.core.unitofwork.transaction | 5 common.configuration | 6 conversion | 7 messaging.core.unitofwork | 8 messaging.commandhandling | 9 messaging.core.conversion | 10 messaging.eventhandling.replay | 11 messaging.eventhandling | 12 messaging.eventhandling.conversion | 13 messaging.core.sequencing | 14 messaging.core.annotation | 15 messaging.core | 16 messaging.eventhandling.annotation | 17 messaging.eventhandling.processing.streaming.token | 18 messaging.queryhandling | 19 messaging.tracing | 20 modelling.repository | 21 messaging.core.interception | 22 messaging.eventhandling.processing.streaming.segmenting | 23 messaging.eventstreaming | 24 modelling | 25 eventsourcing.eventstore | 26 messaging.eventhandling.processing | 27 messaging.eventhandling.processing.streaming.token.store | 28 modelling.entity | 29 eventsourcing.eventstore.jpa | 30 eventsourcing.eventstore.tracing | 31 eventsourcing.handler | 32 messaging.eventhandling.processing.streaming.pooled | 33 messaging.eventhandling.processing.subscribing | 34 modelling.annotation | 35 eventsourcing | 36 extension.springboot.autoconfig | 37 messaging.eventhandling.configuration | 38 modelling.entity.annotation | 39 messaging.core.configuration | 40 eventsourcing.configuration |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 common | ||||||||||||||||||||||||||||||||||||||||
| 2 common.tx | ||||||||||||||||||||||||||||||||||||||||
| 3 common.infra | 1 | |||||||||||||||||||||||||||||||||||||||
| 4 messaging.core.unitofwork.transaction | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 5 common.configuration | 6 | 16 | ||||||||||||||||||||||||||||||||||||||
| 6 conversion | 1 | 4 | ||||||||||||||||||||||||||||||||||||||
| 7 messaging.core.unitofwork | 1 | 10 | ||||||||||||||||||||||||||||||||||||||
| 8 messaging.commandhandling | 4 | 4 | 5 | 6 | 19 | |||||||||||||||||||||||||||||||||||
| 9 messaging.core.conversion | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 10 messaging.eventhandling.replay | 3 | 4 | 3 | 2 | 15 | |||||||||||||||||||||||||||||||||||
| 11 messaging.eventhandling | 6 | 10 | 2 | 12 | 12 | 1 | 26 | |||||||||||||||||||||||||||||||||
| 12 messaging.eventhandling.conversion | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 13 messaging.core.sequencing | 10 | 1 | 1 | 5 | ||||||||||||||||||||||||||||||||||||
| 14 messaging.core.annotation | 2 | 1 | 12 | 1 | 25 | |||||||||||||||||||||||||||||||||||
| 15 messaging.core | 13 | 1 | 8 | 9 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 16 messaging.eventhandling.annotation | 1 | 2 | 6 | 4 | 5 | 1 | 2 | 23 | 5 | |||||||||||||||||||||||||||||||
| 17 messaging.eventhandling.processing.streaming.token | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 18 messaging.queryhandling | 5 | 6 | 1 | 7 | 10 | 1 | 4 | 30 | ||||||||||||||||||||||||||||||||
| 19 messaging.tracing | 2 | 5 | 10 | |||||||||||||||||||||||||||||||||||||
| 20 modelling.repository | 1 | 3 | 6 | 1 | ||||||||||||||||||||||||||||||||||||
| 21 messaging.core.interception | 17 | 4 | 14 | 3 | 4 | 4 | 29 | 6 | ||||||||||||||||||||||||||||||||
| 22 messaging.eventhandling.processing.streaming.segmenting | 1 | 3 | 2 | 8 | 1 | 9 | 5 | |||||||||||||||||||||||||||||||||
| 23 messaging.eventstreaming | 2 | 1 | 13 | 4 | ||||||||||||||||||||||||||||||||||||
| 24 modelling | 1 | 9 | 2 | 1 | 10 | 3 | 6 | 9 | ||||||||||||||||||||||||||||||||
| 25 eventsourcing.eventstore | 5 | 5 | 12 | 22 | 22 | 5 | 24 | |||||||||||||||||||||||||||||||||
| 26 messaging.eventhandling.processing | 1 | 3 | 1 | 1 | 2 | 4 | 1 | |||||||||||||||||||||||||||||||||
| 27 messaging.eventhandling.processing.streaming.token.store | 3 | 1 | 1 | 4 | 1 | |||||||||||||||||||||||||||||||||||
| 28 modelling.entity | 7 | 7 | 21 | 2 | 19 | 3 | 6 | |||||||||||||||||||||||||||||||||
| 29 eventsourcing.eventstore.jpa | 3 | 1 | 1 | 1 | 1 | 1 | 3 | 1 | 3 | 5 | 2 | 17 | ||||||||||||||||||||||||||||
| 30 eventsourcing.eventstore.tracing | 1 | 2 | 1 | 2 | 2 | 2 | 2 | 4 | 2 | 9 | ||||||||||||||||||||||||||||||
| 31 eventsourcing.handler | 5 | 1 | 5 | 1 | 1 | 3 | 1 | 5 | 3 | |||||||||||||||||||||||||||||||
| 32 messaging.eventhandling.processing.streaming.pooled | 2 | 8 | 20 | 15 | 1 | 18 | 12 | 20 | 12 | 2 | 8 | 11 | ||||||||||||||||||||||||||||
| 33 messaging.eventhandling.processing.subscribing | 1 | 2 | 8 | 2 | 4 | 5 | 2 | 11 | ||||||||||||||||||||||||||||||||
| 34 modelling.annotation | 6 | 3 | 1 | 1 | 7 | 4 | 8 | 2 | ||||||||||||||||||||||||||||||||
| 35 eventsourcing | 1 | 3 | 1 | 1 | 3 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||
| 36 extension.springboot.autoconfig | 3 | 12 | 11 | 2 | 5 | 2 | 5 | 4 | 3 | 4 | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||
| 37 messaging.eventhandling.configuration | 2 | 17 | 1 | 7 | 5 | 1 | 3 | 3 | 1 | |||||||||||||||||||||||||||||||
| 38 modelling.entity.annotation | 4 | 1 | 5 | 3 | 2 | 2 | 1 | 5 | 9 | 2 | 8 | 1 | ||||||||||||||||||||||||||||
| 39 messaging.core.configuration | 9 | 1 | 2 | 5 | 1 | 2 | 1 | 1 | 1 | 5 | 4 | 2 | 1 | |||||||||||||||||||||||||||
| 40 eventsourcing.configuration | 10 | 2 | 23 | 1 | 1 | 1 | 2 | 1 | 4 | 6 | 3 | 1 | 6 | 1 | 1 |
3→1 common.infra uses common✕
- Connections
- 1 pair of types, where a type in common.infra uses a type in common.
- The types involved
org.axonframework.common.infra.ComponentDescriptorException→org.axonframework.common.AxonNonTransientException
- Direction
- common.infra uses common, so a change to common can break common.infra, while a change to common.infra can't break common.
- Position
- Below the diagonal: common.infra uses a module listed above it, which is the healthy direction.
4→2 messaging.core.unitofwork.transaction uses common.tx✕
- Connections
- 2 pairs of types, where a type in messaging.core.unitofwork.transaction uses a type in common.tx.
- The types involved
org.axonframework.messaging.core.unitofwork.transaction.3887→org.axonframework.common.tx.TransactionalExecutororg.axonframework.messaging.core.unitofwork.transaction.TransactionalExecutorProvider→org.axonframework.common.tx.TransactionalExecutor
- Direction
- messaging.core.unitofwork.transaction uses common.tx, so a change to common.tx can break messaging.core.unitofwork.transaction, while a change to messaging.core.unitofwork.transaction can't break common.tx.
- Position
- Below the diagonal: messaging.core.unitofwork.transaction uses a module listed above it, which is the healthy direction.
4→7 messaging.core.unitofwork.transaction uses messaging.core.unitofwork part of a loop✕
- Connections
- 2 pairs of types, where a type in messaging.core.unitofwork.transaction uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.messaging.core.unitofwork.transaction.TransactionManager→org.axonframework.messaging.core.unitofwork.ProcessingLifecycleorg.axonframework.messaging.core.unitofwork.transaction.TransactionalExecutorProvider→org.axonframework.messaging.core.unitofwork.ProcessingContext
- Direction
- messaging.core.unitofwork.transaction uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break messaging.core.unitofwork.transaction, while a change to messaging.core.unitofwork.transaction can't break messaging.core.unitofwork.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→1 common.configuration uses common✕
- Connections
- 6 pairs of types, where a type in common.configuration uses a type in common.
- The types involved
org.axonframework.common.configuration.AxonConfigurationImpl→org.axonframework.common.TypeReferenceorg.axonframework.common.configuration.ComponentDefinition→org.axonframework.common.TypeReferenceorg.axonframework.common.configuration.ComponentNotFoundException→org.axonframework.common.TypeReferenceorg.axonframework.common.configuration.Configuration→org.axonframework.common.TypeReferenceorg.axonframework.common.configuration.Identifier→org.axonframework.common.TypeReferenceorg.axonframework.common.configuration.LocalConfiguration→org.axonframework.common.TypeReference
- Direction
- common.configuration uses common, so a change to common can break common.configuration, while a change to common.configuration can't break common.
- Position
- Below the diagonal: common.configuration uses a module listed above it, which is the healthy direction.
5→3 common.configuration uses common.infra✕
- Connections
- 16 pairs of types, where a type in common.configuration uses a type in common.infra.
- The types involved
org.axonframework.common.configuration.AbstractComponent→org.axonframework.common.infra.ComponentDescriptororg.axonframework.common.configuration.AxonConfigurationImpl→org.axonframework.common.infra.ComponentDescriptororg.axonframework.common.configuration.Component→org.axonframework.common.infra.DescribableComponentorg.axonframework.common.configuration.ComponentFactory→org.axonframework.common.infra.DescribableComponentorg.axonframework.common.configuration.ComponentRegistry→org.axonframework.common.infra.DescribableComponentorg.axonframework.common.configuration.Components→org.axonframework.common.infra.ComponentDescriptororg.axonframework.common.configuration.Components→org.axonframework.common.infra.DescribableComponentorg.axonframework.common.configuration.Configuration→org.axonframework.common.infra.DescribableComponentorg.axonframework.common.configuration.ConfigurationExtension→org.axonframework.common.infra.DescribableComponentorg.axonframework.common.configuration.ConfigurationExtensions→org.axonframework.common.infra.ComponentDescriptororg.axonframework.common.configuration.ConfigurationExtensions→org.axonframework.common.infra.DescribableComponentorg.axonframework.common.configuration.DecoratedComponent→org.axonframework.common.infra.ComponentDescriptororg.axonframework.common.configuration.DefaultComponentRegistry→org.axonframework.common.infra.ComponentDescriptororg.axonframework.common.configuration.InstantiatedComponentDefinition→org.axonframework.common.infra.ComponentDescriptororg.axonframework.common.configuration.LazyInitializedComponentDefinition→org.axonframework.common.infra.ComponentDescriptororg.axonframework.common.configuration.LocalConfiguration→org.axonframework.common.infra.ComponentDescriptor
- Direction
- common.configuration uses common.infra, so a change to common.infra can break common.configuration, while a change to common.configuration can't break common.infra.
- Position
- Below the diagonal: common.configuration uses a module listed above it, which is the healthy direction.
6→1 conversion uses common✕
- Connections
- 1 pair of types, where a type in conversion uses a type in common.
- The types involved
org.axonframework.conversion.ConversionException→org.axonframework.common.AxonNonTransientException
- Direction
- conversion uses common, so a change to common can break conversion, while a change to conversion can't break common.
- Position
- Below the diagonal: conversion uses a module listed above it, which is the healthy direction.
6→3 conversion uses common.infra✕
- Connections
- 4 pairs of types, where a type in conversion uses a type in common.infra.
- The types involved
org.axonframework.conversion.ChainingContentTypeConverter→org.axonframework.common.infra.ComponentDescriptororg.axonframework.conversion.Converter→org.axonframework.common.infra.DescribableComponentorg.axonframework.conversion.DelegatingGeneralConverter→org.axonframework.common.infra.ComponentDescriptororg.axonframework.conversion.PassThroughConverter→org.axonframework.common.infra.ComponentDescriptor
- Direction
- conversion uses common.infra, so a change to common.infra can break conversion, while a change to conversion can't break common.infra.
- Position
- Below the diagonal: conversion uses a module listed above it, which is the healthy direction.
7→4 messaging.core.unitofwork uses messaging.core.unitofwork.transaction✕
- Connections
- 1 pair of types, where a type in messaging.core.unitofwork uses a type in messaging.core.unitofwork.transaction.
- The types involved
org.axonframework.messaging.core.unitofwork.TransactionalUnitOfWorkFactory→org.axonframework.messaging.core.unitofwork.transaction.TransactionManager
- Direction
- messaging.core.unitofwork uses messaging.core.unitofwork.transaction, so a change to messaging.core.unitofwork.transaction can break messaging.core.unitofwork, while a change to messaging.core.unitofwork can't break messaging.core.unitofwork.transaction.
- Position
- Below the diagonal: messaging.core.unitofwork uses a module listed above it, which is the healthy direction.
7→15 messaging.core.unitofwork uses messaging.core part of a loop✕
- Connections
- 10 pairs of types, where a type in messaging.core.unitofwork uses a type in messaging.core.
- The types involved
org.axonframework.messaging.core.unitofwork.LegacyMessageSupportingContext→org.axonframework.messaging.core.Messageorg.axonframework.messaging.core.unitofwork.LegacyMessageSupportingContext→org.axonframework.messaging.core.ResourceKeyorg.axonframework.messaging.core.unitofwork.ProcessingContext→org.axonframework.messaging.core.ApplicationContextorg.axonframework.messaging.core.unitofwork.ProcessingContext→org.axonframework.messaging.core.Contextorg.axonframework.messaging.core.unitofwork.ProcessingContext→org.axonframework.messaging.core.ResourceKeyorg.axonframework.messaging.core.unitofwork.ResourceOverridingProcessingContext→org.axonframework.messaging.core.ResourceKeyorg.axonframework.messaging.core.unitofwork.SimpleUnitOfWorkFactory→org.axonframework.messaging.core.ApplicationContextorg.axonframework.messaging.core.unitofwork.UnitOfWork→org.axonframework.messaging.core.ApplicationContextorg.axonframework.messaging.core.unitofwork.UnitOfWorkProcessingContext→org.axonframework.messaging.core.ApplicationContextorg.axonframework.messaging.core.unitofwork.UnitOfWorkProcessingContext→org.axonframework.messaging.core.ResourceKey
- Direction
- messaging.core.unitofwork uses messaging.core, so a change to messaging.core can break messaging.core.unitofwork, while a change to messaging.core.unitofwork can't break messaging.core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→1 messaging.commandhandling uses common✕
- Connections
- 4 pairs of types, where a type in messaging.commandhandling uses a type in common.
- The types involved
org.axonframework.messaging.commandhandling.CommandDispatchException→org.axonframework.common.AxonExceptionorg.axonframework.messaging.commandhandling.CommandMessage→org.axonframework.common.TypeReferenceorg.axonframework.messaging.commandhandling.CommandResultMessage→org.axonframework.common.TypeReferenceorg.axonframework.messaging.commandhandling.NoHandlerForCommandException→org.axonframework.common.AxonTransientException
- Direction
- messaging.commandhandling uses common, so a change to common can break messaging.commandhandling, while a change to messaging.commandhandling can't break common.
- Position
- Below the diagonal: messaging.commandhandling uses a module listed above it, which is the healthy direction.
8→3 messaging.commandhandling uses common.infra✕
- Connections
- 4 pairs of types, where a type in messaging.commandhandling uses a type in common.infra.
- The types involved
org.axonframework.messaging.commandhandling.CommandBus→org.axonframework.common.infra.DescribableComponentorg.axonframework.messaging.commandhandling.CommandHandlingComponent→org.axonframework.common.infra.DescribableComponentorg.axonframework.messaging.commandhandling.SimpleCommandBus→org.axonframework.common.infra.ComponentDescriptororg.axonframework.messaging.commandhandling.SimpleCommandHandlingComponent→org.axonframework.common.infra.ComponentDescriptor
- Direction
- messaging.commandhandling uses common.infra, so a change to common.infra can break messaging.commandhandling, while a change to messaging.commandhandling can't break common.infra.
- Position
- Below the diagonal: messaging.commandhandling uses a module listed above it, which is the healthy direction.
8→6 messaging.commandhandling uses conversion✕
- Connections
- 5 pairs of types, where a type in messaging.commandhandling uses a type in conversion.
- The types involved
org.axonframework.messaging.commandhandling.CommandExecutionException→org.axonframework.conversion.Converterorg.axonframework.messaging.commandhandling.CommandMessage→org.axonframework.conversion.Converterorg.axonframework.messaging.commandhandling.CommandResultMessage→org.axonframework.conversion.Converterorg.axonframework.messaging.commandhandling.GenericCommandMessage→org.axonframework.conversion.Converterorg.axonframework.messaging.commandhandling.GenericCommandResultMessage→org.axonframework.conversion.Converter
- Direction
- messaging.commandhandling uses conversion, so a change to conversion can break messaging.commandhandling, while a change to messaging.commandhandling can't break conversion.
- Position
- Below the diagonal: messaging.commandhandling uses a module listed above it, which is the healthy direction.
8→7 messaging.commandhandling uses messaging.core.unitofwork✕
- Connections
- 6 pairs of types, where a type in messaging.commandhandling uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.messaging.commandhandling.CommandBus→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.commandhandling.CommandHandler→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.commandhandling.CommandHandlingExceptionHandler→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.commandhandling.SimpleCommandBus→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.commandhandling.SimpleCommandBus→org.axonframework.messaging.core.unitofwork.UnitOfWorkFactoryorg.axonframework.messaging.commandhandling.SimpleCommandHandlingComponent→org.axonframework.messaging.core.unitofwork.ProcessingContext
- Direction
- messaging.commandhandling uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break messaging.commandhandling, while a change to messaging.commandhandling can't break messaging.core.unitofwork.
- Position
- Below the diagonal: messaging.commandhandling uses a module listed above it, which is the healthy direction.
8→15 messaging.commandhandling uses messaging.core part of a loop✕
- Connections
- 19 pairs of types, where a type in messaging.commandhandling uses a type in messaging.core.
- The types involved
org.axonframework.messaging.commandhandling.CommandExecutionException→org.axonframework.messaging.core.HandlerExecutionExceptionorg.axonframework.messaging.commandhandling.CommandHandler→org.axonframework.messaging.core.MessageHandlerorg.axonframework.messaging.commandhandling.CommandHandler→org.axonframework.messaging.core.Singleorg.axonframework.messaging.commandhandling.CommandHandlerRegistry→org.axonframework.messaging.core.QualifiedNameorg.axonframework.messaging.commandhandling.CommandHandlingComponent→org.axonframework.messaging.core.QualifiedNameorg.axonframework.messaging.commandhandling.CommandHandlingExceptionHandler→org.axonframework.messaging.core.MessageHandlingExceptionHandlerorg.axonframework.messaging.commandhandling.CommandHandlingExceptionHandler→org.axonframework.messaging.core.Singleorg.axonframework.messaging.commandhandling.CommandMessage→org.axonframework.messaging.core.Messageorg.axonframework.messaging.commandhandling.CommandResultMessage→org.axonframework.messaging.core.ResultMessageorg.axonframework.messaging.commandhandling.DuplicateCommandHandlerSubscriptionException→org.axonframework.messaging.core.QualifiedNameorg.axonframework.messaging.commandhandling.GenericCommandMessage→org.axonframework.messaging.core.Messageorg.axonframework.messaging.commandhandling.GenericCommandMessage→org.axonframework.messaging.core.MessageDecoratororg.axonframework.messaging.commandhandling.GenericCommandMessage→org.axonframework.messaging.core.MessageTypeorg.axonframework.messaging.commandhandling.GenericCommandResultMessage→org.axonframework.messaging.core.GenericResultMessageorg.axonframework.messaging.commandhandling.GenericCommandResultMessage→org.axonframework.messaging.core.Messageorg.axonframework.messaging.commandhandling.GenericCommandResultMessage→org.axonframework.messaging.core.MessageTypeorg.axonframework.messaging.commandhandling.SimpleCommandBus→org.axonframework.messaging.core.QualifiedNameorg.axonframework.messaging.commandhandling.SimpleCommandHandlingComponent→org.axonframework.messaging.core.QualifiedNameorg.axonframework.messaging.commandhandling.SimpleCommandHandlingComponent→org.axonframework.messaging.core.Single
- Direction
- messaging.commandhandling uses messaging.core, so a change to messaging.core can break messaging.commandhandling, while a change to messaging.commandhandling can't break messaging.core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→3 messaging.core.conversion uses common.infra✕
- Connections
- 1 pair of types, where a type in messaging.core.conversion uses a type in common.infra.
- The types involved
org.axonframework.messaging.core.conversion.DelegatingMessageConverter→org.axonframework.common.infra.ComponentDescriptor
- Direction
- messaging.core.conversion uses common.infra, so a change to common.infra can break messaging.core.conversion, while a change to messaging.core.conversion can't break common.infra.
- Position
- Below the diagonal: messaging.core.conversion uses a module listed above it, which is the healthy direction.
9→6 messaging.core.conversion uses conversion✕
- Connections
- 2 pairs of types, where a type in messaging.core.conversion uses a type in conversion.
- The types involved
org.axonframework.messaging.core.conversion.DelegatingMessageConverter→org.axonframework.conversion.Converterorg.axonframework.messaging.core.conversion.MessageConverter→org.axonframework.conversion.Converter
- Direction
- messaging.core.conversion uses conversion, so a change to conversion can break messaging.core.conversion, while a change to messaging.core.conversion can't break conversion.
- Position
- Below the diagonal: messaging.core.conversion uses a module listed above it, which is the healthy direction.
10→1 messaging.eventhandling.replay uses common✕
- Connections
- 3 pairs of types, where a type in messaging.eventhandling.replay uses a type in common.
- The types involved
org.axonframework.messaging.eventhandling.replay.ReplayStatusChanged→org.axonframework.common.TypeReferenceorg.axonframework.messaging.eventhandling.replay.ResetContext→org.axonframework.common.TypeReferenceorg.axonframework.messaging.eventhandling.replay.ResetNotSupportedException→org.axonframework.common.AxonNonTransientException
- Direction
- messaging.eventhandling.replay uses common, so a change to common can break messaging.eventhandling.replay, while a change to messaging.eventhandling.replay can't break common.
- Position
- Below the diagonal: messaging.eventhandling.replay uses a module listed above it, which is the healthy direction.
10→6 messaging.eventhandling.replay uses conversion✕
- Connections
- 4 pairs of types, where a type in messaging.eventhandling.replay uses a type in conversion.
- The types involved
org.axonframework.messaging.eventhandling.replay.GenericReplayStatusChanged→org.axonframework.conversion.Converterorg.axonframework.messaging.eventhandling.replay.GenericResetContext→org.axonframework.conversion.Converterorg.axonframework.messaging.eventhandling.replay.ReplayStatusChanged→org.axonframework.conversion.Converterorg.axonframework.messaging.eventhandling.replay.ResetContext→org.axonframework.conversion.Converter
- Direction
- messaging.eventhandling.replay uses conversion, so a change to conversion can break messaging.eventhandling.replay, while a change to messaging.eventhandling.replay can't break conversion.
- Position
- Below the diagonal: messaging.eventhandling.replay uses a module listed above it, which is the healthy direction.
10→7 messaging.eventhandling.replay uses messaging.core.unitofwork✕
- Connections
- 3 pairs of types, where a type in messaging.eventhandling.replay uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.messaging.eventhandling.replay.ReplayBlockingEventHandlingComponent→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventhandling.replay.ReplayStatusChangedHandler→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventhandling.replay.ResetHandler→org.axonframework.messaging.core.unitofwork.ProcessingContext
- Direction
- messaging.eventhandling.replay uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break messaging.eventhandling.replay, while a change to messaging.eventhandling.replay can't break messaging.core.unitofwork.
- Position
- Below the diagonal: messaging.eventhandling.replay uses a module listed above it, which is the healthy direction.
10→11 messaging.eventhandling.replay uses messaging.eventhandling part of a loop✕
- Connections
- 2 pairs of types, where a type in messaging.eventhandling.replay uses a type in messaging.eventhandling.
- The types involved
org.axonframework.messaging.eventhandling.replay.ReplayBlockingEventHandlingComponent→org.axonframework.messaging.eventhandling.DelegatingEventHandlingComponentorg.axonframework.messaging.eventhandling.replay.ReplayBlockingEventHandlingComponent→org.axonframework.messaging.eventhandling.EventMessage
- Direction
- messaging.eventhandling.replay uses messaging.eventhandling, so a change to messaging.eventhandling can break messaging.eventhandling.replay, while a change to messaging.eventhandling.replay can't break messaging.eventhandling.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→15 messaging.eventhandling.replay uses messaging.core part of a loop✕
- Connections
- 15 pairs of types, where a type in messaging.eventhandling.replay uses a type in messaging.core.
- The types involved
org.axonframework.messaging.eventhandling.replay.GenericReplayStatusChanged→org.axonframework.messaging.core.Messageorg.axonframework.messaging.eventhandling.replay.GenericReplayStatusChanged→org.axonframework.messaging.core.MessageDecoratororg.axonframework.messaging.eventhandling.replay.GenericResetContext→org.axonframework.messaging.core.Messageorg.axonframework.messaging.eventhandling.replay.GenericResetContext→org.axonframework.messaging.core.MessageDecoratororg.axonframework.messaging.eventhandling.replay.GenericResetContext→org.axonframework.messaging.core.MessageTypeorg.axonframework.messaging.eventhandling.replay.ReplayBlockingEventHandlingComponent→org.axonframework.messaging.core.Emptyorg.axonframework.messaging.eventhandling.replay.ReplayBlockingEventHandlingComponent→org.axonframework.messaging.core.Messageorg.axonframework.messaging.eventhandling.replay.ReplayStatusChanged→org.axonframework.messaging.core.Messageorg.axonframework.messaging.eventhandling.replay.ReplayStatusChangedHandler→org.axonframework.messaging.core.Emptyorg.axonframework.messaging.eventhandling.replay.ReplayStatusChangedHandler→org.axonframework.messaging.core.Messageorg.axonframework.messaging.eventhandling.replay.ReplayStatusChangedHandler→org.axonframework.messaging.core.MessageHandlerorg.axonframework.messaging.eventhandling.replay.ResetContext→org.axonframework.messaging.core.Messageorg.axonframework.messaging.eventhandling.replay.ResetHandler→org.axonframework.messaging.core.Emptyorg.axonframework.messaging.eventhandling.replay.ResetHandler→org.axonframework.messaging.core.Messageorg.axonframework.messaging.eventhandling.replay.ResetHandler→org.axonframework.messaging.core.MessageHandler
- Direction
- messaging.eventhandling.replay uses messaging.core, so a change to messaging.core can break messaging.eventhandling.replay, while a change to messaging.eventhandling.replay can't break messaging.core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→1 messaging.eventhandling uses common✕
- Connections
- 6 pairs of types, where a type in messaging.eventhandling uses a type in common.
- The types involved
org.axonframework.messaging.eventhandling.DelegatingEventBus→org.axonframework.common.Registrationorg.axonframework.messaging.eventhandling.EventMessage→org.axonframework.common.TypeReferenceorg.axonframework.messaging.eventhandling.EventSubscribers→org.axonframework.common.Registrationorg.axonframework.messaging.eventhandling.InterceptingEventBus→org.axonframework.common.Registrationorg.axonframework.messaging.eventhandling.SimpleEventBus→org.axonframework.common.Registrationorg.axonframework.messaging.eventhandling.TransactionMethodExecutionException→org.axonframework.common.AxonException
- Direction
- messaging.eventhandling uses common, so a change to common can break messaging.eventhandling, while a change to messaging.eventhandling can't break common.
- Position
- Below the diagonal: messaging.eventhandling uses a module listed above it, which is the healthy direction.
11→3 messaging.eventhandling uses common.infra✕
- Connections
- 10 pairs of types, where a type in messaging.eventhandling uses a type in common.infra.
- The types involved
org.axonframework.messaging.eventhandling.DelegatingEventBus→org.axonframework.common.infra.ComponentDescriptororg.axonframework.messaging.eventhandling.DelegatingEventHandlingComponent→org.axonframework.common.infra.ComponentDescriptororg.axonframework.messaging.eventhandling.EventHandlingComponent→org.axonframework.common.infra.DescribableComponentorg.axonframework.messaging.eventhandling.EventSink→org.axonframework.common.infra.DescribableComponentorg.axonframework.messaging.eventhandling.EventSubscribers→org.axonframework.common.infra.ComponentDescriptororg.axonframework.messaging.eventhandling.EventSubscribers→org.axonframework.common.infra.DescribableComponentorg.axonframework.messaging.eventhandling.InterceptingEventBus→org.axonframework.common.infra.ComponentDescriptororg.axonframework.messaging.eventhandling.InterceptingEventSink→org.axonframework.common.infra.ComponentDescriptororg.axonframework.messaging.eventhandling.SimpleEventBus→org.axonframework.common.infra.ComponentDescriptororg.axonframework.messaging.eventhandling.SimpleEventHandlingComponent→org.axonframework.common.infra.ComponentDescriptor
- Direction
- messaging.eventhandling uses common.infra, so a change to common.infra can break messaging.eventhandling, while a change to messaging.eventhandling can't break common.infra.
- Position
- Below the diagonal: messaging.eventhandling uses a module listed above it, which is the healthy direction.
11→6 messaging.eventhandling uses conversion✕
- Connections
- 2 pairs of types, where a type in messaging.eventhandling uses a type in conversion.
- The types involved
org.axonframework.messaging.eventhandling.EventMessage→org.axonframework.conversion.Converterorg.axonframework.messaging.eventhandling.GenericEventMessage→org.axonframework.conversion.Converter
- Direction
- messaging.eventhandling uses conversion, so a change to conversion can break messaging.eventhandling, while a change to messaging.eventhandling can't break conversion.
- Position
- Below the diagonal: messaging.eventhandling uses a module listed above it, which is the healthy direction.
11→7 messaging.eventhandling uses messaging.core.unitofwork✕
- Connections
- 12 pairs of types, where a type in messaging.eventhandling uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.messaging.eventhandling.DelegatingEventBus→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventhandling.DelegatingEventHandlingComponent→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventhandling.EventHandler→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventhandling.EventHandlingComponent→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventhandling.EventHandlingExceptionHandler→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventhandling.EventSink→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventhandling.EventSubscribers→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventhandling.InterceptingEventBus→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventhandling.InterceptingEventSink→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventhandling.InterceptingPublisher→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventhandling.SimpleEventBus→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventhandling.SimpleEventHandlingComponent→org.axonframework.messaging.core.unitofwork.ProcessingContext
- Direction
- messaging.eventhandling uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break messaging.eventhandling, while a change to messaging.eventhandling can't break messaging.core.unitofwork.
- Position
- Below the diagonal: messaging.eventhandling uses a module listed above it, which is the healthy direction.
11→10 messaging.eventhandling uses messaging.eventhandling.replay✕
- Connections
- 12 pairs of types, where a type in messaging.eventhandling uses a type in messaging.eventhandling.replay.
- The types involved
org.axonframework.messaging.eventhandling.DelegatingEventHandlingComponent→org.axonframework.messaging.eventhandling.replay.ReplayStatusChangedorg.axonframework.messaging.eventhandling.DelegatingEventHandlingComponent→org.axonframework.messaging.eventhandling.replay.ResetContextorg.axonframework.messaging.eventhandling.EventHandlingComponent→org.axonframework.messaging.eventhandling.replay.ReplayStatusChangedorg.axonframework.messaging.eventhandling.EventHandlingComponent→org.axonframework.messaging.eventhandling.replay.ReplayStatusChangedHandlerorg.axonframework.messaging.eventhandling.EventHandlingComponent→org.axonframework.messaging.eventhandling.replay.ResetContextorg.axonframework.messaging.eventhandling.EventHandlingComponent→org.axonframework.messaging.eventhandling.replay.ResetHandlerorg.axonframework.messaging.eventhandling.SimpleEventHandlingComponent→org.axonframework.messaging.eventhandling.replay.ReplayStatusChangedorg.axonframework.messaging.eventhandling.SimpleEventHandlingComponent→org.axonframework.messaging.eventhandling.replay.ReplayStatusChangedHandlerorg.axonframework.messaging.eventhandling.SimpleEventHandlingComponent→org.axonframework.messaging.eventhandling.replay.ReplayStatusChangedHandlerRegistryorg.axonframework.messaging.eventhandling.SimpleEventHandlingComponent→org.axonframework.messaging.eventhandling.replay.ResetContextorg.axonframework.messaging.eventhandling.SimpleEventHandlingComponent→org.axonframework.messaging.eventhandling.replay.ResetHandlerorg.axonframework.messaging.eventhandling.SimpleEventHandlingComponent→org.axonframework.messaging.eventhandling.replay.ResetHandlerRegistry
- Direction
- messaging.eventhandling uses messaging.eventhandling.replay, so a change to messaging.eventhandling.replay can break messaging.eventhandling, while a change to messaging.eventhandling can't break messaging.eventhandling.replay.
- Position
- Below the diagonal: messaging.eventhandling uses a module listed above it, which is the healthy direction.
11→13 messaging.eventhandling uses messaging.core.sequencing part of a loop✕
- Connections
- 1 pair of types, where a type in messaging.eventhandling uses a type in messaging.core.sequencing.
- The types involved
org.axonframework.messaging.eventhandling.SimpleEventHandlingComponent→org.axonframework.messaging.core.sequencing.SequencingPolicy
- Direction
- messaging.eventhandling uses messaging.core.sequencing, so a change to messaging.core.sequencing can break messaging.eventhandling, while a change to messaging.eventhandling can't break messaging.core.sequencing.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→15 messaging.eventhandling uses messaging.core part of a loop✕
- Connections
- 26 pairs of types, where a type in messaging.eventhandling uses a type in messaging.core. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
org.axonframework.messaging.eventhandling.DelegatingEventHandlingComponent→org.axonframework.messaging.core.Emptyorg.axonframework.messaging.eventhandling.DelegatingEventHandlingComponent→org.axonframework.messaging.core.Messageorg.axonframework.messaging.eventhandling.DelegatingEventHandlingComponent→org.axonframework.messaging.core.QualifiedNameorg.axonframework.messaging.eventhandling.EventBus→org.axonframework.messaging.core.SubscribableEventSourceorg.axonframework.messaging.eventhandling.EventHandler→org.axonframework.messaging.core.Emptyorg.axonframework.messaging.eventhandling.EventHandler→org.axonframework.messaging.core.Messageorg.axonframework.messaging.eventhandling.EventHandler→org.axonframework.messaging.core.MessageHandlerorg.axonframework.messaging.eventhandling.EventHandlerRegistry→org.axonframework.messaging.core.QualifiedNameorg.axonframework.messaging.eventhandling.EventHandlingComponent→org.axonframework.messaging.core.Emptyorg.axonframework.messaging.eventhandling.EventHandlingComponent→org.axonframework.messaging.core.Messageorg.axonframework.messaging.eventhandling.EventHandlingComponent→org.axonframework.messaging.core.QualifiedNameorg.axonframework.messaging.eventhandling.EventHandlingExceptionHandler→org.axonframework.messaging.core.Emptyorg.axonframework.messaging.eventhandling.EventHandlingExceptionHandler→org.axonframework.messaging.core.Messageorg.axonframework.messaging.eventhandling.EventHandlingExceptionHandler→org.axonframework.messaging.core.MessageHandlingExceptionHandlerorg.axonframework.messaging.eventhandling.EventMessage→org.axonframework.messaging.core.Messageorg.axonframework.messaging.eventhandling.GenericEventMessage→org.axonframework.messaging.core.Messageorg.axonframework.messaging.eventhandling.GenericEventMessage→org.axonframework.messaging.core.MessageDecoratororg.axonframework.messaging.eventhandling.GenericEventMessage→org.axonframework.messaging.core.MessageTypeorg.axonframework.messaging.eventhandling.InterceptingEventBus→org.axonframework.messaging.core.MessageDispatchInterceptororg.axonframework.messaging.eventhandling.InterceptingEventSink→org.axonframework.messaging.core.MessageDispatchInterceptororg.axonframework.messaging.eventhandling.InterceptingPublisher→org.axonframework.messaging.core.DefaultMessageDispatchInterceptorChainorg.axonframework.messaging.eventhandling.NoHandlerForEventException→org.axonframework.messaging.core.QualifiedNameorg.axonframework.messaging.eventhandling.SimpleEventBus→org.axonframework.messaging.core.ResourceKeyorg.axonframework.messaging.eventhandling.SimpleEventHandlingComponent→org.axonframework.messaging.core.Emptyorg.axonframework.messaging.eventhandling.SimpleEventHandlingComponent→org.axonframework.messaging.core.Message
- Direction
- messaging.eventhandling uses messaging.core, so a change to messaging.core can break messaging.eventhandling, while a change to messaging.eventhandling can't break messaging.core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→3 messaging.eventhandling.conversion uses common.infra✕
- Connections
- 1 pair of types, where a type in messaging.eventhandling.conversion uses a type in common.infra.
- The types involved
org.axonframework.messaging.eventhandling.conversion.DelegatingEventConverter→org.axonframework.common.infra.ComponentDescriptor
- Direction
- messaging.eventhandling.conversion uses common.infra, so a change to common.infra can break messaging.eventhandling.conversion, while a change to messaging.eventhandling.conversion can't break common.infra.
- Position
- Below the diagonal: messaging.eventhandling.conversion uses a module listed above it, which is the healthy direction.
12→6 messaging.eventhandling.conversion uses conversion✕
- Connections
- 2 pairs of types, where a type in messaging.eventhandling.conversion uses a type in conversion.
- The types involved
org.axonframework.messaging.eventhandling.conversion.DelegatingEventConverter→org.axonframework.conversion.Converterorg.axonframework.messaging.eventhandling.conversion.EventConverter→org.axonframework.conversion.Converter
- Direction
- messaging.eventhandling.conversion uses conversion, so a change to conversion can break messaging.eventhandling.conversion, while a change to messaging.eventhandling.conversion can't break conversion.
- Position
- Below the diagonal: messaging.eventhandling.conversion uses a module listed above it, which is the healthy direction.
12→9 messaging.eventhandling.conversion uses messaging.core.conversion✕
- Connections
- 1 pair of types, where a type in messaging.eventhandling.conversion uses a type in messaging.core.conversion.
- The types involved
org.axonframework.messaging.eventhandling.conversion.DelegatingEventConverter→org.axonframework.messaging.core.conversion.MessageConverter
- Direction
- messaging.eventhandling.conversion uses messaging.core.conversion, so a change to messaging.core.conversion can break messaging.eventhandling.conversion, while a change to messaging.eventhandling.conversion can't break messaging.core.conversion.
- Position
- Below the diagonal: messaging.eventhandling.conversion uses a module listed above it, which is the healthy direction.
13→7 messaging.core.sequencing uses messaging.core.unitofwork✕
- Connections
- 10 pairs of types, where a type in messaging.core.sequencing uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.messaging.core.sequencing.ExtractionSequencingPolicy→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.sequencing.FallbackSequencingPolicy→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.sequencing.FullConcurrencyPolicy→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.sequencing.HierarchicalSequencingPolicy→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.sequencing.MetadataSequencingPolicy→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.sequencing.NoOpSequencingPolicy→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.sequencing.RoutingKeySequencingPolicy→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.sequencing.SequencingPolicy→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.sequencing.SequentialPerAggregatePolicy→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.sequencing.SequentialPolicy→org.axonframework.messaging.core.unitofwork.ProcessingContext
- Direction
- messaging.core.sequencing uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break messaging.core.sequencing, while a change to messaging.core.sequencing can't break messaging.core.unitofwork.
- Position
- Below the diagonal: messaging.core.sequencing uses a module listed above it, which is the healthy direction.
13→8 messaging.core.sequencing uses messaging.commandhandling✕
- Connections
- 1 pair of types, where a type in messaging.core.sequencing uses a type in messaging.commandhandling.
- The types involved
org.axonframework.messaging.core.sequencing.RoutingKeySequencingPolicy→org.axonframework.messaging.commandhandling.CommandMessage
- Direction
- messaging.core.sequencing uses messaging.commandhandling, so a change to messaging.commandhandling can break messaging.core.sequencing, while a change to messaging.core.sequencing can't break messaging.commandhandling.
- Position
- Below the diagonal: messaging.core.sequencing uses a module listed above it, which is the healthy direction.
13→11 messaging.core.sequencing uses messaging.eventhandling✕
- Connections
- 1 pair of types, where a type in messaging.core.sequencing uses a type in messaging.eventhandling.
- The types involved
org.axonframework.messaging.core.sequencing.SequentialPerAggregatePolicy→org.axonframework.messaging.eventhandling.EventMessage
- Direction
- messaging.core.sequencing uses messaging.eventhandling, so a change to messaging.eventhandling can break messaging.core.sequencing, while a change to messaging.core.sequencing can't break messaging.eventhandling.
- Position
- Below the diagonal: messaging.core.sequencing uses a module listed above it, which is the healthy direction.
13→15 messaging.core.sequencing uses messaging.core part of a loop✕
- Connections
- 5 pairs of types, where a type in messaging.core.sequencing uses a type in messaging.core.
- The types involved
org.axonframework.messaging.core.sequencing.ExtractionSequencingPolicy→org.axonframework.messaging.core.Messageorg.axonframework.messaging.core.sequencing.FullConcurrencyPolicy→org.axonframework.messaging.core.Messageorg.axonframework.messaging.core.sequencing.MetadataSequencingPolicy→org.axonframework.messaging.core.Messageorg.axonframework.messaging.core.sequencing.NoOpSequencingPolicy→org.axonframework.messaging.core.Messageorg.axonframework.messaging.core.sequencing.SequentialPolicy→org.axonframework.messaging.core.Message
- Direction
- messaging.core.sequencing uses messaging.core, so a change to messaging.core can break messaging.core.sequencing, while a change to messaging.core.sequencing can't break messaging.core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→1 messaging.core.annotation uses common✕
- Connections
- 2 pairs of types, where a type in messaging.core.annotation uses a type in common.
- The types involved
org.axonframework.messaging.core.annotation.MessageHandlerInvocationException→org.axonframework.common.AxonExceptionorg.axonframework.messaging.core.annotation.UnsupportedHandlerException→org.axonframework.common.AxonConfigurationException
- Direction
- messaging.core.annotation uses common, so a change to common can break messaging.core.annotation, while a change to messaging.core.annotation can't break common.
- Position
- Below the diagonal: messaging.core.annotation uses a module listed above it, which is the healthy direction.
14→5 messaging.core.annotation uses common.configuration✕
- Connections
- 1 pair of types, where a type in messaging.core.annotation uses a type in common.configuration.
- The types involved
org.axonframework.messaging.core.annotation.InjectComponentParameterResolverFactory→org.axonframework.common.configuration.Configuration
- Direction
- messaging.core.annotation uses common.configuration, so a change to common.configuration can break messaging.core.annotation, while a change to messaging.core.annotation can't break common.configuration.
- Position
- Below the diagonal: messaging.core.annotation uses a module listed above it, which is the healthy direction.
14→7 messaging.core.annotation uses messaging.core.unitofwork✕
- Connections
- 12 pairs of types, where a type in messaging.core.annotation uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.messaging.core.annotation.AggregateTypeParameterResolver→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.annotation.AnnotatedMetadataParameterResolver→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.annotation.FixedValueParameterResolver→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.annotation.MessageHandlingMember→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.annotation.MessageIdentifierParameterResolver→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.annotation.MessageParameterResolver→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.annotation.MetadataParameterResolver→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.annotation.MethodInvokingMessageHandlingMember→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.annotation.ParameterResolver→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.annotation.PayloadParameterResolver→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.annotation.SourceIdParameterResolver→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.annotation.WrappedMessageHandlingMember→org.axonframework.messaging.core.unitofwork.ProcessingContext
- Direction
- messaging.core.annotation uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break messaging.core.annotation, while a change to messaging.core.annotation can't break messaging.core.unitofwork.
- Position
- Below the diagonal: messaging.core.annotation uses a module listed above it, which is the healthy direction.
14→13 messaging.core.annotation uses messaging.core.sequencing✕
- Connections
- 1 pair of types, where a type in messaging.core.annotation uses a type in messaging.core.sequencing.
- The types involved
org.axonframework.messaging.core.annotation.SequencingPolicy→org.axonframework.messaging.core.sequencing.SequencingPolicy
- Direction
- messaging.core.annotation uses messaging.core.sequencing, so a change to messaging.core.sequencing can break messaging.core.annotation, while a change to messaging.core.annotation can't break messaging.core.sequencing.
- Position
- Below the diagonal: messaging.core.annotation uses a module listed above it, which is the healthy direction.
14→15 messaging.core.annotation uses messaging.core part of a loop✕
- Connections
- 25 pairs of types, where a type in messaging.core.annotation uses a type in messaging.core.
- The types involved
org.axonframework.messaging.core.annotation.1→org.axonframework.messaging.core.MessageTypeorg.axonframework.messaging.core.annotation.AnnotatedHandlerAttributes→org.axonframework.messaging.core.SimpleHandlerAttributesorg.axonframework.messaging.core.annotation.AnnotatedHandlerInspector→org.axonframework.messaging.core.Messageorg.axonframework.messaging.core.annotation.AnnotatedHandlerInspector→org.axonframework.messaging.core.MessageStreamorg.axonframework.messaging.core.annotation.AnnotatedHandlerInspector→org.axonframework.messaging.core.MessageTypeResolverorg.axonframework.messaging.core.annotation.AnnotatedMessageHandlingMemberDefinition→org.axonframework.messaging.core.MessageStreamorg.axonframework.messaging.core.annotation.AnnotationMessageTypeResolver→org.axonframework.messaging.core.MessageTypeorg.axonframework.messaging.core.annotation.AnnotationMessageTypeResolver→org.axonframework.messaging.core.MessageTypeResolverorg.axonframework.messaging.core.annotation.HandlerDefinition→org.axonframework.messaging.core.MessageStreamorg.axonframework.messaging.core.annotation.Message→org.axonframework.messaging.core.Messageorg.axonframework.messaging.core.annotation.MessageHandler→org.axonframework.messaging.core.Messageorg.axonframework.messaging.core.annotation.MessageHandlingMember→org.axonframework.messaging.core.Messageorg.axonframework.messaging.core.annotation.MessageHandlingMember→org.axonframework.messaging.core.MessageStreamorg.axonframework.messaging.core.annotation.MessageParameterResolver→org.axonframework.messaging.core.Messageorg.axonframework.messaging.core.annotation.MessageStreamResolver→org.axonframework.messaging.core.Messageorg.axonframework.messaging.core.annotation.MessageStreamResolver→org.axonframework.messaging.core.MessageStreamorg.axonframework.messaging.core.annotation.MessageStreamResolverUtils→org.axonframework.messaging.core.Messageorg.axonframework.messaging.core.annotation.MessageStreamResolverUtils→org.axonframework.messaging.core.MessageStreamorg.axonframework.messaging.core.annotation.MessageStreamResolverUtils→org.axonframework.messaging.core.MessageTypeResolverorg.axonframework.messaging.core.annotation.MetadataParameterResolver→org.axonframework.messaging.core.Metadataorg.axonframework.messaging.core.annotation.MethodInvokingMessageHandlingMember→org.axonframework.messaging.core.Messageorg.axonframework.messaging.core.annotation.MethodInvokingMessageHandlingMember→org.axonframework.messaging.core.MessageStreamorg.axonframework.messaging.core.annotation.MultiHandlerDefinition→org.axonframework.messaging.core.MessageStreamorg.axonframework.messaging.core.annotation.WrappedMessageHandlingMember→org.axonframework.messaging.core.Messageorg.axonframework.messaging.core.annotation.WrappedMessageHandlingMember→org.axonframework.messaging.core.MessageStream
- Direction
- messaging.core.annotation uses messaging.core, so a change to messaging.core can break messaging.core.annotation, while a change to messaging.core.annotation can't break messaging.core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→1 messaging.core uses common✕
- Connections
- 13 pairs of types, where a type in messaging.core uses a type in common.
- The types involved
org.axonframework.messaging.core.EventPublicationFailedException→org.axonframework.common.AxonExceptionorg.axonframework.messaging.core.ExecutionException→org.axonframework.common.AxonTransientExceptionorg.axonframework.messaging.core.GenericMessage→org.axonframework.common.TypeReferenceorg.axonframework.messaging.core.HandlerExecutionException→org.axonframework.common.AxonExceptionorg.axonframework.messaging.core.HandlerExecutionException→org.axonframework.common.TypeReferenceorg.axonframework.messaging.core.IllegalPayloadAccessException→org.axonframework.common.AxonNonTransientExceptionorg.axonframework.messaging.core.Message→org.axonframework.common.TypeReferenceorg.axonframework.messaging.core.MessageDecorator→org.axonframework.common.TypeReferenceorg.axonframework.messaging.core.MessageTypeNotResolvedException→org.axonframework.common.AxonExceptionorg.axonframework.messaging.core.RemoteHandlingException→org.axonframework.common.AxonExceptionorg.axonframework.messaging.core.RemoteNonTransientHandlingException→org.axonframework.common.AxonNonTransientExceptionorg.axonframework.messaging.core.ResultMessage→org.axonframework.common.TypeReferenceorg.axonframework.messaging.core.SubscribableEventSource→org.axonframework.common.Registration
- Direction
- messaging.core uses common, so a change to common can break messaging.core, while a change to messaging.core can't break common.
- Position
- Below the diagonal: messaging.core uses a module listed above it, which is the healthy direction.
15→5 messaging.core uses common.configuration✕
- Connections
- 1 pair of types, where a type in messaging.core uses a type in common.configuration.
- The types involved
org.axonframework.messaging.core.ConfigurationApplicationContext→org.axonframework.common.configuration.Configuration
- Direction
- messaging.core uses common.configuration, so a change to common.configuration can break messaging.core, while a change to messaging.core can't break common.configuration.
- Position
- Below the diagonal: messaging.core uses a module listed above it, which is the healthy direction.
15→6 messaging.core uses conversion✕
- Connections
- 8 pairs of types, where a type in messaging.core uses a type in conversion.
- The types involved
org.axonframework.messaging.core.ConversionCache→org.axonframework.conversion.Converterorg.axonframework.messaging.core.GenericMessage→org.axonframework.conversion.Converterorg.axonframework.messaging.core.GenericResultMessage→org.axonframework.conversion.Converterorg.axonframework.messaging.core.HandlerExecutionException→org.axonframework.conversion.Converterorg.axonframework.messaging.core.Message→org.axonframework.conversion.Converterorg.axonframework.messaging.core.MessageDecorator→org.axonframework.conversion.Converterorg.axonframework.messaging.core.ResultMessage→org.axonframework.conversion.Converterorg.axonframework.messaging.core.Target→org.axonframework.conversion.Converter
- Direction
- messaging.core uses conversion, so a change to conversion can break messaging.core, while a change to messaging.core can't break conversion.
- Position
- Below the diagonal: messaging.core uses a module listed above it, which is the healthy direction.
15→7 messaging.core uses messaging.core.unitofwork✕
- Connections
- 9 pairs of types, where a type in messaging.core uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.messaging.core.DefaultMessageDispatchInterceptorChain→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.InterceptingDispatcher→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.Message→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.MessageDispatchInterceptor→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.MessageDispatchInterceptorChain→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.MessageHandlerInterceptor→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.MessageHandlerInterceptorChain→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.MessageHandlingExceptionHandler→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.SubscribableEventSource→org.axonframework.messaging.core.unitofwork.ProcessingContext
- Direction
- messaging.core uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break messaging.core, while a change to messaging.core can't break messaging.core.unitofwork.
- Position
- Below the diagonal: messaging.core uses a module listed above it, which is the healthy direction.
15→11 messaging.core uses messaging.eventhandling✕
- Connections
- 1 pair of types, where a type in messaging.core uses a type in messaging.eventhandling.
- The types involved
org.axonframework.messaging.core.SubscribableEventSource→org.axonframework.messaging.eventhandling.EventMessage
- Direction
- messaging.core uses messaging.eventhandling, so a change to messaging.eventhandling can break messaging.core, while a change to messaging.core can't break messaging.eventhandling.
- Position
- Below the diagonal: messaging.core uses a module listed above it, which is the healthy direction.
15→14 messaging.core uses messaging.core.annotation✕
- Connections
- 1 pair of types, where a type in messaging.core uses a type in messaging.core.annotation.
- The types involved
org.axonframework.messaging.core.SimpleHandlerAttributes→org.axonframework.messaging.core.annotation.HandlerAttributes
- Direction
- messaging.core uses messaging.core.annotation, so a change to messaging.core.annotation can break messaging.core, while a change to messaging.core can't break messaging.core.annotation.
- Position
- Below the diagonal: messaging.core uses a module listed above it, which is the healthy direction.
16→3 messaging.eventhandling.annotation uses common.infra✕
- Connections
- 1 pair of types, where a type in messaging.eventhandling.annotation uses a type in common.infra.
- The types involved
org.axonframework.messaging.eventhandling.annotation.AnnotatedEventHandlingComponent→org.axonframework.common.infra.ComponentDescriptor
- Direction
- messaging.eventhandling.annotation uses common.infra, so a change to common.infra can break messaging.eventhandling.annotation, while a change to messaging.eventhandling.annotation can't break common.infra.
- Position
- Below the diagonal: messaging.eventhandling.annotation uses a module listed above it, which is the healthy direction.
16→5 messaging.eventhandling.annotation uses common.configuration✕
- Connections
- 2 pairs of types, where a type in messaging.eventhandling.annotation uses a type in common.configuration.
- The types involved
org.axonframework.messaging.eventhandling.annotation.EventAppenderParameterResolverFactoryConfigurationEnhancer→org.axonframework.common.configuration.ComponentRegistryorg.axonframework.messaging.eventhandling.annotation.EventAppenderParameterResolverFactoryConfigurationEnhancer→org.axonframework.common.configuration.ConfigurationEnhancer
- Direction
- messaging.eventhandling.annotation uses common.configuration, so a change to common.configuration can break messaging.eventhandling.annotation, while a change to messaging.eventhandling.annotation can't break common.configuration.
- Position
- Below the diagonal: messaging.eventhandling.annotation uses a module listed above it, which is the healthy direction.
16→7 messaging.eventhandling.annotation uses messaging.core.unitofwork✕
- Connections
- 6 pairs of types, where a type in messaging.eventhandling.annotation uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.messaging.eventhandling.annotation.1→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventhandling.annotation.1962→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventhandling.annotation.AnnotatedEventHandlingComponent→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventhandling.annotation.MethodEventMessageHandlingMember→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventhandling.annotation.SequenceNumberParameterResolver→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventhandling.annotation.TimestampParameterResolver→org.axonframework.messaging.core.unitofwork.ProcessingContext
- Direction
- messaging.eventhandling.annotation uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break messaging.eventhandling.annotation, while a change to messaging.eventhandling.annotation can't break messaging.core.unitofwork.
- Position
- Below the diagonal: messaging.eventhandling.annotation uses a module listed above it, which is the healthy direction.
16→10 messaging.eventhandling.annotation uses messaging.eventhandling.replay✕
- Connections
- 4 pairs of types, where a type in messaging.eventhandling.annotation uses a type in messaging.eventhandling.replay.
- The types involved
org.axonframework.messaging.eventhandling.annotation.AnnotatedEventHandlingComponent→org.axonframework.messaging.eventhandling.replay.ReplayStatusChangedorg.axonframework.messaging.eventhandling.annotation.AnnotatedEventHandlingComponent→org.axonframework.messaging.eventhandling.replay.ReplayStatusChangedHandlerorg.axonframework.messaging.eventhandling.annotation.AnnotatedEventHandlingComponent→org.axonframework.messaging.eventhandling.replay.ResetContextorg.axonframework.messaging.eventhandling.annotation.AnnotatedEventHandlingComponent→org.axonframework.messaging.eventhandling.replay.ResetHandler
- Direction
- messaging.eventhandling.annotation uses messaging.eventhandling.replay, so a change to messaging.eventhandling.replay can break messaging.eventhandling.annotation, while a change to messaging.eventhandling.annotation can't break messaging.eventhandling.replay.
- Position
- Below the diagonal: messaging.eventhandling.annotation uses a module listed above it, which is the healthy direction.
16→11 messaging.eventhandling.annotation uses messaging.eventhandling✕
- Connections
- 5 pairs of types, where a type in messaging.eventhandling.annotation uses a type in messaging.eventhandling.
- The types involved
org.axonframework.messaging.eventhandling.annotation.AnnotatedEventHandlingComponent→org.axonframework.messaging.eventhandling.EventHandlerorg.axonframework.messaging.eventhandling.annotation.AnnotatedEventHandlingComponent→org.axonframework.messaging.eventhandling.EventHandlingComponentorg.axonframework.messaging.eventhandling.annotation.AnnotatedEventHandlingComponent→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.messaging.eventhandling.annotation.AnnotatedEventHandlingComponent→org.axonframework.messaging.eventhandling.SimpleEventHandlingComponentorg.axonframework.messaging.eventhandling.annotation.SequencingPolicyEventMessageHandlingMember→org.axonframework.messaging.eventhandling.EventMessage
- Direction
- messaging.eventhandling.annotation uses messaging.eventhandling, so a change to messaging.eventhandling can break messaging.eventhandling.annotation, while a change to messaging.eventhandling.annotation can't break messaging.eventhandling.
- Position
- Below the diagonal: messaging.eventhandling.annotation uses a module listed above it, which is the healthy direction.
16→12 messaging.eventhandling.annotation uses messaging.eventhandling.conversion✕
- Connections
- 1 pair of types, where a type in messaging.eventhandling.annotation uses a type in messaging.eventhandling.conversion.
- The types involved
org.axonframework.messaging.eventhandling.annotation.AnnotatedEventHandlingComponent→org.axonframework.messaging.eventhandling.conversion.EventConverter
- Direction
- messaging.eventhandling.annotation uses messaging.eventhandling.conversion, so a change to messaging.eventhandling.conversion can break messaging.eventhandling.annotation, while a change to messaging.eventhandling.annotation can't break messaging.eventhandling.conversion.
- Position
- Below the diagonal: messaging.eventhandling.annotation uses a module listed above it, which is the healthy direction.
16→13 messaging.eventhandling.annotation uses messaging.core.sequencing✕
- Connections
- 2 pairs of types, where a type in messaging.eventhandling.annotation uses a type in messaging.core.sequencing.
- The types involved
org.axonframework.messaging.eventhandling.annotation.AnnotatedEventHandlingComponent→org.axonframework.messaging.core.sequencing.SequencingPolicyorg.axonframework.messaging.eventhandling.annotation.SequencingPolicyEventMessageHandlingMember→org.axonframework.messaging.core.sequencing.SequencingPolicy
- Direction
- messaging.eventhandling.annotation uses messaging.core.sequencing, so a change to messaging.core.sequencing can break messaging.eventhandling.annotation, while a change to messaging.eventhandling.annotation can't break messaging.core.sequencing.
- Position
- Below the diagonal: messaging.eventhandling.annotation uses a module listed above it, which is the healthy direction.
16→14 messaging.eventhandling.annotation uses messaging.core.annotation✕
- Connections
- 23 pairs of types, where a type in messaging.eventhandling.annotation uses a type in messaging.core.annotation.
- The types involved
org.axonframework.messaging.eventhandling.annotation.1→org.axonframework.messaging.core.annotation.ParameterResolverorg.axonframework.messaging.eventhandling.annotation.1962→org.axonframework.messaging.core.annotation.ParameterResolverorg.axonframework.messaging.eventhandling.annotation.AnnotatedEventHandlingComponent→org.axonframework.messaging.core.annotation.AnnotatedHandlerInspectororg.axonframework.messaging.eventhandling.annotation.AnnotatedEventHandlingComponent→org.axonframework.messaging.core.annotation.HandlerDefinitionorg.axonframework.messaging.eventhandling.annotation.AnnotatedEventHandlingComponent→org.axonframework.messaging.core.annotation.MessageHandlingMemberorg.axonframework.messaging.eventhandling.annotation.AnnotatedEventHandlingComponent→org.axonframework.messaging.core.annotation.ParameterResolverFactoryorg.axonframework.messaging.eventhandling.annotation.EventAppenderParameterResolverFactory→org.axonframework.messaging.core.annotation.ParameterResolverorg.axonframework.messaging.eventhandling.annotation.EventAppenderParameterResolverFactory→org.axonframework.messaging.core.annotation.ParameterResolverFactoryorg.axonframework.messaging.eventhandling.annotation.EventHandlingMember→org.axonframework.messaging.core.annotation.MessageHandlingMemberorg.axonframework.messaging.eventhandling.annotation.MethodEventHandlerDefinition→org.axonframework.messaging.core.annotation.HandlerEnhancerDefinitionorg.axonframework.messaging.eventhandling.annotation.MethodEventHandlerDefinition→org.axonframework.messaging.core.annotation.MessageHandlingMemberorg.axonframework.messaging.eventhandling.annotation.MethodEventMessageHandlingMember→org.axonframework.messaging.core.annotation.MessageHandlingMemberorg.axonframework.messaging.eventhandling.annotation.MethodEventMessageHandlingMember→org.axonframework.messaging.core.annotation.WrappedMessageHandlingMemberorg.axonframework.messaging.eventhandling.annotation.MethodSequencingPolicyEventHandlerDefinition→org.axonframework.messaging.core.annotation.HandlerEnhancerDefinitionorg.axonframework.messaging.eventhandling.annotation.MethodSequencingPolicyEventHandlerDefinition→org.axonframework.messaging.core.annotation.MessageHandlingMemberorg.axonframework.messaging.eventhandling.annotation.SequenceNumberParameterResolver→org.axonframework.messaging.core.annotation.ParameterResolverorg.axonframework.messaging.eventhandling.annotation.SequenceNumberParameterResolverFactory→org.axonframework.messaging.core.annotation.AbstractAnnotatedParameterResolverFactoryorg.axonframework.messaging.eventhandling.annotation.SequenceNumberParameterResolverFactory→org.axonframework.messaging.core.annotation.ParameterResolverorg.axonframework.messaging.eventhandling.annotation.SequencingPolicyEventMessageHandlingMember→org.axonframework.messaging.core.annotation.MessageHandlingMemberorg.axonframework.messaging.eventhandling.annotation.SequencingPolicyEventMessageHandlingMember→org.axonframework.messaging.core.annotation.WrappedMessageHandlingMemberorg.axonframework.messaging.eventhandling.annotation.TimestampParameterResolver→org.axonframework.messaging.core.annotation.ParameterResolverorg.axonframework.messaging.eventhandling.annotation.TimestampParameterResolverFactory→org.axonframework.messaging.core.annotation.AbstractAnnotatedParameterResolverFactoryorg.axonframework.messaging.eventhandling.annotation.TimestampParameterResolverFactory→org.axonframework.messaging.core.annotation.ParameterResolver
- Direction
- messaging.eventhandling.annotation uses messaging.core.annotation, so a change to messaging.core.annotation can break messaging.eventhandling.annotation, while a change to messaging.eventhandling.annotation can't break messaging.core.annotation.
- Position
- Below the diagonal: messaging.eventhandling.annotation uses a module listed above it, which is the healthy direction.
16→15 messaging.eventhandling.annotation uses messaging.core✕
- Connections
- 5 pairs of types, where a type in messaging.eventhandling.annotation uses a type in messaging.core.
- The types involved
org.axonframework.messaging.eventhandling.annotation.AnnotatedEventHandlingComponent→org.axonframework.messaging.core.Emptyorg.axonframework.messaging.eventhandling.annotation.AnnotatedEventHandlingComponent→org.axonframework.messaging.core.Messageorg.axonframework.messaging.eventhandling.annotation.AnnotatedEventHandlingComponent→org.axonframework.messaging.core.MessageTypeResolverorg.axonframework.messaging.eventhandling.annotation.AnnotatedEventHandlingComponent→org.axonframework.messaging.core.QualifiedNameorg.axonframework.messaging.eventhandling.annotation.MethodEventMessageHandlingMember→org.axonframework.messaging.core.Message
- Direction
- messaging.eventhandling.annotation uses messaging.core, so a change to messaging.core can break messaging.eventhandling.annotation, while a change to messaging.eventhandling.annotation can't break messaging.core.
- Position
- Below the diagonal: messaging.eventhandling.annotation uses a module listed above it, which is the healthy direction.
17→6 messaging.eventhandling.processing.streaming.token uses conversion✕
- Connections
- 1 pair of types, where a type in messaging.eventhandling.processing.streaming.token uses a type in conversion.
- The types involved
org.axonframework.messaging.eventhandling.processing.streaming.token.ReplayToken→org.axonframework.conversion.Converter
- Direction
- messaging.eventhandling.processing.streaming.token uses conversion, so a change to conversion can break messaging.eventhandling.processing.streaming.token, while a change to messaging.eventhandling.processing.streaming.token can't break conversion.
- Position
- Below the diagonal: messaging.eventhandling.processing.streaming.token uses a module listed above it, which is the healthy direction.
17→15 messaging.eventhandling.processing.streaming.token uses messaging.core✕
- Connections
- 2 pairs of types, where a type in messaging.eventhandling.processing.streaming.token uses a type in messaging.core.
- The types involved
org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingToken→org.axonframework.messaging.core.Contextorg.axonframework.messaging.eventhandling.processing.streaming.token.TrackingToken→org.axonframework.messaging.core.ResourceKey
- Direction
- messaging.eventhandling.processing.streaming.token uses messaging.core, so a change to messaging.core can break messaging.eventhandling.processing.streaming.token, while a change to messaging.eventhandling.processing.streaming.token can't break messaging.core.
- Position
- Below the diagonal: messaging.eventhandling.processing.streaming.token uses a module listed above it, which is the healthy direction.
18→1 messaging.queryhandling uses common✕
- Connections
- 5 pairs of types, where a type in messaging.queryhandling uses a type in common.
- The types involved
org.axonframework.messaging.queryhandling.CompletedEmitterException→org.axonframework.common.AxonNonTransientExceptionorg.axonframework.messaging.queryhandling.NoHandlerForQueryException→org.axonframework.common.AxonExceptionorg.axonframework.messaging.queryhandling.QueryMessage→org.axonframework.common.TypeReferenceorg.axonframework.messaging.queryhandling.QueryResponseMessage→org.axonframework.common.TypeReferenceorg.axonframework.messaging.queryhandling.SubscriptionQueryUpdateMessage→org.axonframework.common.TypeReference
- Direction
- messaging.queryhandling uses common, so a change to common can break messaging.queryhandling, while a change to messaging.queryhandling can't break common.
- Position
- Below the diagonal: messaging.queryhandling uses a module listed above it, which is the healthy direction.
18→3 messaging.queryhandling uses common.infra✕
- Connections
- 6 pairs of types, where a type in messaging.queryhandling uses a type in common.infra.
- The types involved
org.axonframework.messaging.queryhandling.QueryBus→org.axonframework.common.infra.DescribableComponentorg.axonframework.messaging.queryhandling.QueryHandlingComponent→org.axonframework.common.infra.DescribableComponentorg.axonframework.messaging.queryhandling.QueryUpdateEmitter→org.axonframework.common.infra.DescribableComponentorg.axonframework.messaging.queryhandling.SimpleQueryBus→org.axonframework.common.infra.ComponentDescriptororg.axonframework.messaging.queryhandling.SimpleQueryHandlingComponent→org.axonframework.common.infra.ComponentDescriptororg.axonframework.messaging.queryhandling.SimpleQueryUpdateEmitter→org.axonframework.common.infra.ComponentDescriptor
- Direction
- messaging.queryhandling uses common.infra, so a change to common.infra can break messaging.queryhandling, while a change to messaging.queryhandling can't break common.infra.
- Position
- Below the diagonal: messaging.queryhandling uses a module listed above it, which is the healthy direction.
18→5 messaging.queryhandling uses common.configuration✕
- Connections
- 1 pair of types, where a type in messaging.queryhandling uses a type in common.configuration.
- The types involved
org.axonframework.messaging.queryhandling.QueryShutdownManager→org.axonframework.common.configuration.LifecycleRegistry
- Direction
- messaging.queryhandling uses common.configuration, so a change to common.configuration can break messaging.queryhandling, while a change to messaging.queryhandling can't break common.configuration.
- Position
- Below the diagonal: messaging.queryhandling uses a module listed above it, which is the healthy direction.
18→6 messaging.queryhandling uses conversion✕
- Connections
- 7 pairs of types, where a type in messaging.queryhandling uses a type in conversion.
- The types involved
org.axonframework.messaging.queryhandling.GenericQueryMessage→org.axonframework.conversion.Converterorg.axonframework.messaging.queryhandling.GenericQueryResponseMessage→org.axonframework.conversion.Converterorg.axonframework.messaging.queryhandling.GenericSubscriptionQueryUpdateMessage→org.axonframework.conversion.Converterorg.axonframework.messaging.queryhandling.QueryExecutionException→org.axonframework.conversion.Converterorg.axonframework.messaging.queryhandling.QueryMessage→org.axonframework.conversion.Converterorg.axonframework.messaging.queryhandling.QueryResponseMessage→org.axonframework.conversion.Converterorg.axonframework.messaging.queryhandling.SubscriptionQueryUpdateMessage→org.axonframework.conversion.Converter
- Direction
- messaging.queryhandling uses conversion, so a change to conversion can break messaging.queryhandling, while a change to messaging.queryhandling can't break conversion.
- Position
- Below the diagonal: messaging.queryhandling uses a module listed above it, which is the healthy direction.
18→7 messaging.queryhandling uses messaging.core.unitofwork✕
- Connections
- 10 pairs of types, where a type in messaging.queryhandling uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.messaging.queryhandling.1→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.queryhandling.2008→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.queryhandling.QueryBus→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.queryhandling.QueryHandler→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.queryhandling.QueryHandlingExceptionHandler→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.queryhandling.QueryUpdateEmitter→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.queryhandling.SimpleQueryBus→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.queryhandling.SimpleQueryBus→org.axonframework.messaging.core.unitofwork.UnitOfWorkFactoryorg.axonframework.messaging.queryhandling.SimpleQueryHandlingComponent→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.queryhandling.SimpleQueryUpdateEmitter→org.axonframework.messaging.core.unitofwork.ProcessingContext
- Direction
- messaging.queryhandling uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break messaging.queryhandling, while a change to messaging.queryhandling can't break messaging.core.unitofwork.
- Position
- Below the diagonal: messaging.queryhandling uses a module listed above it, which is the healthy direction.
18→9 messaging.queryhandling uses messaging.core.conversion✕
- Connections
- 1 pair of types, where a type in messaging.queryhandling uses a type in messaging.core.conversion.
- The types involved
org.axonframework.messaging.queryhandling.SimpleQueryUpdateEmitter→org.axonframework.messaging.core.conversion.MessageConverter
- Direction
- messaging.queryhandling uses messaging.core.conversion, so a change to messaging.core.conversion can break messaging.queryhandling, while a change to messaging.queryhandling can't break messaging.core.conversion.
- Position
- Below the diagonal: messaging.queryhandling uses a module listed above it, which is the healthy direction.
18→14 messaging.queryhandling uses messaging.core.annotation✕
- Connections
- 4 pairs of types, where a type in messaging.queryhandling uses a type in messaging.core.annotation.
- The types involved
org.axonframework.messaging.queryhandling.1→org.axonframework.messaging.core.annotation.ParameterResolverorg.axonframework.messaging.queryhandling.2008→org.axonframework.messaging.core.annotation.ParameterResolverorg.axonframework.messaging.queryhandling.QueryUpdateEmitterParameterResolverFactory→org.axonframework.messaging.core.annotation.ParameterResolverorg.axonframework.messaging.queryhandling.QueryUpdateEmitterParameterResolverFactory→org.axonframework.messaging.core.annotation.ParameterResolverFactory
- Direction
- messaging.queryhandling uses messaging.core.annotation, so a change to messaging.core.annotation can break messaging.queryhandling, while a change to messaging.queryhandling can't break messaging.core.annotation.
- Position
- Below the diagonal: messaging.queryhandling uses a module listed above it, which is the healthy direction.
18→15 messaging.queryhandling uses messaging.core✕
- Connections
- 30 pairs of types, where a type in messaging.queryhandling uses a type in messaging.core. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
org.axonframework.messaging.queryhandling.DuplicateQueryHandlerSubscriptionException→org.axonframework.messaging.core.QualifiedNameorg.axonframework.messaging.queryhandling.GenericQueryMessage→org.axonframework.messaging.core.Messageorg.axonframework.messaging.queryhandling.GenericQueryMessage→org.axonframework.messaging.core.MessageDecoratororg.axonframework.messaging.queryhandling.GenericQueryMessage→org.axonframework.messaging.core.MessageTypeorg.axonframework.messaging.queryhandling.GenericQueryResponseMessage→org.axonframework.messaging.core.GenericResultMessageorg.axonframework.messaging.queryhandling.GenericQueryResponseMessage→org.axonframework.messaging.core.Messageorg.axonframework.messaging.queryhandling.GenericQueryResponseMessage→org.axonframework.messaging.core.MessageTypeorg.axonframework.messaging.queryhandling.GenericSubscriptionQueryUpdateMessage→org.axonframework.messaging.core.GenericResultMessageorg.axonframework.messaging.queryhandling.GenericSubscriptionQueryUpdateMessage→org.axonframework.messaging.core.Messageorg.axonframework.messaging.queryhandling.GenericSubscriptionQueryUpdateMessage→org.axonframework.messaging.core.MessageTypeorg.axonframework.messaging.queryhandling.QueryBus→org.axonframework.messaging.core.MessageStreamorg.axonframework.messaging.queryhandling.QueryExecutionException→org.axonframework.messaging.core.HandlerExecutionExceptionorg.axonframework.messaging.queryhandling.QueryHandler→org.axonframework.messaging.core.MessageHandlerorg.axonframework.messaging.queryhandling.QueryHandler→org.axonframework.messaging.core.MessageStreamorg.axonframework.messaging.queryhandling.QueryHandlerRegistry→org.axonframework.messaging.core.QualifiedNameorg.axonframework.messaging.queryhandling.QueryHandlingComponent→org.axonframework.messaging.core.QualifiedNameorg.axonframework.messaging.queryhandling.QueryHandlingExceptionHandler→org.axonframework.messaging.core.MessageHandlingExceptionHandlerorg.axonframework.messaging.queryhandling.QueryHandlingExceptionHandler→org.axonframework.messaging.core.MessageStreamorg.axonframework.messaging.queryhandling.QueryMessage→org.axonframework.messaging.core.Messageorg.axonframework.messaging.queryhandling.QueryResponseMessage→org.axonframework.messaging.core.ResultMessageorg.axonframework.messaging.queryhandling.QueryShutdownManager→org.axonframework.messaging.core.MessageStreamorg.axonframework.messaging.queryhandling.QueryUpdateEmitter→org.axonframework.messaging.core.QualifiedNameorg.axonframework.messaging.queryhandling.SimpleQueryBus→org.axonframework.messaging.core.MessageStreamorg.axonframework.messaging.queryhandling.SimpleQueryBus→org.axonframework.messaging.core.QualifiedNameorg.axonframework.messaging.queryhandling.SimpleQueryBus→org.axonframework.messaging.core.QueueMessageStream
- Direction
- messaging.queryhandling uses messaging.core, so a change to messaging.core can break messaging.queryhandling, while a change to messaging.queryhandling can't break messaging.core.
- Position
- Below the diagonal: messaging.queryhandling uses a module listed above it, which is the healthy direction.
19→3 messaging.tracing uses common.infra✕
- Connections
- 2 pairs of types, where a type in messaging.tracing uses a type in common.infra.
- The types involved
org.axonframework.messaging.tracing.LoggingSpanFactory→org.axonframework.common.infra.ComponentDescriptororg.axonframework.messaging.tracing.SpanFactory→org.axonframework.common.infra.DescribableComponent
- Direction
- messaging.tracing uses common.infra, so a change to common.infra can break messaging.tracing, while a change to messaging.tracing can't break common.infra.
- Position
- Below the diagonal: messaging.tracing uses a module listed above it, which is the healthy direction.
19→7 messaging.tracing uses messaging.core.unitofwork✕
- Connections
- 5 pairs of types, where a type in messaging.tracing uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.messaging.tracing.LoggingSpanFactory→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.tracing.Span→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.tracing.SpanAttributesProvider→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.tracing.SpanFactory→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.tracing.SpanScope→org.axonframework.messaging.core.unitofwork.ProcessingContext
- Direction
- messaging.tracing uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break messaging.tracing, while a change to messaging.tracing can't break messaging.core.unitofwork.
- Position
- Below the diagonal: messaging.tracing uses a module listed above it, which is the healthy direction.
19→15 messaging.tracing uses messaging.core✕
- Connections
- 10 pairs of types, where a type in messaging.tracing uses a type in messaging.core.
- The types involved
org.axonframework.messaging.tracing.LoggingSpanFactory→org.axonframework.messaging.core.Messageorg.axonframework.messaging.tracing.Span→org.axonframework.messaging.core.MessageStreamorg.axonframework.messaging.tracing.SpanAttributesProvider→org.axonframework.messaging.core.Messageorg.axonframework.messaging.tracing.SpanFactory→org.axonframework.messaging.core.Messageorg.axonframework.messaging.tracing.SpanScope→org.axonframework.messaging.core.ResourceKeyorg.axonframework.messaging.tracing.SpanScopedMessageStream→org.axonframework.messaging.core.AbstractMessageStreamorg.axonframework.messaging.tracing.SpanScopedMessageStream→org.axonframework.messaging.core.Entryorg.axonframework.messaging.tracing.SpanScopedMessageStream→org.axonframework.messaging.core.FetchResultorg.axonframework.messaging.tracing.SpanScopedMessageStream→org.axonframework.messaging.core.MessageStreamorg.axonframework.messaging.tracing.SpanScopedMessageStream→org.axonframework.messaging.core.NoValue
- Direction
- messaging.tracing uses messaging.core, so a change to messaging.core can break messaging.tracing, while a change to messaging.tracing can't break messaging.core.
- Position
- Below the diagonal: messaging.tracing uses a module listed above it, which is the healthy direction.
20→1 modelling.repository uses common✕
- Connections
- 1 pair of types, where a type in modelling.repository uses a type in common.
- The types involved
org.axonframework.modelling.repository.EntityNotFoundException→org.axonframework.common.AxonNonTransientException
- Direction
- modelling.repository uses common, so a change to common can break modelling.repository, while a change to modelling.repository can't break common.
- Position
- Below the diagonal: modelling.repository uses a module listed above it, which is the healthy direction.
20→3 modelling.repository uses common.infra✕
- Connections
- 3 pairs of types, where a type in modelling.repository uses a type in common.infra.
- The types involved
org.axonframework.modelling.repository.InMemoryRepository→org.axonframework.common.infra.ComponentDescriptororg.axonframework.modelling.repository.Repository→org.axonframework.common.infra.DescribableComponentorg.axonframework.modelling.repository.SimpleRepository→org.axonframework.common.infra.ComponentDescriptor
- Direction
- modelling.repository uses common.infra, so a change to common.infra can break modelling.repository, while a change to modelling.repository can't break common.infra.
- Position
- Below the diagonal: modelling.repository uses a module listed above it, which is the healthy direction.
20→7 modelling.repository uses messaging.core.unitofwork✕
- Connections
- 6 pairs of types, where a type in modelling.repository uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.modelling.repository.InMemoryRepository→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.modelling.repository.LifecycleManagement→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.modelling.repository.Repository→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.modelling.repository.SimpleRepository→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.modelling.repository.SimpleRepositoryEntityLoader→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.modelling.repository.SimpleRepositoryEntityPersister→org.axonframework.messaging.core.unitofwork.ProcessingContext
- Direction
- modelling.repository uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break modelling.repository, while a change to modelling.repository can't break messaging.core.unitofwork.
- Position
- Below the diagonal: modelling.repository uses a module listed above it, which is the healthy direction.
20→15 modelling.repository uses messaging.core✕
- Connections
- 1 pair of types, where a type in modelling.repository uses a type in messaging.core.
- The types involved
org.axonframework.modelling.repository.SimpleRepository→org.axonframework.messaging.core.ResourceKey
- Direction
- modelling.repository uses messaging.core, so a change to messaging.core can break modelling.repository, while a change to modelling.repository can't break messaging.core.
- Position
- Below the diagonal: modelling.repository uses a module listed above it, which is the healthy direction.
21→1 messaging.core.interception uses common✕
- Connections
- 17 pairs of types, where a type in messaging.core.interception uses a type in common.
- The types involved
org.axonframework.messaging.core.interception.1→org.axonframework.common.TypeReferenceorg.axonframework.messaging.core.interception.2→org.axonframework.common.TypeReferenceorg.axonframework.messaging.core.interception.2274→org.axonframework.common.TypeReferenceorg.axonframework.messaging.core.interception.2355→org.axonframework.common.TypeReferenceorg.axonframework.messaging.core.interception.2426→org.axonframework.common.TypeReferenceorg.axonframework.messaging.core.interception.2508→org.axonframework.common.TypeReferenceorg.axonframework.messaging.core.interception.2574→org.axonframework.common.TypeReferenceorg.axonframework.messaging.core.interception.2657→org.axonframework.common.TypeReferenceorg.axonframework.messaging.core.interception.2722→org.axonframework.common.TypeReferenceorg.axonframework.messaging.core.interception.2806→org.axonframework.common.TypeReferenceorg.axonframework.messaging.core.interception.2993→org.axonframework.common.TypeReferenceorg.axonframework.messaging.core.interception.3→org.axonframework.common.TypeReferenceorg.axonframework.messaging.core.interception.4→org.axonframework.common.TypeReferenceorg.axonframework.messaging.core.interception.5→org.axonframework.common.TypeReferenceorg.axonframework.messaging.core.interception.DefaultDispatchInterceptorRegistry→org.axonframework.common.TypeReferenceorg.axonframework.messaging.core.interception.DefaultHandlerInterceptorRegistry→org.axonframework.common.TypeReferenceorg.axonframework.messaging.core.interception.JSR303ViolationException→org.axonframework.common.AxonNonTransientException
- Direction
- messaging.core.interception uses common, so a change to common can break messaging.core.interception, while a change to messaging.core.interception can't break common.
- Position
- Below the diagonal: messaging.core.interception uses a module listed above it, which is the healthy direction.
21→3 messaging.core.interception uses common.infra✕
- Connections
- 4 pairs of types, where a type in messaging.core.interception uses a type in common.infra.
- The types involved
org.axonframework.messaging.core.interception.DefaultDispatchInterceptorRegistry→org.axonframework.common.infra.ComponentDescriptororg.axonframework.messaging.core.interception.DefaultHandlerInterceptorRegistry→org.axonframework.common.infra.ComponentDescriptororg.axonframework.messaging.core.interception.DispatchInterceptorRegistry→org.axonframework.common.infra.DescribableComponentorg.axonframework.messaging.core.interception.HandlerInterceptorRegistry→org.axonframework.common.infra.DescribableComponent
- Direction
- messaging.core.interception uses common.infra, so a change to common.infra can break messaging.core.interception, while a change to messaging.core.interception can't break common.infra.
- Position
- Below the diagonal: messaging.core.interception uses a module listed above it, which is the healthy direction.
21→5 messaging.core.interception uses common.configuration✕
- Connections
- 14 pairs of types, where a type in messaging.core.interception uses a type in common.configuration.
- The types involved
org.axonframework.messaging.core.interception.DefaultDispatchInterceptorRegistry→org.axonframework.common.configuration.ComponentBuilderorg.axonframework.messaging.core.interception.DefaultDispatchInterceptorRegistry→org.axonframework.common.configuration.ComponentDefinitionorg.axonframework.messaging.core.interception.DefaultDispatchInterceptorRegistry→org.axonframework.common.configuration.Configurationorg.axonframework.messaging.core.interception.DefaultHandlerInterceptorRegistry→org.axonframework.common.configuration.ComponentBuilderorg.axonframework.messaging.core.interception.DefaultHandlerInterceptorRegistry→org.axonframework.common.configuration.ComponentDefinitionorg.axonframework.messaging.core.interception.DefaultHandlerInterceptorRegistry→org.axonframework.common.configuration.Configurationorg.axonframework.messaging.core.interception.DispatchInterceptorFactory→org.axonframework.common.configuration.Configurationorg.axonframework.messaging.core.interception.DispatchInterceptorRegistry→org.axonframework.common.configuration.ComponentBuilderorg.axonframework.messaging.core.interception.DispatchInterceptorRegistry→org.axonframework.common.configuration.Configurationorg.axonframework.messaging.core.interception.GenericInterceptorDefinition→org.axonframework.common.configuration.ComponentBuilderorg.axonframework.messaging.core.interception.GenericInterceptorDefinition→org.axonframework.common.configuration.LazyInitializedComponentDefinitionorg.axonframework.messaging.core.interception.HandlerInterceptorFactory→org.axonframework.common.configuration.Configurationorg.axonframework.messaging.core.interception.HandlerInterceptorRegistry→org.axonframework.common.configuration.ComponentBuilderorg.axonframework.messaging.core.interception.HandlerInterceptorRegistry→org.axonframework.common.configuration.Configuration
- Direction
- messaging.core.interception uses common.configuration, so a change to common.configuration can break messaging.core.interception, while a change to messaging.core.interception can't break common.configuration.
- Position
- Below the diagonal: messaging.core.interception uses a module listed above it, which is the healthy direction.
21→7 messaging.core.interception uses messaging.core.unitofwork✕
- Connections
- 3 pairs of types, where a type in messaging.core.interception uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.messaging.core.interception.BeanValidationInterceptor→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.interception.CorrelationDataInterceptor→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.core.interception.LoggingInterceptor→org.axonframework.messaging.core.unitofwork.ProcessingContext
- Direction
- messaging.core.interception uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break messaging.core.interception, while a change to messaging.core.interception can't break messaging.core.unitofwork.
- Position
- Below the diagonal: messaging.core.interception uses a module listed above it, which is the healthy direction.
21→8 messaging.core.interception uses messaging.commandhandling✕
- Connections
- 4 pairs of types, where a type in messaging.core.interception uses a type in messaging.commandhandling.
- The types involved
org.axonframework.messaging.core.interception.DefaultDispatchInterceptorRegistry→org.axonframework.messaging.commandhandling.CommandMessageorg.axonframework.messaging.core.interception.DefaultHandlerInterceptorRegistry→org.axonframework.messaging.commandhandling.CommandMessageorg.axonframework.messaging.core.interception.DispatchInterceptorRegistry→org.axonframework.messaging.commandhandling.CommandMessageorg.axonframework.messaging.core.interception.HandlerInterceptorRegistry→org.axonframework.messaging.commandhandling.CommandMessage
- Direction
- messaging.core.interception uses messaging.commandhandling, so a change to messaging.commandhandling can break messaging.core.interception, while a change to messaging.core.interception can't break messaging.commandhandling.
- Position
- Below the diagonal: messaging.core.interception uses a module listed above it, which is the healthy direction.
21→11 messaging.core.interception uses messaging.eventhandling✕
- Connections
- 4 pairs of types, where a type in messaging.core.interception uses a type in messaging.eventhandling.
- The types involved
org.axonframework.messaging.core.interception.DefaultDispatchInterceptorRegistry→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.messaging.core.interception.DefaultHandlerInterceptorRegistry→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.messaging.core.interception.DispatchInterceptorRegistry→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.messaging.core.interception.HandlerInterceptorRegistry→org.axonframework.messaging.eventhandling.EventMessage
- Direction
- messaging.core.interception uses messaging.eventhandling, so a change to messaging.eventhandling can break messaging.core.interception, while a change to messaging.core.interception can't break messaging.eventhandling.
- Position
- Below the diagonal: messaging.core.interception uses a module listed above it, which is the healthy direction.
21→15 messaging.core.interception uses messaging.core✕
- Connections
- 29 pairs of types, where a type in messaging.core.interception uses a type in messaging.core. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
org.axonframework.messaging.core.interception.BeanValidationInterceptor→org.axonframework.messaging.core.Messageorg.axonframework.messaging.core.interception.BeanValidationInterceptor→org.axonframework.messaging.core.MessageDispatchInterceptororg.axonframework.messaging.core.interception.BeanValidationInterceptor→org.axonframework.messaging.core.MessageDispatchInterceptorChainorg.axonframework.messaging.core.interception.BeanValidationInterceptor→org.axonframework.messaging.core.MessageHandlerInterceptororg.axonframework.messaging.core.interception.BeanValidationInterceptor→org.axonframework.messaging.core.MessageHandlerInterceptorChainorg.axonframework.messaging.core.interception.BeanValidationInterceptor→org.axonframework.messaging.core.MessageStreamorg.axonframework.messaging.core.interception.CorrelationDataInterceptor→org.axonframework.messaging.core.MessageDispatchInterceptororg.axonframework.messaging.core.interception.CorrelationDataInterceptor→org.axonframework.messaging.core.MessageDispatchInterceptorChainorg.axonframework.messaging.core.interception.CorrelationDataInterceptor→org.axonframework.messaging.core.MessageHandlerInterceptororg.axonframework.messaging.core.interception.CorrelationDataInterceptor→org.axonframework.messaging.core.MessageHandlerInterceptorChainorg.axonframework.messaging.core.interception.CorrelationDataInterceptor→org.axonframework.messaging.core.MessageStreamorg.axonframework.messaging.core.interception.CorrelationDataInterceptor→org.axonframework.messaging.core.ResourceKeyorg.axonframework.messaging.core.interception.DefaultDispatchInterceptorRegistry→org.axonframework.messaging.core.Messageorg.axonframework.messaging.core.interception.DefaultDispatchInterceptorRegistry→org.axonframework.messaging.core.MessageDispatchInterceptororg.axonframework.messaging.core.interception.DefaultHandlerInterceptorRegistry→org.axonframework.messaging.core.Messageorg.axonframework.messaging.core.interception.DefaultHandlerInterceptorRegistry→org.axonframework.messaging.core.MessageHandlerInterceptororg.axonframework.messaging.core.interception.DispatchInterceptorFactory→org.axonframework.messaging.core.MessageDispatchInterceptororg.axonframework.messaging.core.interception.DispatchInterceptorRegistry→org.axonframework.messaging.core.Messageorg.axonframework.messaging.core.interception.DispatchInterceptorRegistry→org.axonframework.messaging.core.MessageDispatchInterceptororg.axonframework.messaging.core.interception.GenericInterceptorDefinition→org.axonframework.messaging.core.Messageorg.axonframework.messaging.core.interception.GenericInterceptorDefinition→org.axonframework.messaging.core.MessageDispatchInterceptororg.axonframework.messaging.core.interception.HandlerInterceptorFactory→org.axonframework.messaging.core.MessageHandlerInterceptororg.axonframework.messaging.core.interception.HandlerInterceptorRegistry→org.axonframework.messaging.core.Messageorg.axonframework.messaging.core.interception.HandlerInterceptorRegistry→org.axonframework.messaging.core.MessageHandlerInterceptororg.axonframework.messaging.core.interception.LoggingInterceptor→org.axonframework.messaging.core.MessageDispatchInterceptor
- Direction
- messaging.core.interception uses messaging.core, so a change to messaging.core can break messaging.core.interception, while a change to messaging.core.interception can't break messaging.core.
- Position
- Below the diagonal: messaging.core.interception uses a module listed above it, which is the healthy direction.
21→18 messaging.core.interception uses messaging.queryhandling✕
- Connections
- 6 pairs of types, where a type in messaging.core.interception uses a type in messaging.queryhandling.
- The types involved
org.axonframework.messaging.core.interception.DefaultDispatchInterceptorRegistry→org.axonframework.messaging.queryhandling.QueryMessageorg.axonframework.messaging.core.interception.DefaultDispatchInterceptorRegistry→org.axonframework.messaging.queryhandling.SubscriptionQueryUpdateMessageorg.axonframework.messaging.core.interception.DefaultHandlerInterceptorRegistry→org.axonframework.messaging.queryhandling.QueryMessageorg.axonframework.messaging.core.interception.DispatchInterceptorRegistry→org.axonframework.messaging.queryhandling.QueryMessageorg.axonframework.messaging.core.interception.DispatchInterceptorRegistry→org.axonframework.messaging.queryhandling.SubscriptionQueryUpdateMessageorg.axonframework.messaging.core.interception.HandlerInterceptorRegistry→org.axonframework.messaging.queryhandling.QueryMessage
- Direction
- messaging.core.interception uses messaging.queryhandling, so a change to messaging.queryhandling can break messaging.core.interception, while a change to messaging.core.interception can't break messaging.queryhandling.
- Position
- Below the diagonal: messaging.core.interception uses a module listed above it, which is the healthy direction.
22→3 messaging.eventhandling.processing.streaming.segmenting uses common.infra✕
- Connections
- 1 pair of types, where a type in messaging.eventhandling.processing.streaming.segmenting uses a type in common.infra.
- The types involved
org.axonframework.messaging.eventhandling.processing.streaming.segmenting.SequenceOverridingEventHandlingComponent→org.axonframework.common.infra.ComponentDescriptor
- Direction
- messaging.eventhandling.processing.streaming.segmenting uses common.infra, so a change to common.infra can break messaging.eventhandling.processing.streaming.segmenting, while a change to messaging.eventhandling.processing.streaming.segmenting can't break common.infra.
- Position
- Below the diagonal: messaging.eventhandling.processing.streaming.segmenting uses a module listed above it, which is the healthy direction.
22→7 messaging.eventhandling.processing.streaming.segmenting uses messaging.core.unitofwork✕
- Connections
- 3 pairs of types, where a type in messaging.eventhandling.processing.streaming.segmenting uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.messaging.eventhandling.processing.streaming.segmenting.SequenceCachingEventHandlingComponent→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventhandling.processing.streaming.segmenting.SequenceOverridingEventHandlingComponent→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventhandling.processing.streaming.segmenting.SequencingEventHandlingComponent→org.axonframework.messaging.core.unitofwork.ProcessingContext
- Direction
- messaging.eventhandling.processing.streaming.segmenting uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break messaging.eventhandling.processing.streaming.segmenting, while a change to messaging.eventhandling.processing.streaming.segmenting can't break messaging.core.unitofwork.
- Position
- Below the diagonal: messaging.eventhandling.processing.streaming.segmenting uses a module listed above it, which is the healthy direction.
22→10 messaging.eventhandling.processing.streaming.segmenting uses messaging.eventhandling.replay✕
- Connections
- 2 pairs of types, where a type in messaging.eventhandling.processing.streaming.segmenting uses a type in messaging.eventhandling.replay.
- The types involved
org.axonframework.messaging.eventhandling.processing.streaming.segmenting.SequenceOverridingEventHandlingComponent→org.axonframework.messaging.eventhandling.replay.ReplayStatusChangedorg.axonframework.messaging.eventhandling.processing.streaming.segmenting.SequenceOverridingEventHandlingComponent→org.axonframework.messaging.eventhandling.replay.ResetContext
- Direction
- messaging.eventhandling.processing.streaming.segmenting uses messaging.eventhandling.replay, so a change to messaging.eventhandling.replay can break messaging.eventhandling.processing.streaming.segmenting, while a change to messaging.eventhandling.processing.streaming.segmenting can't break messaging.eventhandling.replay.
- Position
- Below the diagonal: messaging.eventhandling.processing.streaming.segmenting uses a module listed above it, which is the healthy direction.
22→11 messaging.eventhandling.processing.streaming.segmenting uses messaging.eventhandling✕
- Connections
- 8 pairs of types, where a type in messaging.eventhandling.processing.streaming.segmenting uses a type in messaging.eventhandling.
- The types involved
org.axonframework.messaging.eventhandling.processing.streaming.segmenting.SequenceCachingEventHandlingComponent→org.axonframework.messaging.eventhandling.DelegatingEventHandlingComponentorg.axonframework.messaging.eventhandling.processing.streaming.segmenting.SequenceCachingEventHandlingComponent→org.axonframework.messaging.eventhandling.EventHandlingComponentorg.axonframework.messaging.eventhandling.processing.streaming.segmenting.SequenceCachingEventHandlingComponent→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.messaging.eventhandling.processing.streaming.segmenting.SequenceOverridingEventHandlingComponent→org.axonframework.messaging.eventhandling.EventHandlingComponentorg.axonframework.messaging.eventhandling.processing.streaming.segmenting.SequenceOverridingEventHandlingComponent→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.messaging.eventhandling.processing.streaming.segmenting.SequencingEventHandlingComponent→org.axonframework.messaging.eventhandling.DelegatingEventHandlingComponentorg.axonframework.messaging.eventhandling.processing.streaming.segmenting.SequencingEventHandlingComponent→org.axonframework.messaging.eventhandling.EventHandlingComponentorg.axonframework.messaging.eventhandling.processing.streaming.segmenting.SequencingEventHandlingComponent→org.axonframework.messaging.eventhandling.EventMessage
- Direction
- messaging.eventhandling.processing.streaming.segmenting uses messaging.eventhandling, so a change to messaging.eventhandling can break messaging.eventhandling.processing.streaming.segmenting, while a change to messaging.eventhandling.processing.streaming.segmenting can't break messaging.eventhandling.
- Position
- Below the diagonal: messaging.eventhandling.processing.streaming.segmenting uses a module listed above it, which is the healthy direction.
22→13 messaging.eventhandling.processing.streaming.segmenting uses messaging.core.sequencing✕
- Connections
- 1 pair of types, where a type in messaging.eventhandling.processing.streaming.segmenting uses a type in messaging.core.sequencing.
- The types involved
org.axonframework.messaging.eventhandling.processing.streaming.segmenting.SequenceOverridingEventHandlingComponent→org.axonframework.messaging.core.sequencing.SequencingPolicy
- Direction
- messaging.eventhandling.processing.streaming.segmenting uses messaging.core.sequencing, so a change to messaging.core.sequencing can break messaging.eventhandling.processing.streaming.segmenting, while a change to messaging.eventhandling.processing.streaming.segmenting can't break messaging.core.sequencing.
- Position
- Below the diagonal: messaging.eventhandling.processing.streaming.segmenting uses a module listed above it, which is the healthy direction.
22→15 messaging.eventhandling.processing.streaming.segmenting uses messaging.core✕
- Connections
- 9 pairs of types, where a type in messaging.eventhandling.processing.streaming.segmenting uses a type in messaging.core.
- The types involved
org.axonframework.messaging.eventhandling.processing.streaming.segmenting.Segment→org.axonframework.messaging.core.Contextorg.axonframework.messaging.eventhandling.processing.streaming.segmenting.Segment→org.axonframework.messaging.core.ResourceKeyorg.axonframework.messaging.eventhandling.processing.streaming.segmenting.SequenceCachingEventHandlingComponent→org.axonframework.messaging.core.ResourceKeyorg.axonframework.messaging.eventhandling.processing.streaming.segmenting.SequenceOverridingEventHandlingComponent→org.axonframework.messaging.core.Emptyorg.axonframework.messaging.eventhandling.processing.streaming.segmenting.SequenceOverridingEventHandlingComponent→org.axonframework.messaging.core.Messageorg.axonframework.messaging.eventhandling.processing.streaming.segmenting.SequenceOverridingEventHandlingComponent→org.axonframework.messaging.core.QualifiedNameorg.axonframework.messaging.eventhandling.processing.streaming.segmenting.SequencingEventHandlingComponent→org.axonframework.messaging.core.Emptyorg.axonframework.messaging.eventhandling.processing.streaming.segmenting.SequencingEventHandlingComponent→org.axonframework.messaging.core.Messageorg.axonframework.messaging.eventhandling.processing.streaming.segmenting.SequencingEventHandlingComponent→org.axonframework.messaging.core.ResourceKey
- Direction
- messaging.eventhandling.processing.streaming.segmenting uses messaging.core, so a change to messaging.core can break messaging.eventhandling.processing.streaming.segmenting, while a change to messaging.eventhandling.processing.streaming.segmenting can't break messaging.core.
- Position
- Below the diagonal: messaging.eventhandling.processing.streaming.segmenting uses a module listed above it, which is the healthy direction.
22→17 messaging.eventhandling.processing.streaming.segmenting uses messaging.eventhandling.processing.streaming.token✕
- Connections
- 5 pairs of types, where a type in messaging.eventhandling.processing.streaming.segmenting uses a type in messaging.eventhandling.processing.streaming.token.
- The types involved
org.axonframework.messaging.eventhandling.processing.streaming.segmenting.EventTrackerStatus→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingTokenorg.axonframework.messaging.eventhandling.processing.streaming.segmenting.SegmentChangeListener→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingTokenorg.axonframework.messaging.eventhandling.processing.streaming.segmenting.SimpleSegmentChangeListener→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingTokenorg.axonframework.messaging.eventhandling.processing.streaming.segmenting.TrackerStatus→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingTokenorg.axonframework.messaging.eventhandling.processing.streaming.segmenting.WrappedTrackerStatus→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingToken
- Direction
- messaging.eventhandling.processing.streaming.segmenting uses messaging.eventhandling.processing.streaming.token, so a change to messaging.eventhandling.processing.streaming.token can break messaging.eventhandling.processing.streaming.segmenting, while a change to messaging.eventhandling.processing.streaming.segmenting can't break messaging.eventhandling.processing.streaming.token.
- Position
- Below the diagonal: messaging.eventhandling.processing.streaming.segmenting uses a module listed above it, which is the healthy direction.
23→7 messaging.eventstreaming uses messaging.core.unitofwork✕
- Connections
- 2 pairs of types, where a type in messaging.eventstreaming uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.messaging.eventstreaming.StreamableEventSource→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventstreaming.TrackingTokenSource→org.axonframework.messaging.core.unitofwork.ProcessingContext
- Direction
- messaging.eventstreaming uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break messaging.eventstreaming, while a change to messaging.eventstreaming can't break messaging.core.unitofwork.
- Position
- Below the diagonal: messaging.eventstreaming uses a module listed above it, which is the healthy direction.
23→11 messaging.eventstreaming uses messaging.eventhandling✕
- Connections
- 1 pair of types, where a type in messaging.eventstreaming uses a type in messaging.eventhandling.
- The types involved
org.axonframework.messaging.eventstreaming.StreamableEventSource→org.axonframework.messaging.eventhandling.EventMessage
- Direction
- messaging.eventstreaming uses messaging.eventhandling, so a change to messaging.eventhandling can break messaging.eventstreaming, while a change to messaging.eventstreaming can't break messaging.eventhandling.
- Position
- Below the diagonal: messaging.eventstreaming uses a module listed above it, which is the healthy direction.
23→15 messaging.eventstreaming uses messaging.core✕
- Connections
- 13 pairs of types, where a type in messaging.eventstreaming uses a type in messaging.core.
- The types involved
org.axonframework.messaging.eventstreaming.AnyEvent→org.axonframework.messaging.core.QualifiedNameorg.axonframework.messaging.eventstreaming.EventCriteria→org.axonframework.messaging.core.QualifiedNameorg.axonframework.messaging.eventstreaming.EventCriterion→org.axonframework.messaging.core.QualifiedNameorg.axonframework.messaging.eventstreaming.EventTypeRestrictableEventCriteria→org.axonframework.messaging.core.MessageTypeResolverorg.axonframework.messaging.eventstreaming.EventTypeRestrictableEventCriteria→org.axonframework.messaging.core.QualifiedNameorg.axonframework.messaging.eventstreaming.EventTypeRestrictableOrEventCriteria→org.axonframework.messaging.core.QualifiedNameorg.axonframework.messaging.eventstreaming.EventsCondition→org.axonframework.messaging.core.QualifiedNameorg.axonframework.messaging.eventstreaming.OrEventCriteria→org.axonframework.messaging.core.QualifiedNameorg.axonframework.messaging.eventstreaming.StreamableEventSource→org.axonframework.messaging.core.MessageStreamorg.axonframework.messaging.eventstreaming.Tag→org.axonframework.messaging.core.Contextorg.axonframework.messaging.eventstreaming.Tag→org.axonframework.messaging.core.ResourceKeyorg.axonframework.messaging.eventstreaming.TagAndTypeFilteredEventCriteria→org.axonframework.messaging.core.QualifiedNameorg.axonframework.messaging.eventstreaming.TagFilteredEventCriteria→org.axonframework.messaging.core.QualifiedName
- Direction
- messaging.eventstreaming uses messaging.core, so a change to messaging.core can break messaging.eventstreaming, while a change to messaging.eventstreaming can't break messaging.core.
- Position
- Below the diagonal: messaging.eventstreaming uses a module listed above it, which is the healthy direction.
23→17 messaging.eventstreaming uses messaging.eventhandling.processing.streaming.token✕
- Connections
- 4 pairs of types, where a type in messaging.eventstreaming uses a type in messaging.eventhandling.processing.streaming.token.
- The types involved
org.axonframework.messaging.eventstreaming.DefaultStreamingCondition→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingTokenorg.axonframework.messaging.eventstreaming.StartingFrom→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingTokenorg.axonframework.messaging.eventstreaming.StreamingCondition→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingTokenorg.axonframework.messaging.eventstreaming.TrackingTokenSource→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingToken
- Direction
- messaging.eventstreaming uses messaging.eventhandling.processing.streaming.token, so a change to messaging.eventhandling.processing.streaming.token can break messaging.eventstreaming, while a change to messaging.eventstreaming can't break messaging.eventhandling.processing.streaming.token.
- Position
- Below the diagonal: messaging.eventstreaming uses a module listed above it, which is the healthy direction.
24→1 modelling uses common✕
- Connections
- 1 pair of types, where a type in modelling uses a type in common.
- The types involved
org.axonframework.modelling.ConcurrencyException→org.axonframework.common.AxonTransientException
- Direction
- modelling uses common, so a change to common can break modelling, while a change to modelling can't break common.
- Position
- Below the diagonal: modelling uses a module listed above it, which is the healthy direction.
24→3 modelling uses common.infra✕
- Connections
- 9 pairs of types, where a type in modelling uses a type in common.infra.
- The types involved
org.axonframework.modelling.FallbackEntityIdResolver→org.axonframework.common.infra.ComponentDescriptororg.axonframework.modelling.FallbackEntityIdResolver→org.axonframework.common.infra.DescribableComponentorg.axonframework.modelling.HierarchicalStateManager→org.axonframework.common.infra.ComponentDescriptororg.axonframework.modelling.MetadataEntityIdResolver→org.axonframework.common.infra.ComponentDescriptororg.axonframework.modelling.MetadataEntityIdResolver→org.axonframework.common.infra.DescribableComponentorg.axonframework.modelling.SimpleEntityEvolvingComponent→org.axonframework.common.infra.ComponentDescriptororg.axonframework.modelling.SimpleEntityEvolvingComponent→org.axonframework.common.infra.DescribableComponentorg.axonframework.modelling.SimpleStateManager→org.axonframework.common.infra.ComponentDescriptororg.axonframework.modelling.StateManager→org.axonframework.common.infra.DescribableComponent
- Direction
- modelling uses common.infra, so a change to common.infra can break modelling, while a change to modelling can't break common.infra.
- Position
- Below the diagonal: modelling uses a module listed above it, which is the healthy direction.
24→5 modelling uses common.configuration✕
- Connections
- 2 pairs of types, where a type in modelling uses a type in common.configuration.
- The types involved
org.axonframework.modelling.HierarchicalStateManagerConfigurationEnhancer→org.axonframework.common.configuration.ComponentRegistryorg.axonframework.modelling.HierarchicalStateManagerConfigurationEnhancer→org.axonframework.common.configuration.ConfigurationEnhancer
- Direction
- modelling uses common.configuration, so a change to common.configuration can break modelling, while a change to modelling can't break common.configuration.
- Position
- Below the diagonal: modelling uses a module listed above it, which is the healthy direction.
24→6 modelling uses conversion✕
- Connections
- 1 pair of types, where a type in modelling uses a type in conversion.
- The types involved
org.axonframework.modelling.MetadataEntityIdResolver→org.axonframework.conversion.Converter
- Direction
- modelling uses conversion, so a change to conversion can break modelling, while a change to modelling can't break conversion.
- Position
- Below the diagonal: modelling uses a module listed above it, which is the healthy direction.
24→7 modelling uses messaging.core.unitofwork✕
- Connections
- 10 pairs of types, where a type in modelling uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.modelling.EntityEvolver→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.modelling.EntityIdResolver→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.modelling.FallbackEntityIdResolver→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.modelling.HierarchicalStateManager→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.modelling.MetadataEntityIdResolver→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.modelling.PayloadBasedEntityEvolver→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.modelling.PropertyBasedEntityIdResolver→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.modelling.SimpleEntityEvolvingComponent→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.modelling.SimpleStateManager→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.modelling.StateManager→org.axonframework.messaging.core.unitofwork.ProcessingContext
- Direction
- modelling uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break modelling, while a change to modelling can't break messaging.core.unitofwork.
- Position
- Below the diagonal: modelling uses a module listed above it, which is the healthy direction.
24→11 modelling uses messaging.eventhandling✕
- Connections
- 3 pairs of types, where a type in modelling uses a type in messaging.eventhandling.
- The types involved
org.axonframework.modelling.EntityEvolver→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.modelling.PayloadBasedEntityEvolver→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.modelling.SimpleEntityEvolvingComponent→org.axonframework.messaging.eventhandling.EventMessage
- Direction
- modelling uses messaging.eventhandling, so a change to messaging.eventhandling can break modelling, while a change to modelling can't break messaging.eventhandling.
- Position
- Below the diagonal: modelling uses a module listed above it, which is the healthy direction.
24→15 modelling uses messaging.core✕
- Connections
- 6 pairs of types, where a type in modelling uses a type in messaging.core.
- The types involved
org.axonframework.modelling.EntityEvolvingComponent→org.axonframework.messaging.core.QualifiedNameorg.axonframework.modelling.EntityIdResolver→org.axonframework.messaging.core.Messageorg.axonframework.modelling.FallbackEntityIdResolver→org.axonframework.messaging.core.Messageorg.axonframework.modelling.MetadataEntityIdResolver→org.axonframework.messaging.core.Messageorg.axonframework.modelling.PropertyBasedEntityIdResolver→org.axonframework.messaging.core.Messageorg.axonframework.modelling.SimpleEntityEvolvingComponent→org.axonframework.messaging.core.QualifiedName
- Direction
- modelling uses messaging.core, so a change to messaging.core can break modelling, while a change to modelling can't break messaging.core.
- Position
- Below the diagonal: modelling uses a module listed above it, which is the healthy direction.
24→20 modelling uses modelling.repository✕
- Connections
- 9 pairs of types, where a type in modelling uses a type in modelling.repository.
- The types involved
org.axonframework.modelling.HierarchicalStateManager→org.axonframework.modelling.repository.ManagedEntityorg.axonframework.modelling.HierarchicalStateManager→org.axonframework.modelling.repository.Repositoryorg.axonframework.modelling.RepositoryAlreadyRegisteredException→org.axonframework.modelling.repository.Repositoryorg.axonframework.modelling.SimpleStateManager→org.axonframework.modelling.repository.ManagedEntityorg.axonframework.modelling.SimpleStateManager→org.axonframework.modelling.repository.Repositoryorg.axonframework.modelling.StateManager→org.axonframework.modelling.repository.ManagedEntityorg.axonframework.modelling.StateManager→org.axonframework.modelling.repository.Repositoryorg.axonframework.modelling.StateManager→org.axonframework.modelling.repository.SimpleRepositoryEntityLoaderorg.axonframework.modelling.StateManager→org.axonframework.modelling.repository.SimpleRepositoryEntityPersister
- Direction
- modelling uses modelling.repository, so a change to modelling.repository can break modelling, while a change to modelling can't break modelling.repository.
- Position
- Below the diagonal: modelling uses a module listed above it, which is the healthy direction.
25→1 eventsourcing.eventstore uses common✕
- Connections
- 5 pairs of types, where a type in eventsourcing.eventstore uses a type in common.
- The types involved
org.axonframework.eventsourcing.eventstore.AppendEventsTransactionRejectedException→org.axonframework.common.AxonNonTransientExceptionorg.axonframework.eventsourcing.eventstore.ContinuousMessageStream→org.axonframework.common.Registrationorg.axonframework.eventsourcing.eventstore.EventStoreException→org.axonframework.common.AxonNonTransientExceptionorg.axonframework.eventsourcing.eventstore.InterceptingEventStore→org.axonframework.common.Registrationorg.axonframework.eventsourcing.eventstore.StorageEngineBackedEventStore→org.axonframework.common.Registration
- Direction
- eventsourcing.eventstore uses common, so a change to common can break eventsourcing.eventstore, while a change to eventsourcing.eventstore can't break common.
- Position
- Below the diagonal: eventsourcing.eventstore uses a module listed above it, which is the healthy direction.
25→3 eventsourcing.eventstore uses common.infra✕
- Connections
- 5 pairs of types, where a type in eventsourcing.eventstore uses a type in common.infra.
- The types involved
org.axonframework.eventsourcing.eventstore.ConflictDiagnosingEventStorageEngine→org.axonframework.common.infra.ComponentDescriptororg.axonframework.eventsourcing.eventstore.EventStorageEngine→org.axonframework.common.infra.DescribableComponentorg.axonframework.eventsourcing.eventstore.InterceptingEventStore→org.axonframework.common.infra.ComponentDescriptororg.axonframework.eventsourcing.eventstore.SnapshotCapableEventStorageEngine→org.axonframework.common.infra.ComponentDescriptororg.axonframework.eventsourcing.eventstore.StorageEngineBackedEventStore→org.axonframework.common.infra.ComponentDescriptor
- Direction
- eventsourcing.eventstore uses common.infra, so a change to common.infra can break eventsourcing.eventstore, while a change to eventsourcing.eventstore can't break common.infra.
- Position
- Below the diagonal: eventsourcing.eventstore uses a module listed above it, which is the healthy direction.
25→7 eventsourcing.eventstore uses messaging.core.unitofwork✕
- Connections
- 12 pairs of types, where a type in eventsourcing.eventstore uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.eventsourcing.eventstore.ConflictDiagnosingEventStorageEngine→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.eventsourcing.eventstore.DefaultEventStoreTransaction→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.eventsourcing.eventstore.DiagnosingAppendTransaction→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.eventsourcing.eventstore.EventStorageEngine→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.eventsourcing.eventstore.EventStore→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.eventsourcing.eventstore.EventStoreTransaction→org.axonframework.messaging.core.unitofwork.Phaseorg.axonframework.eventsourcing.eventstore.InterceptingAppender→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.eventsourcing.eventstore.InterceptingEventStore→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.eventsourcing.eventstore.InterceptingEventStoreTransaction→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.eventsourcing.eventstore.SnapshotCapableEventStorageEngine→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.eventsourcing.eventstore.StorageEngineBackedEventStore→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.eventsourcing.eventstore.TagResolver→org.axonframework.messaging.core.unitofwork.ProcessingContext
- Direction
- eventsourcing.eventstore uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break eventsourcing.eventstore, while a change to eventsourcing.eventstore can't break messaging.core.unitofwork.
- Position
- Below the diagonal: eventsourcing.eventstore uses a module listed above it, which is the healthy direction.
25→11 eventsourcing.eventstore uses messaging.eventhandling✕
- Connections
- 22 pairs of types, where a type in eventsourcing.eventstore uses a type in messaging.eventhandling.
- The types involved
org.axonframework.eventsourcing.eventstore.AnnotationBasedTagResolver→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.eventsourcing.eventstore.AppendEventsTransactionRejectedException→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.eventsourcing.eventstore.ConflictDiagnosingEventStorageEngine→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.eventsourcing.eventstore.ContinuousMessageStream→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.eventsourcing.eventstore.DefaultEventStoreTransaction→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.eventsourcing.eventstore.EventStorageEngine→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.eventsourcing.eventstore.EventStore→org.axonframework.messaging.eventhandling.EventBusorg.axonframework.eventsourcing.eventstore.EventStoreTransaction→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.eventsourcing.eventstore.InterceptingAppender→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.eventsourcing.eventstore.InterceptingEventStore→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.eventsourcing.eventstore.InterceptingEventStore→org.axonframework.messaging.eventhandling.InterceptingEventBusorg.axonframework.eventsourcing.eventstore.InterceptingEventStoreTransaction→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.eventsourcing.eventstore.MetadataBasedTagResolver→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.eventsourcing.eventstore.MultiTagResolver→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.eventsourcing.eventstore.PayloadBasedTagResolver→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.eventsourcing.eventstore.SnapshotCapableEventStorageEngine→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.eventsourcing.eventstore.SnapshotEventMessage→org.axonframework.messaging.eventhandling.GenericEventMessageorg.axonframework.eventsourcing.eventstore.StorageEngineBackedEventStore→org.axonframework.messaging.eventhandling.EventBusorg.axonframework.eventsourcing.eventstore.StorageEngineBackedEventStore→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.eventsourcing.eventstore.TagResolver→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.eventsourcing.eventstore.TerminalEventMessage→org.axonframework.messaging.eventhandling.GenericEventMessageorg.axonframework.eventsourcing.eventstore.TooManyTagsOnEventMessageException→org.axonframework.messaging.eventhandling.EventMessage
- Direction
- eventsourcing.eventstore uses messaging.eventhandling, so a change to messaging.eventhandling can break eventsourcing.eventstore, while a change to eventsourcing.eventstore can't break messaging.eventhandling.
- Position
- Below the diagonal: eventsourcing.eventstore uses a module listed above it, which is the healthy direction.
25→15 eventsourcing.eventstore uses messaging.core✕
- Connections
- 22 pairs of types, where a type in eventsourcing.eventstore uses a type in messaging.core.
- The types involved
org.axonframework.eventsourcing.eventstore.ConflictDiagnosingEventStorageEngine→org.axonframework.messaging.core.MessageStreamorg.axonframework.eventsourcing.eventstore.ConsistencyMarker→org.axonframework.messaging.core.Contextorg.axonframework.eventsourcing.eventstore.ConsistencyMarker→org.axonframework.messaging.core.ResourceKeyorg.axonframework.eventsourcing.eventstore.ContinuousMessageStream→org.axonframework.messaging.core.AbstractMessageStreamorg.axonframework.eventsourcing.eventstore.ContinuousMessageStream→org.axonframework.messaging.core.Entryorg.axonframework.eventsourcing.eventstore.ContinuousMessageStream→org.axonframework.messaging.core.FetchResultorg.axonframework.eventsourcing.eventstore.DefaultEventStoreTransaction→org.axonframework.messaging.core.MessageStreamorg.axonframework.eventsourcing.eventstore.DefaultEventStoreTransaction→org.axonframework.messaging.core.ResourceKeyorg.axonframework.eventsourcing.eventstore.EventStorageEngine→org.axonframework.messaging.core.MessageStreamorg.axonframework.eventsourcing.eventstore.EventStoreTransaction→org.axonframework.messaging.core.MessageStreamorg.axonframework.eventsourcing.eventstore.EventTypeResolver→org.axonframework.messaging.core.MessageTypeorg.axonframework.eventsourcing.eventstore.InterceptingAppender→org.axonframework.messaging.core.DefaultMessageDispatchInterceptorChainorg.axonframework.eventsourcing.eventstore.InterceptingAppender→org.axonframework.messaging.core.MessageDispatchInterceptororg.axonframework.eventsourcing.eventstore.InterceptingEventStore→org.axonframework.messaging.core.MessageDispatchInterceptororg.axonframework.eventsourcing.eventstore.InterceptingEventStore→org.axonframework.messaging.core.MessageStreamorg.axonframework.eventsourcing.eventstore.InterceptingEventStore→org.axonframework.messaging.core.ResourceKeyorg.axonframework.eventsourcing.eventstore.InterceptingEventStoreTransaction→org.axonframework.messaging.core.MessageStreamorg.axonframework.eventsourcing.eventstore.Snapshot→org.axonframework.messaging.core.QualifiedNameorg.axonframework.eventsourcing.eventstore.SnapshotCapableEventStorageEngine→org.axonframework.messaging.core.MessageStreamorg.axonframework.eventsourcing.eventstore.StorageEngineBackedEventStore→org.axonframework.messaging.core.MessageStreamorg.axonframework.eventsourcing.eventstore.StorageEngineBackedEventStore→org.axonframework.messaging.core.ResourceKeyorg.axonframework.eventsourcing.eventstore.TagResolver→org.axonframework.messaging.core.ResourceKey
- Direction
- eventsourcing.eventstore uses messaging.core, so a change to messaging.core can break eventsourcing.eventstore, while a change to eventsourcing.eventstore can't break messaging.core.
- Position
- Below the diagonal: eventsourcing.eventstore uses a module listed above it, which is the healthy direction.
25→17 eventsourcing.eventstore uses messaging.eventhandling.processing.streaming.token✕
- Connections
- 5 pairs of types, where a type in eventsourcing.eventstore uses a type in messaging.eventhandling.processing.streaming.token.
- The types involved
org.axonframework.eventsourcing.eventstore.ConflictDiagnosingEventStorageEngine→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingTokenorg.axonframework.eventsourcing.eventstore.EventStorageEngine→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingTokenorg.axonframework.eventsourcing.eventstore.InterceptingEventStore→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingTokenorg.axonframework.eventsourcing.eventstore.SnapshotCapableEventStorageEngine→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingTokenorg.axonframework.eventsourcing.eventstore.StorageEngineBackedEventStore→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingToken
- Direction
- eventsourcing.eventstore uses messaging.eventhandling.processing.streaming.token, so a change to messaging.eventhandling.processing.streaming.token can break eventsourcing.eventstore, while a change to eventsourcing.eventstore can't break messaging.eventhandling.processing.streaming.token.
- Position
- Below the diagonal: eventsourcing.eventstore uses a module listed above it, which is the healthy direction.
25→23 eventsourcing.eventstore uses messaging.eventstreaming✕
- Connections
- 24 pairs of types, where a type in eventsourcing.eventstore uses a type in messaging.eventstreaming.
- The types involved
org.axonframework.eventsourcing.eventstore.AggregateBasedEventStorageEngineUtils→org.axonframework.messaging.eventstreaming.Tagorg.axonframework.eventsourcing.eventstore.AnnotationBasedTagResolver→org.axonframework.messaging.eventstreaming.Tagorg.axonframework.eventsourcing.eventstore.AppendCondition→org.axonframework.messaging.eventstreaming.EventCriteriaorg.axonframework.eventsourcing.eventstore.AppendCondition→org.axonframework.messaging.eventstreaming.EventsConditionorg.axonframework.eventsourcing.eventstore.AppendEventsTransactionRejectedException→org.axonframework.messaging.eventstreaming.Tagorg.axonframework.eventsourcing.eventstore.ConflictDiagnosingEventStorageEngine→org.axonframework.messaging.eventstreaming.StreamingConditionorg.axonframework.eventsourcing.eventstore.DefaultAppendCondition→org.axonframework.messaging.eventstreaming.EventCriteriaorg.axonframework.eventsourcing.eventstore.DefaultSourcingCondition→org.axonframework.messaging.eventstreaming.EventCriteriaorg.axonframework.eventsourcing.eventstore.EventStorageEngine→org.axonframework.messaging.eventstreaming.StreamingConditionorg.axonframework.eventsourcing.eventstore.EventStore→org.axonframework.messaging.eventstreaming.StreamableEventSourceorg.axonframework.eventsourcing.eventstore.GenericTaggedEventMessage→org.axonframework.messaging.eventstreaming.Tagorg.axonframework.eventsourcing.eventstore.InterceptingEventStore→org.axonframework.messaging.eventstreaming.StreamingConditionorg.axonframework.eventsourcing.eventstore.MetadataBasedTagResolver→org.axonframework.messaging.eventstreaming.Tagorg.axonframework.eventsourcing.eventstore.MultiTagResolver→org.axonframework.messaging.eventstreaming.Tagorg.axonframework.eventsourcing.eventstore.NoAppendCondition→org.axonframework.messaging.eventstreaming.EventCriteriaorg.axonframework.eventsourcing.eventstore.PayloadBasedTagResolver→org.axonframework.messaging.eventstreaming.Tagorg.axonframework.eventsourcing.eventstore.SnapshotCapableEventStorageEngine→org.axonframework.messaging.eventstreaming.EventCriteriaorg.axonframework.eventsourcing.eventstore.SnapshotCapableEventStorageEngine→org.axonframework.messaging.eventstreaming.StreamingConditionorg.axonframework.eventsourcing.eventstore.SourcingCondition→org.axonframework.messaging.eventstreaming.EventCriteriaorg.axonframework.eventsourcing.eventstore.SourcingCondition→org.axonframework.messaging.eventstreaming.EventsConditionorg.axonframework.eventsourcing.eventstore.StorageEngineBackedEventStore→org.axonframework.messaging.eventstreaming.StreamingConditionorg.axonframework.eventsourcing.eventstore.TagResolver→org.axonframework.messaging.eventstreaming.Tagorg.axonframework.eventsourcing.eventstore.TaggedEventMessage→org.axonframework.messaging.eventstreaming.Tagorg.axonframework.eventsourcing.eventstore.TooManyTagsOnEventMessageException→org.axonframework.messaging.eventstreaming.Tag
- Direction
- eventsourcing.eventstore uses messaging.eventstreaming, so a change to messaging.eventstreaming can break eventsourcing.eventstore, while a change to eventsourcing.eventstore can't break messaging.eventstreaming.
- Position
- Below the diagonal: eventsourcing.eventstore uses a module listed above it, which is the healthy direction.
26→1 messaging.eventhandling.processing uses common✕
- Connections
- 1 pair of types, where a type in messaging.eventhandling.processing uses a type in common.
- The types involved
org.axonframework.messaging.eventhandling.processing.EventProcessingException→org.axonframework.common.AxonException
- Direction
- messaging.eventhandling.processing uses common, so a change to common can break messaging.eventhandling.processing, while a change to messaging.eventhandling.processing can't break common.
- Position
- Below the diagonal: messaging.eventhandling.processing uses a module listed above it, which is the healthy direction.
26→3 messaging.eventhandling.processing uses common.infra✕
- Connections
- 3 pairs of types, where a type in messaging.eventhandling.processing uses a type in common.infra.
- The types involved
org.axonframework.messaging.eventhandling.processing.EventProcessor→org.axonframework.common.infra.DescribableComponentorg.axonframework.messaging.eventhandling.processing.ProcessorEventHandlingComponents→org.axonframework.common.infra.ComponentDescriptororg.axonframework.messaging.eventhandling.processing.ProcessorEventHandlingComponents→org.axonframework.common.infra.DescribableComponent
- Direction
- messaging.eventhandling.processing uses common.infra, so a change to common.infra can break messaging.eventhandling.processing, while a change to messaging.eventhandling.processing can't break common.infra.
- Position
- Below the diagonal: messaging.eventhandling.processing uses a module listed above it, which is the healthy direction.
26→7 messaging.eventhandling.processing uses messaging.core.unitofwork✕
- Connections
- 1 pair of types, where a type in messaging.eventhandling.processing uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.messaging.eventhandling.processing.ProcessorEventHandlingComponents→org.axonframework.messaging.core.unitofwork.ProcessingContext
- Direction
- messaging.eventhandling.processing uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break messaging.eventhandling.processing, while a change to messaging.eventhandling.processing can't break messaging.core.unitofwork.
- Position
- Below the diagonal: messaging.eventhandling.processing uses a module listed above it, which is the healthy direction.
26→10 messaging.eventhandling.processing uses messaging.eventhandling.replay✕
- Connections
- 1 pair of types, where a type in messaging.eventhandling.processing uses a type in messaging.eventhandling.replay.
- The types involved
org.axonframework.messaging.eventhandling.processing.ProcessorEventHandlingComponents→org.axonframework.messaging.eventhandling.replay.ResetContext
- Direction
- messaging.eventhandling.processing uses messaging.eventhandling.replay, so a change to messaging.eventhandling.replay can break messaging.eventhandling.processing, while a change to messaging.eventhandling.processing can't break messaging.eventhandling.replay.
- Position
- Below the diagonal: messaging.eventhandling.processing uses a module listed above it, which is the healthy direction.
26→11 messaging.eventhandling.processing uses messaging.eventhandling✕
- Connections
- 2 pairs of types, where a type in messaging.eventhandling.processing uses a type in messaging.eventhandling.
- The types involved
org.axonframework.messaging.eventhandling.processing.ProcessorEventHandlingComponents→org.axonframework.messaging.eventhandling.EventHandlingComponentorg.axonframework.messaging.eventhandling.processing.ProcessorEventHandlingComponents→org.axonframework.messaging.eventhandling.EventMessage
- Direction
- messaging.eventhandling.processing uses messaging.eventhandling, so a change to messaging.eventhandling can break messaging.eventhandling.processing, while a change to messaging.eventhandling.processing can't break messaging.eventhandling.
- Position
- Below the diagonal: messaging.eventhandling.processing uses a module listed above it, which is the healthy direction.
26→15 messaging.eventhandling.processing uses messaging.core✕
- Connections
- 4 pairs of types, where a type in messaging.eventhandling.processing uses a type in messaging.core.
- The types involved
org.axonframework.messaging.eventhandling.processing.ProcessorEventHandlingComponents→org.axonframework.messaging.core.Emptyorg.axonframework.messaging.eventhandling.processing.ProcessorEventHandlingComponents→org.axonframework.messaging.core.Entryorg.axonframework.messaging.eventhandling.processing.ProcessorEventHandlingComponents→org.axonframework.messaging.core.Messageorg.axonframework.messaging.eventhandling.processing.ProcessorEventHandlingComponents→org.axonframework.messaging.core.QualifiedName
- Direction
- messaging.eventhandling.processing uses messaging.core, so a change to messaging.core can break messaging.eventhandling.processing, while a change to messaging.eventhandling.processing can't break messaging.core.
- Position
- Below the diagonal: messaging.eventhandling.processing uses a module listed above it, which is the healthy direction.
26→22 messaging.eventhandling.processing uses messaging.eventhandling.processing.streaming.segmenting✕
- Connections
- 1 pair of types, where a type in messaging.eventhandling.processing uses a type in messaging.eventhandling.processing.streaming.segmenting.
- The types involved
org.axonframework.messaging.eventhandling.processing.ProcessorEventHandlingComponents→org.axonframework.messaging.eventhandling.processing.streaming.segmenting.Segment
- Direction
- messaging.eventhandling.processing uses messaging.eventhandling.processing.streaming.segmenting, so a change to messaging.eventhandling.processing.streaming.segmenting can break messaging.eventhandling.processing, while a change to messaging.eventhandling.processing can't break messaging.eventhandling.processing.streaming.segmenting.
- Position
- Below the diagonal: messaging.eventhandling.processing uses a module listed above it, which is the healthy direction.
27→1 messaging.eventhandling.processing.streaming.token.store uses common✕
- Connections
- 3 pairs of types, where a type in messaging.eventhandling.processing.streaming.token.store uses a type in common.
- The types involved
org.axonframework.messaging.eventhandling.processing.streaming.token.store.UnableToClaimTokenException→org.axonframework.common.AxonTransientExceptionorg.axonframework.messaging.eventhandling.processing.streaming.token.store.UnableToInitializeTokenException→org.axonframework.common.AxonTransientExceptionorg.axonframework.messaging.eventhandling.processing.streaming.token.store.UnableToRetrieveIdentifierException→org.axonframework.common.AxonTransientException
- Direction
- messaging.eventhandling.processing.streaming.token.store uses common, so a change to common can break messaging.eventhandling.processing.streaming.token.store, while a change to messaging.eventhandling.processing.streaming.token.store can't break common.
- Position
- Below the diagonal: messaging.eventhandling.processing.streaming.token.store uses a module listed above it, which is the healthy direction.
27→6 messaging.eventhandling.processing.streaming.token.store uses conversion✕
- Connections
- 1 pair of types, where a type in messaging.eventhandling.processing.streaming.token.store uses a type in conversion.
- The types involved
org.axonframework.messaging.eventhandling.processing.streaming.token.store.LegacyTokenTypes→org.axonframework.conversion.Converter
- Direction
- messaging.eventhandling.processing.streaming.token.store uses conversion, so a change to conversion can break messaging.eventhandling.processing.streaming.token.store, while a change to messaging.eventhandling.processing.streaming.token.store can't break conversion.
- Position
- Below the diagonal: messaging.eventhandling.processing.streaming.token.store uses a module listed above it, which is the healthy direction.
27→7 messaging.eventhandling.processing.streaming.token.store uses messaging.core.unitofwork✕
- Connections
- 1 pair of types, where a type in messaging.eventhandling.processing.streaming.token.store uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.messaging.eventhandling.processing.streaming.token.store.TokenStore→org.axonframework.messaging.core.unitofwork.ProcessingContext
- Direction
- messaging.eventhandling.processing.streaming.token.store uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break messaging.eventhandling.processing.streaming.token.store, while a change to messaging.eventhandling.processing.streaming.token.store can't break messaging.core.unitofwork.
- Position
- Below the diagonal: messaging.eventhandling.processing.streaming.token.store uses a module listed above it, which is the healthy direction.
27→17 messaging.eventhandling.processing.streaming.token.store uses messaging.eventhandling.processing.streaming.token✕
- Connections
- 4 pairs of types, where a type in messaging.eventhandling.processing.streaming.token.store uses a type in messaging.eventhandling.processing.streaming.token.
- The types involved
org.axonframework.messaging.eventhandling.processing.streaming.token.store.ConfigToken→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingTokenorg.axonframework.messaging.eventhandling.processing.streaming.token.store.LegacyTokenTypeMapper→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingTokenorg.axonframework.messaging.eventhandling.processing.streaming.token.store.LegacyTokenTypes→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingTokenorg.axonframework.messaging.eventhandling.processing.streaming.token.store.TokenStore→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingToken
- Direction
- messaging.eventhandling.processing.streaming.token.store uses messaging.eventhandling.processing.streaming.token, so a change to messaging.eventhandling.processing.streaming.token can break messaging.eventhandling.processing.streaming.token.store, while a change to messaging.eventhandling.processing.streaming.token.store can't break messaging.eventhandling.processing.streaming.token.
- Position
- Below the diagonal: messaging.eventhandling.processing.streaming.token.store uses a module listed above it, which is the healthy direction.
27→22 messaging.eventhandling.processing.streaming.token.store uses messaging.eventhandling.processing.streaming.segmenting✕
- Connections
- 1 pair of types, where a type in messaging.eventhandling.processing.streaming.token.store uses a type in messaging.eventhandling.processing.streaming.segmenting.
- The types involved
org.axonframework.messaging.eventhandling.processing.streaming.token.store.TokenStore→org.axonframework.messaging.eventhandling.processing.streaming.segmenting.Segment
- Direction
- messaging.eventhandling.processing.streaming.token.store uses messaging.eventhandling.processing.streaming.segmenting, so a change to messaging.eventhandling.processing.streaming.segmenting can break messaging.eventhandling.processing.streaming.token.store, while a change to messaging.eventhandling.processing.streaming.token.store can't break messaging.eventhandling.processing.streaming.segmenting.
- Position
- Below the diagonal: messaging.eventhandling.processing.streaming.token.store uses a module listed above it, which is the healthy direction.
28→3 modelling.entity uses common.infra✕
- Connections
- 7 pairs of types, where a type in modelling.entity uses a type in common.infra.
- The types involved
org.axonframework.modelling.entity.ConcreteEntityMetamodel→org.axonframework.common.infra.ComponentDescriptororg.axonframework.modelling.entity.ConcreteEntityMetamodel→org.axonframework.common.infra.DescribableComponentorg.axonframework.modelling.entity.EntityCommandHandlingComponent→org.axonframework.common.infra.ComponentDescriptororg.axonframework.modelling.entity.EntityCommandHandlingComponent→org.axonframework.common.infra.DescribableComponentorg.axonframework.modelling.entity.EntityMetamodel→org.axonframework.common.infra.DescribableComponentorg.axonframework.modelling.entity.PolymorphicEntityMetamodel→org.axonframework.common.infra.ComponentDescriptororg.axonframework.modelling.entity.PolymorphicEntityMetamodel→org.axonframework.common.infra.DescribableComponent
- Direction
- modelling.entity uses common.infra, so a change to common.infra can break modelling.entity, while a change to modelling.entity can't break common.infra.
- Position
- Below the diagonal: modelling.entity uses a module listed above it, which is the healthy direction.
28→7 modelling.entity uses messaging.core.unitofwork✕
- Connections
- 7 pairs of types, where a type in modelling.entity uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.modelling.entity.ConcreteEntityMetamodel→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.modelling.entity.EntityCommandHandler→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.modelling.entity.EntityCommandHandlerInterceptor→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.modelling.entity.EntityCommandHandlerInterceptorChain→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.modelling.entity.EntityCommandHandlingComponent→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.modelling.entity.EntityMetamodel→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.modelling.entity.PolymorphicEntityMetamodel→org.axonframework.messaging.core.unitofwork.ProcessingContext
- Direction
- modelling.entity uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break modelling.entity, while a change to modelling.entity can't break messaging.core.unitofwork.
- Position
- Below the diagonal: modelling.entity uses a module listed above it, which is the healthy direction.
28→8 modelling.entity uses messaging.commandhandling✕
- Connections
- 21 pairs of types, where a type in modelling.entity uses a type in messaging.commandhandling.
- The types involved
org.axonframework.modelling.entity.Builder→org.axonframework.messaging.commandhandling.CommandHandlerorg.axonframework.modelling.entity.ChildEntityNotFoundException→org.axonframework.messaging.commandhandling.CommandMessageorg.axonframework.modelling.entity.ConcreteEntityMetamodel→org.axonframework.messaging.commandhandling.CommandHandlerorg.axonframework.modelling.entity.ConcreteEntityMetamodel→org.axonframework.messaging.commandhandling.CommandMessageorg.axonframework.modelling.entity.ConcreteEntityMetamodel→org.axonframework.messaging.commandhandling.CommandResultMessageorg.axonframework.modelling.entity.EntityAlreadyExistsForCreationalCommandHandlerException→org.axonframework.messaging.commandhandling.CommandMessageorg.axonframework.modelling.entity.EntityCommandHandler→org.axonframework.messaging.commandhandling.CommandMessageorg.axonframework.modelling.entity.EntityCommandHandler→org.axonframework.messaging.commandhandling.CommandResultMessageorg.axonframework.modelling.entity.EntityCommandHandlerInterceptor→org.axonframework.messaging.commandhandling.CommandMessageorg.axonframework.modelling.entity.EntityCommandHandlerInterceptorChain→org.axonframework.messaging.commandhandling.CommandMessageorg.axonframework.modelling.entity.EntityCommandHandlingComponent→org.axonframework.messaging.commandhandling.CommandHandlingComponentorg.axonframework.modelling.entity.EntityCommandHandlingComponent→org.axonframework.messaging.commandhandling.CommandMessageorg.axonframework.modelling.entity.EntityCommandHandlingComponent→org.axonframework.messaging.commandhandling.CommandResultMessageorg.axonframework.modelling.entity.EntityMetamodel→org.axonframework.messaging.commandhandling.CommandMessageorg.axonframework.modelling.entity.EntityMetamodel→org.axonframework.messaging.commandhandling.CommandResultMessageorg.axonframework.modelling.entity.EntityMetamodelBuilder→org.axonframework.messaging.commandhandling.CommandHandlerorg.axonframework.modelling.entity.EntityMissingForInstanceCommandHandlerException→org.axonframework.messaging.commandhandling.CommandMessageorg.axonframework.modelling.entity.PolymorphicEntityMetamodel→org.axonframework.messaging.commandhandling.CommandMessageorg.axonframework.modelling.entity.PolymorphicEntityMetamodel→org.axonframework.messaging.commandhandling.CommandResultMessageorg.axonframework.modelling.entity.PolymorphicEntityMetamodelBuilder→org.axonframework.messaging.commandhandling.CommandHandlerorg.axonframework.modelling.entity.WrongPolymorphicEntityTypeException→org.axonframework.messaging.commandhandling.CommandMessage
- Direction
- modelling.entity uses messaging.commandhandling, so a change to messaging.commandhandling can break modelling.entity, while a change to modelling.entity can't break messaging.commandhandling.
- Position
- Below the diagonal: modelling.entity uses a module listed above it, which is the healthy direction.
28→11 modelling.entity uses messaging.eventhandling✕
- Connections
- 2 pairs of types, where a type in modelling.entity uses a type in messaging.eventhandling.
- The types involved
org.axonframework.modelling.entity.ConcreteEntityMetamodel→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.modelling.entity.PolymorphicEntityMetamodel→org.axonframework.messaging.eventhandling.EventMessage
- Direction
- modelling.entity uses messaging.eventhandling, so a change to messaging.eventhandling can break modelling.entity, while a change to modelling.entity can't break messaging.eventhandling.
- Position
- Below the diagonal: modelling.entity uses a module listed above it, which is the healthy direction.
28→15 modelling.entity uses messaging.core✕
- Connections
- 19 pairs of types, where a type in modelling.entity uses a type in messaging.core.
- The types involved
org.axonframework.modelling.entity.Builder→org.axonframework.messaging.core.QualifiedNameorg.axonframework.modelling.entity.ConcreteEntityMetamodel→org.axonframework.messaging.core.Messageorg.axonframework.modelling.entity.ConcreteEntityMetamodel→org.axonframework.messaging.core.MessageStreamorg.axonframework.modelling.entity.ConcreteEntityMetamodel→org.axonframework.messaging.core.QualifiedNameorg.axonframework.modelling.entity.ConcreteEntityMetamodel→org.axonframework.messaging.core.Singleorg.axonframework.modelling.entity.EntityCommandHandler→org.axonframework.messaging.core.MessageHandlerorg.axonframework.modelling.entity.EntityCommandHandler→org.axonframework.messaging.core.Singleorg.axonframework.modelling.entity.EntityCommandHandlerInterceptor→org.axonframework.messaging.core.MessageStreamorg.axonframework.modelling.entity.EntityCommandHandlerInterceptorChain→org.axonframework.messaging.core.MessageStreamorg.axonframework.modelling.entity.EntityCommandHandlingComponent→org.axonframework.messaging.core.QualifiedNameorg.axonframework.modelling.entity.EntityCommandHandlingComponent→org.axonframework.messaging.core.Singleorg.axonframework.modelling.entity.EntityMetamodel→org.axonframework.messaging.core.QualifiedNameorg.axonframework.modelling.entity.EntityMetamodel→org.axonframework.messaging.core.ResourceKeyorg.axonframework.modelling.entity.EntityMetamodel→org.axonframework.messaging.core.Singleorg.axonframework.modelling.entity.EntityMetamodelBuilder→org.axonframework.messaging.core.QualifiedNameorg.axonframework.modelling.entity.PolymorphicEntityMetamodel→org.axonframework.messaging.core.MessageStreamorg.axonframework.modelling.entity.PolymorphicEntityMetamodel→org.axonframework.messaging.core.QualifiedNameorg.axonframework.modelling.entity.PolymorphicEntityMetamodel→org.axonframework.messaging.core.Singleorg.axonframework.modelling.entity.PolymorphicEntityMetamodelBuilder→org.axonframework.messaging.core.QualifiedName
- Direction
- modelling.entity uses messaging.core, so a change to messaging.core can break modelling.entity, while a change to modelling.entity can't break messaging.core.
- Position
- Below the diagonal: modelling.entity uses a module listed above it, which is the healthy direction.
28→20 modelling.entity uses modelling.repository✕
- Connections
- 3 pairs of types, where a type in modelling.entity uses a type in modelling.repository.
- The types involved
org.axonframework.modelling.entity.EntityCommandHandlingComponent→org.axonframework.modelling.repository.ManagedEntityorg.axonframework.modelling.entity.EntityCommandHandlingComponent→org.axonframework.modelling.repository.Repositoryorg.axonframework.modelling.entity.EntityMissingForInstanceCommandHandlerException→org.axonframework.modelling.repository.EntityNotFoundException
- Direction
- modelling.entity uses modelling.repository, so a change to modelling.repository can break modelling.entity, while a change to modelling.entity can't break modelling.repository.
- Position
- Below the diagonal: modelling.entity uses a module listed above it, which is the healthy direction.
28→24 modelling.entity uses modelling✕
- Connections
- 6 pairs of types, where a type in modelling.entity uses a type in modelling.
- The types involved
org.axonframework.modelling.entity.Builder→org.axonframework.modelling.EntityEvolverorg.axonframework.modelling.entity.ConcreteEntityMetamodel→org.axonframework.modelling.EntityEvolverorg.axonframework.modelling.entity.EntityCommandHandlingComponent→org.axonframework.modelling.EntityIdResolverorg.axonframework.modelling.entity.EntityMetamodel→org.axonframework.modelling.EntityEvolverorg.axonframework.modelling.entity.EntityMetamodelBuilder→org.axonframework.modelling.EntityEvolverorg.axonframework.modelling.entity.PolymorphicEntityMetamodelBuilder→org.axonframework.modelling.EntityEvolver
- Direction
- modelling.entity uses modelling, so a change to modelling can break modelling.entity, while a change to modelling.entity can't break modelling.
- Position
- Below the diagonal: modelling.entity uses a module listed above it, which is the healthy direction.
29→1 eventsourcing.eventstore.jpa uses common✕
- Connections
- 3 pairs of types, where a type in eventsourcing.eventstore.jpa uses a type in common.
- The types involved
org.axonframework.eventsourcing.eventstore.jpa.1→org.axonframework.common.TypeReferenceorg.axonframework.eventsourcing.eventstore.jpa.4985→org.axonframework.common.TypeReferenceorg.axonframework.eventsourcing.eventstore.jpa.AggregateBasedJpaEventStorageEngine→org.axonframework.common.TypeReference
- Direction
- eventsourcing.eventstore.jpa uses common, so a change to common can break eventsourcing.eventstore.jpa, while a change to eventsourcing.eventstore.jpa can't break common.
- Position
- Below the diagonal: eventsourcing.eventstore.jpa uses a module listed above it, which is the healthy direction.
29→2 eventsourcing.eventstore.jpa uses common.tx✕
- Connections
- 1 pair of types, where a type in eventsourcing.eventstore.jpa uses a type in common.tx.
- The types involved
org.axonframework.eventsourcing.eventstore.jpa.AggregateBasedJpaEventStorageEngine→org.axonframework.common.tx.TransactionalExecutor
- Direction
- eventsourcing.eventstore.jpa uses common.tx, so a change to common.tx can break eventsourcing.eventstore.jpa, while a change to eventsourcing.eventstore.jpa can't break common.tx.
- Position
- Below the diagonal: eventsourcing.eventstore.jpa uses a module listed above it, which is the healthy direction.
29→3 eventsourcing.eventstore.jpa uses common.infra✕
- Connections
- 1 pair of types, where a type in eventsourcing.eventstore.jpa uses a type in common.infra.
- The types involved
org.axonframework.eventsourcing.eventstore.jpa.AggregateBasedJpaEventStorageEngine→org.axonframework.common.infra.ComponentDescriptor
- Direction
- eventsourcing.eventstore.jpa uses common.infra, so a change to common.infra can break eventsourcing.eventstore.jpa, while a change to eventsourcing.eventstore.jpa can't break common.infra.
- Position
- Below the diagonal: eventsourcing.eventstore.jpa uses a module listed above it, which is the healthy direction.
29→4 eventsourcing.eventstore.jpa uses messaging.core.unitofwork.transaction✕
- Connections
- 1 pair of types, where a type in eventsourcing.eventstore.jpa uses a type in messaging.core.unitofwork.transaction.
- The types involved
org.axonframework.eventsourcing.eventstore.jpa.AggregateBasedJpaEventStorageEngine→org.axonframework.messaging.core.unitofwork.transaction.TransactionalExecutorProvider
- Direction
- eventsourcing.eventstore.jpa uses messaging.core.unitofwork.transaction, so a change to messaging.core.unitofwork.transaction can break eventsourcing.eventstore.jpa, while a change to eventsourcing.eventstore.jpa can't break messaging.core.unitofwork.transaction.
- Position
- Below the diagonal: eventsourcing.eventstore.jpa uses a module listed above it, which is the healthy direction.
29→6 eventsourcing.eventstore.jpa uses conversion✕
- Connections
- 1 pair of types, where a type in eventsourcing.eventstore.jpa uses a type in conversion.
- The types involved
org.axonframework.eventsourcing.eventstore.jpa.AggregateBasedJpaEventStorageEngine→org.axonframework.conversion.Converter
- Direction
- eventsourcing.eventstore.jpa uses conversion, so a change to conversion can break eventsourcing.eventstore.jpa, while a change to eventsourcing.eventstore.jpa can't break conversion.
- Position
- Below the diagonal: eventsourcing.eventstore.jpa uses a module listed above it, which is the healthy direction.
29→7 eventsourcing.eventstore.jpa uses messaging.core.unitofwork✕
- Connections
- 1 pair of types, where a type in eventsourcing.eventstore.jpa uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.eventsourcing.eventstore.jpa.AggregateBasedJpaEventStorageEngine→org.axonframework.messaging.core.unitofwork.ProcessingContext
- Direction
- eventsourcing.eventstore.jpa uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break eventsourcing.eventstore.jpa, while a change to eventsourcing.eventstore.jpa can't break messaging.core.unitofwork.
- Position
- Below the diagonal: eventsourcing.eventstore.jpa uses a module listed above it, which is the healthy direction.
29→11 eventsourcing.eventstore.jpa uses messaging.eventhandling✕
- Connections
- 3 pairs of types, where a type in eventsourcing.eventstore.jpa uses a type in messaging.eventhandling.
- The types involved
org.axonframework.eventsourcing.eventstore.jpa.AggregateBasedJpaEventStorageEngine→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.eventsourcing.eventstore.jpa.AggregateBasedJpaEventStorageEngine→org.axonframework.messaging.eventhandling.GenericEventMessageorg.axonframework.eventsourcing.eventstore.jpa.AggregateSource→org.axonframework.messaging.eventhandling.EventMessage
- Direction
- eventsourcing.eventstore.jpa uses messaging.eventhandling, so a change to messaging.eventhandling can break eventsourcing.eventstore.jpa, while a change to eventsourcing.eventstore.jpa can't break messaging.eventhandling.
- Position
- Below the diagonal: eventsourcing.eventstore.jpa uses a module listed above it, which is the healthy direction.
29→12 eventsourcing.eventstore.jpa uses messaging.eventhandling.conversion✕
- Connections
- 1 pair of types, where a type in eventsourcing.eventstore.jpa uses a type in messaging.eventhandling.conversion.
- The types involved
org.axonframework.eventsourcing.eventstore.jpa.AggregateBasedJpaEventStorageEngine→org.axonframework.messaging.eventhandling.conversion.EventConverter
- Direction
- eventsourcing.eventstore.jpa uses messaging.eventhandling.conversion, so a change to messaging.eventhandling.conversion can break eventsourcing.eventstore.jpa, while a change to eventsourcing.eventstore.jpa can't break messaging.eventhandling.conversion.
- Position
- Below the diagonal: eventsourcing.eventstore.jpa uses a module listed above it, which is the healthy direction.
29→15 eventsourcing.eventstore.jpa uses messaging.core✕
- Connections
- 3 pairs of types, where a type in eventsourcing.eventstore.jpa uses a type in messaging.core.
- The types involved
org.axonframework.eventsourcing.eventstore.jpa.AggregateBasedJpaEventStorageEngine→org.axonframework.messaging.core.Contextorg.axonframework.eventsourcing.eventstore.jpa.AggregateBasedJpaEventStorageEngine→org.axonframework.messaging.core.MessageStreamorg.axonframework.eventsourcing.eventstore.jpa.AggregateSource→org.axonframework.messaging.core.MessageStream
- Direction
- eventsourcing.eventstore.jpa uses messaging.core, so a change to messaging.core can break eventsourcing.eventstore.jpa, while a change to eventsourcing.eventstore.jpa can't break messaging.core.
- Position
- Below the diagonal: eventsourcing.eventstore.jpa uses a module listed above it, which is the healthy direction.
29→17 eventsourcing.eventstore.jpa uses messaging.eventhandling.processing.streaming.token✕
- Connections
- 5 pairs of types, where a type in eventsourcing.eventstore.jpa uses a type in messaging.eventhandling.processing.streaming.token.
- The types involved
org.axonframework.eventsourcing.eventstore.jpa.AggregateBasedJpaEventStorageEngine→org.axonframework.messaging.eventhandling.processing.streaming.token.GapAwareTrackingTokenorg.axonframework.eventsourcing.eventstore.jpa.AggregateBasedJpaEventStorageEngine→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingTokenorg.axonframework.eventsourcing.eventstore.jpa.GapAwareTrackingTokenOperations→org.axonframework.messaging.eventhandling.processing.streaming.token.GapAwareTrackingTokenorg.axonframework.eventsourcing.eventstore.jpa.GapAwareTrackingTokenOperations→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingTokenorg.axonframework.eventsourcing.eventstore.jpa.TokenAndEvent→org.axonframework.messaging.eventhandling.processing.streaming.token.GapAwareTrackingToken
- Direction
- eventsourcing.eventstore.jpa uses messaging.eventhandling.processing.streaming.token, so a change to messaging.eventhandling.processing.streaming.token can break eventsourcing.eventstore.jpa, while a change to eventsourcing.eventstore.jpa can't break messaging.eventhandling.processing.streaming.token.
- Position
- Below the diagonal: eventsourcing.eventstore.jpa uses a module listed above it, which is the healthy direction.
29→23 eventsourcing.eventstore.jpa uses messaging.eventstreaming✕
- Connections
- 2 pairs of types, where a type in eventsourcing.eventstore.jpa uses a type in messaging.eventstreaming.
- The types involved
org.axonframework.eventsourcing.eventstore.jpa.AggregateBasedJpaEventStorageEngine→org.axonframework.messaging.eventstreaming.EventCriterionorg.axonframework.eventsourcing.eventstore.jpa.AggregateBasedJpaEventStorageEngine→org.axonframework.messaging.eventstreaming.StreamingCondition
- Direction
- eventsourcing.eventstore.jpa uses messaging.eventstreaming, so a change to messaging.eventstreaming can break eventsourcing.eventstore.jpa, while a change to eventsourcing.eventstore.jpa can't break messaging.eventstreaming.
- Position
- Below the diagonal: eventsourcing.eventstore.jpa uses a module listed above it, which is the healthy direction.
29→25 eventsourcing.eventstore.jpa uses eventsourcing.eventstore✕
- Connections
- 17 pairs of types, where a type in eventsourcing.eventstore.jpa uses a type in eventsourcing.eventstore.
- The types involved
org.axonframework.eventsourcing.eventstore.jpa.10869→org.axonframework.eventsourcing.eventstore.AggregateBasedConsistencyMarkerorg.axonframework.eventsourcing.eventstore.jpa.10869→org.axonframework.eventsourcing.eventstore.ConsistencyMarkerorg.axonframework.eventsourcing.eventstore.jpa.AggregateBasedJpaEventStorageEngine→org.axonframework.eventsourcing.eventstore.AggregateBasedConsistencyMarkerorg.axonframework.eventsourcing.eventstore.jpa.AggregateBasedJpaEventStorageEngine→org.axonframework.eventsourcing.eventstore.AggregateSequencerorg.axonframework.eventsourcing.eventstore.jpa.AggregateBasedJpaEventStorageEngine→org.axonframework.eventsourcing.eventstore.AppendConditionorg.axonframework.eventsourcing.eventstore.jpa.AggregateBasedJpaEventStorageEngine→org.axonframework.eventsourcing.eventstore.AppendTransactionorg.axonframework.eventsourcing.eventstore.jpa.AggregateBasedJpaEventStorageEngine→org.axonframework.eventsourcing.eventstore.ConsistencyMarkerorg.axonframework.eventsourcing.eventstore.jpa.AggregateBasedJpaEventStorageEngine→org.axonframework.eventsourcing.eventstore.EventStorageEngineorg.axonframework.eventsourcing.eventstore.jpa.AggregateBasedJpaEventStorageEngine→org.axonframework.eventsourcing.eventstore.EventTypeResolverorg.axonframework.eventsourcing.eventstore.jpa.AggregateBasedJpaEventStorageEngine→org.axonframework.eventsourcing.eventstore.Handleorg.axonframework.eventsourcing.eventstore.jpa.AggregateBasedJpaEventStorageEngine→org.axonframework.eventsourcing.eventstore.SourcingConditionorg.axonframework.eventsourcing.eventstore.jpa.AggregateBasedJpaEventStorageEngine→org.axonframework.eventsourcing.eventstore.TaggedEventMessageorg.axonframework.eventsourcing.eventstore.jpa.AggregateBasedJpaEventStorageEngineConfiguration→org.axonframework.eventsourcing.eventstore.EventCoordinatororg.axonframework.eventsourcing.eventstore.jpa.AggregateBasedJpaEventStorageEngineConfiguration→org.axonframework.eventsourcing.eventstore.EventTypeResolverorg.axonframework.eventsourcing.eventstore.jpa.AggregateSource→org.axonframework.eventsourcing.eventstore.AggregateBasedConsistencyMarkerorg.axonframework.eventsourcing.eventstore.jpa.JpaPollingEventCoordinator→org.axonframework.eventsourcing.eventstore.EventCoordinatororg.axonframework.eventsourcing.eventstore.jpa.JpaPollingEventCoordinator→org.axonframework.eventsourcing.eventstore.Handle
- Direction
- eventsourcing.eventstore.jpa uses eventsourcing.eventstore, so a change to eventsourcing.eventstore can break eventsourcing.eventstore.jpa, while a change to eventsourcing.eventstore.jpa can't break eventsourcing.eventstore.
- Position
- Below the diagonal: eventsourcing.eventstore.jpa uses a module listed above it, which is the healthy direction.
30→1 eventsourcing.eventstore.tracing uses common✕
- Connections
- 1 pair of types, where a type in eventsourcing.eventstore.tracing uses a type in common.
- The types involved
org.axonframework.eventsourcing.eventstore.tracing.TracingEventStore→org.axonframework.common.Registration
- Direction
- eventsourcing.eventstore.tracing uses common, so a change to common can break eventsourcing.eventstore.tracing, while a change to eventsourcing.eventstore.tracing can't break common.
- Position
- Below the diagonal: eventsourcing.eventstore.tracing uses a module listed above it, which is the healthy direction.
30→3 eventsourcing.eventstore.tracing uses common.infra✕
- Connections
- 2 pairs of types, where a type in eventsourcing.eventstore.tracing uses a type in common.infra.
- The types involved
org.axonframework.eventsourcing.eventstore.tracing.TracingEventStorageEngine→org.axonframework.common.infra.ComponentDescriptororg.axonframework.eventsourcing.eventstore.tracing.TracingEventStore→org.axonframework.common.infra.ComponentDescriptor
- Direction
- eventsourcing.eventstore.tracing uses common.infra, so a change to common.infra can break eventsourcing.eventstore.tracing, while a change to eventsourcing.eventstore.tracing can't break common.infra.
- Position
- Below the diagonal: eventsourcing.eventstore.tracing uses a module listed above it, which is the healthy direction.
30→5 eventsourcing.eventstore.tracing uses common.configuration✕
- Connections
- 1 pair of types, where a type in eventsourcing.eventstore.tracing uses a type in common.configuration.
- The types involved
org.axonframework.eventsourcing.eventstore.tracing.TracingEventStorageEngine→org.axonframework.common.configuration.DecoratingComponent
- Direction
- eventsourcing.eventstore.tracing uses common.configuration, so a change to common.configuration can break eventsourcing.eventstore.tracing, while a change to eventsourcing.eventstore.tracing can't break common.configuration.
- Position
- Below the diagonal: eventsourcing.eventstore.tracing uses a module listed above it, which is the healthy direction.
30→7 eventsourcing.eventstore.tracing uses messaging.core.unitofwork✕
- Connections
- 2 pairs of types, where a type in eventsourcing.eventstore.tracing uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.eventsourcing.eventstore.tracing.TracingEventStorageEngine→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.eventsourcing.eventstore.tracing.TracingEventStore→org.axonframework.messaging.core.unitofwork.ProcessingContext
- Direction
- eventsourcing.eventstore.tracing uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break eventsourcing.eventstore.tracing, while a change to eventsourcing.eventstore.tracing can't break messaging.core.unitofwork.
- Position
- Below the diagonal: eventsourcing.eventstore.tracing uses a module listed above it, which is the healthy direction.
30→11 eventsourcing.eventstore.tracing uses messaging.eventhandling✕
- Connections
- 2 pairs of types, where a type in eventsourcing.eventstore.tracing uses a type in messaging.eventhandling.
- The types involved
org.axonframework.eventsourcing.eventstore.tracing.TracingEventStorageEngine→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.eventsourcing.eventstore.tracing.TracingEventStore→org.axonframework.messaging.eventhandling.EventMessage
- Direction
- eventsourcing.eventstore.tracing uses messaging.eventhandling, so a change to messaging.eventhandling can break eventsourcing.eventstore.tracing, while a change to eventsourcing.eventstore.tracing can't break messaging.eventhandling.
- Position
- Below the diagonal: eventsourcing.eventstore.tracing uses a module listed above it, which is the healthy direction.
30→15 eventsourcing.eventstore.tracing uses messaging.core✕
- Connections
- 2 pairs of types, where a type in eventsourcing.eventstore.tracing uses a type in messaging.core.
- The types involved
org.axonframework.eventsourcing.eventstore.tracing.TracingEventStorageEngine→org.axonframework.messaging.core.MessageStreamorg.axonframework.eventsourcing.eventstore.tracing.TracingEventStore→org.axonframework.messaging.core.MessageStream
- Direction
- eventsourcing.eventstore.tracing uses messaging.core, so a change to messaging.core can break eventsourcing.eventstore.tracing, while a change to eventsourcing.eventstore.tracing can't break messaging.core.
- Position
- Below the diagonal: eventsourcing.eventstore.tracing uses a module listed above it, which is the healthy direction.
30→17 eventsourcing.eventstore.tracing uses messaging.eventhandling.processing.streaming.token✕
- Connections
- 2 pairs of types, where a type in eventsourcing.eventstore.tracing uses a type in messaging.eventhandling.processing.streaming.token.
- The types involved
org.axonframework.eventsourcing.eventstore.tracing.TracingEventStorageEngine→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingTokenorg.axonframework.eventsourcing.eventstore.tracing.TracingEventStore→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingToken
- Direction
- eventsourcing.eventstore.tracing uses messaging.eventhandling.processing.streaming.token, so a change to messaging.eventhandling.processing.streaming.token can break eventsourcing.eventstore.tracing, while a change to eventsourcing.eventstore.tracing can't break messaging.eventhandling.processing.streaming.token.
- Position
- Below the diagonal: eventsourcing.eventstore.tracing uses a module listed above it, which is the healthy direction.
30→19 eventsourcing.eventstore.tracing uses messaging.tracing✕
- Connections
- 4 pairs of types, where a type in eventsourcing.eventstore.tracing uses a type in messaging.tracing.
- The types involved
org.axonframework.eventsourcing.eventstore.tracing.TracingAppendTransaction→org.axonframework.messaging.tracing.SpanScopeorg.axonframework.eventsourcing.eventstore.tracing.TracingEventStorageEngine→org.axonframework.messaging.tracing.SpanFactoryorg.axonframework.eventsourcing.eventstore.tracing.TracingEventStorageEngine→org.axonframework.messaging.tracing.SpanScopeorg.axonframework.eventsourcing.eventstore.tracing.TracingEventStore→org.axonframework.messaging.tracing.SpanFactory
- Direction
- eventsourcing.eventstore.tracing uses messaging.tracing, so a change to messaging.tracing can break eventsourcing.eventstore.tracing, while a change to eventsourcing.eventstore.tracing can't break messaging.tracing.
- Position
- Below the diagonal: eventsourcing.eventstore.tracing uses a module listed above it, which is the healthy direction.
30→23 eventsourcing.eventstore.tracing uses messaging.eventstreaming✕
- Connections
- 2 pairs of types, where a type in eventsourcing.eventstore.tracing uses a type in messaging.eventstreaming.
- The types involved
org.axonframework.eventsourcing.eventstore.tracing.TracingEventStorageEngine→org.axonframework.messaging.eventstreaming.StreamingConditionorg.axonframework.eventsourcing.eventstore.tracing.TracingEventStore→org.axonframework.messaging.eventstreaming.StreamingCondition
- Direction
- eventsourcing.eventstore.tracing uses messaging.eventstreaming, so a change to messaging.eventstreaming can break eventsourcing.eventstore.tracing, while a change to eventsourcing.eventstore.tracing can't break messaging.eventstreaming.
- Position
- Below the diagonal: eventsourcing.eventstore.tracing uses a module listed above it, which is the healthy direction.
30→25 eventsourcing.eventstore.tracing uses eventsourcing.eventstore✕
- Connections
- 9 pairs of types, where a type in eventsourcing.eventstore.tracing uses a type in eventsourcing.eventstore.
- The types involved
org.axonframework.eventsourcing.eventstore.tracing.TracingAppendTransaction→org.axonframework.eventsourcing.eventstore.AppendTransactionorg.axonframework.eventsourcing.eventstore.tracing.TracingAppendTransaction→org.axonframework.eventsourcing.eventstore.ConsistencyMarkerorg.axonframework.eventsourcing.eventstore.tracing.TracingEventStorageEngine→org.axonframework.eventsourcing.eventstore.AppendConditionorg.axonframework.eventsourcing.eventstore.tracing.TracingEventStorageEngine→org.axonframework.eventsourcing.eventstore.AppendTransactionorg.axonframework.eventsourcing.eventstore.tracing.TracingEventStorageEngine→org.axonframework.eventsourcing.eventstore.EventStorageEngineorg.axonframework.eventsourcing.eventstore.tracing.TracingEventStorageEngine→org.axonframework.eventsourcing.eventstore.SourcingConditionorg.axonframework.eventsourcing.eventstore.tracing.TracingEventStorageEngine→org.axonframework.eventsourcing.eventstore.TaggedEventMessageorg.axonframework.eventsourcing.eventstore.tracing.TracingEventStore→org.axonframework.eventsourcing.eventstore.EventStoreorg.axonframework.eventsourcing.eventstore.tracing.TracingEventStore→org.axonframework.eventsourcing.eventstore.EventStoreTransaction
- Direction
- eventsourcing.eventstore.tracing uses eventsourcing.eventstore, so a change to eventsourcing.eventstore can break eventsourcing.eventstore.tracing, while a change to eventsourcing.eventstore.tracing can't break eventsourcing.eventstore.
- Position
- Below the diagonal: eventsourcing.eventstore.tracing uses a module listed above it, which is the healthy direction.
31→3 eventsourcing.handler uses common.infra✕
- Connections
- 5 pairs of types, where a type in eventsourcing.handler uses a type in common.infra.
- The types involved
org.axonframework.eventsourcing.handler.EntityLifecycleHandler→org.axonframework.common.infra.DescribableComponentorg.axonframework.eventsourcing.handler.InitializingEntityEvolver→org.axonframework.common.infra.ComponentDescriptororg.axonframework.eventsourcing.handler.InitializingEntityEvolver→org.axonframework.common.infra.DescribableComponentorg.axonframework.eventsourcing.handler.SimpleEntityLifecycleHandler→org.axonframework.common.infra.ComponentDescriptororg.axonframework.eventsourcing.handler.SnapshottingEntityLifecycleHandler→org.axonframework.common.infra.ComponentDescriptor
- Direction
- eventsourcing.handler uses common.infra, so a change to common.infra can break eventsourcing.handler, while a change to eventsourcing.handler can't break common.infra.
- Position
- Below the diagonal: eventsourcing.handler uses a module listed above it, which is the healthy direction.
31→6 eventsourcing.handler uses conversion✕
- Connections
- 1 pair of types, where a type in eventsourcing.handler uses a type in conversion.
- The types involved
org.axonframework.eventsourcing.handler.SnapshottingEntityLifecycleHandler→org.axonframework.conversion.Converter
- Direction
- eventsourcing.handler uses conversion, so a change to conversion can break eventsourcing.handler, while a change to eventsourcing.handler can't break conversion.
- Position
- Below the diagonal: eventsourcing.handler uses a module listed above it, which is the healthy direction.
31→7 eventsourcing.handler uses messaging.core.unitofwork✕
- Connections
- 5 pairs of types, where a type in eventsourcing.handler uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.eventsourcing.handler.EntityLifecycleHandler→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.eventsourcing.handler.InitializingEntityEvolver→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.eventsourcing.handler.SimpleEntityLifecycleHandler→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.eventsourcing.handler.SnapshottingEntityLifecycleHandler→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.eventsourcing.handler.SourcingHandler→org.axonframework.messaging.core.unitofwork.ProcessingContext
- Direction
- eventsourcing.handler uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break eventsourcing.handler, while a change to eventsourcing.handler can't break messaging.core.unitofwork.
- Position
- Below the diagonal: eventsourcing.handler uses a module listed above it, which is the healthy direction.
31→11 eventsourcing.handler uses messaging.eventhandling✕
- Connections
- 1 pair of types, where a type in eventsourcing.handler uses a type in messaging.eventhandling.
- The types involved
org.axonframework.eventsourcing.handler.InitializingEntityEvolver→org.axonframework.messaging.eventhandling.EventMessage
- Direction
- eventsourcing.handler uses messaging.eventhandling, so a change to messaging.eventhandling can break eventsourcing.handler, while a change to eventsourcing.handler can't break messaging.eventhandling.
- Position
- Below the diagonal: eventsourcing.handler uses a module listed above it, which is the healthy direction.
31→15 eventsourcing.handler uses messaging.core✕
- Connections
- 1 pair of types, where a type in eventsourcing.handler uses a type in messaging.core.
- The types involved
org.axonframework.eventsourcing.handler.SnapshottingEntityLifecycleHandler→org.axonframework.messaging.core.VersionedType
- Direction
- eventsourcing.handler uses messaging.core, so a change to messaging.core can break eventsourcing.handler, while a change to eventsourcing.handler can't break messaging.core.
- Position
- Below the diagonal: eventsourcing.handler uses a module listed above it, which is the healthy direction.
31→20 eventsourcing.handler uses modelling.repository✕
- Connections
- 3 pairs of types, where a type in eventsourcing.handler uses a type in modelling.repository.
- The types involved
org.axonframework.eventsourcing.handler.EntityLifecycleHandler→org.axonframework.modelling.repository.ManagedEntityorg.axonframework.eventsourcing.handler.SimpleEntityLifecycleHandler→org.axonframework.modelling.repository.ManagedEntityorg.axonframework.eventsourcing.handler.SnapshottingEntityLifecycleHandler→org.axonframework.modelling.repository.ManagedEntity
- Direction
- eventsourcing.handler uses modelling.repository, so a change to modelling.repository can break eventsourcing.handler, while a change to eventsourcing.handler can't break modelling.repository.
- Position
- Below the diagonal: eventsourcing.handler uses a module listed above it, which is the healthy direction.
31→24 eventsourcing.handler uses modelling✕
- Connections
- 1 pair of types, where a type in eventsourcing.handler uses a type in modelling.
- The types involved
org.axonframework.eventsourcing.handler.InitializingEntityEvolver→org.axonframework.modelling.EntityEvolver
- Direction
- eventsourcing.handler uses modelling, so a change to modelling can break eventsourcing.handler, while a change to eventsourcing.handler can't break modelling.
- Position
- Below the diagonal: eventsourcing.handler uses a module listed above it, which is the healthy direction.
31→25 eventsourcing.handler uses eventsourcing.eventstore✕
- Connections
- 5 pairs of types, where a type in eventsourcing.handler uses a type in eventsourcing.eventstore.
- The types involved
org.axonframework.eventsourcing.handler.SimpleEntityLifecycleHandler→org.axonframework.eventsourcing.eventstore.EventStoreorg.axonframework.eventsourcing.handler.SimpleEntityLifecycleHandler→org.axonframework.eventsourcing.eventstore.TagResolverorg.axonframework.eventsourcing.handler.SnapshottingEntityLifecycleHandler→org.axonframework.eventsourcing.eventstore.EventStoreorg.axonframework.eventsourcing.handler.SnapshottingEntityLifecycleHandler→org.axonframework.eventsourcing.eventstore.Positionorg.axonframework.eventsourcing.handler.SnapshottingEntityLifecycleHandler→org.axonframework.eventsourcing.eventstore.TagResolver
- Direction
- eventsourcing.handler uses eventsourcing.eventstore, so a change to eventsourcing.eventstore can break eventsourcing.handler, while a change to eventsourcing.handler can't break eventsourcing.eventstore.
- Position
- Below the diagonal: eventsourcing.handler uses a module listed above it, which is the healthy direction.
31→35 eventsourcing.handler uses eventsourcing part of a loop✕
- Connections
- 3 pairs of types, where a type in eventsourcing.handler uses a type in eventsourcing.
- The types involved
org.axonframework.eventsourcing.handler.InitializingEntityEvolver→org.axonframework.eventsourcing.EventSourcedEntityFactoryorg.axonframework.eventsourcing.handler.SimpleEntityLifecycleHandler→org.axonframework.eventsourcing.CriteriaResolverorg.axonframework.eventsourcing.handler.SnapshottingEntityLifecycleHandler→org.axonframework.eventsourcing.CriteriaResolver
- Direction
- eventsourcing.handler uses eventsourcing, so a change to eventsourcing can break eventsourcing.handler, while a change to eventsourcing.handler can't break eventsourcing.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→3 messaging.eventhandling.processing.streaming.pooled uses common.infra✕
- Connections
- 2 pairs of types, where a type in messaging.eventhandling.processing.streaming.pooled uses a type in common.infra.
- The types involved
org.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessor→org.axonframework.common.infra.ComponentDescriptororg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorConfiguration→org.axonframework.common.infra.ComponentDescriptor
- Direction
- messaging.eventhandling.processing.streaming.pooled uses common.infra, so a change to common.infra can break messaging.eventhandling.processing.streaming.pooled, while a change to messaging.eventhandling.processing.streaming.pooled can't break common.infra.
- Position
- Below the diagonal: messaging.eventhandling.processing.streaming.pooled uses a module listed above it, which is the healthy direction.
32→5 messaging.eventhandling.processing.streaming.pooled uses common.configuration✕
- Connections
- 8 pairs of types, where a type in messaging.eventhandling.processing.streaming.pooled uses a type in common.configuration.
- The types involved
org.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorConfiguration→org.axonframework.common.configuration.Configurationorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorModule→org.axonframework.common.configuration.BaseModuleorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorModule→org.axonframework.common.configuration.ComponentBuilderorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorModule→org.axonframework.common.configuration.Configurationorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorModule→org.axonframework.common.configuration.ModuleBuilderorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorsConfigurer→org.axonframework.common.configuration.ComponentRegistryorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorsConfigurer→org.axonframework.common.configuration.Configurationorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorsConfigurer→org.axonframework.common.configuration.ModuleBuilder
- Direction
- messaging.eventhandling.processing.streaming.pooled uses common.configuration, so a change to common.configuration can break messaging.eventhandling.processing.streaming.pooled, while a change to messaging.eventhandling.processing.streaming.pooled can't break common.configuration.
- Position
- Below the diagonal: messaging.eventhandling.processing.streaming.pooled uses a module listed above it, which is the healthy direction.
32→7 messaging.eventhandling.processing.streaming.pooled uses messaging.core.unitofwork✕
- Connections
- 20 pairs of types, where a type in messaging.eventhandling.processing.streaming.pooled uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.messaging.eventhandling.processing.streaming.pooled.BatchProcessor→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventhandling.processing.streaming.pooled.Builder→org.axonframework.messaging.core.unitofwork.UnitOfWorkFactoryorg.axonframework.messaging.eventhandling.processing.streaming.pooled.ClaimTask→org.axonframework.messaging.core.unitofwork.UnitOfWorkFactoryorg.axonframework.messaging.eventhandling.processing.streaming.pooled.Coordinator→org.axonframework.messaging.core.unitofwork.UnitOfWorkFactoryorg.axonframework.messaging.eventhandling.processing.streaming.pooled.CoordinatorTask→org.axonframework.messaging.core.unitofwork.UnitOfWorkFactoryorg.axonframework.messaging.eventhandling.processing.streaming.pooled.DefaultWorkPackageEventFilter→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventhandling.processing.streaming.pooled.EventFilter→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventhandling.processing.streaming.pooled.EventSchedulingProcessingContext→org.axonframework.messaging.core.unitofwork.ErrorHandlerorg.axonframework.messaging.eventhandling.processing.streaming.pooled.EventSchedulingProcessingContext→org.axonframework.messaging.core.unitofwork.Phaseorg.axonframework.messaging.eventhandling.processing.streaming.pooled.EventSchedulingProcessingContext→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventhandling.processing.streaming.pooled.EventSchedulingProcessingContext→org.axonframework.messaging.core.unitofwork.ProcessingLifecycleorg.axonframework.messaging.eventhandling.processing.streaming.pooled.MergeTask→org.axonframework.messaging.core.unitofwork.UnitOfWorkFactoryorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessor→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessor→org.axonframework.messaging.core.unitofwork.UnitOfWorkFactoryorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorConfiguration→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorConfiguration→org.axonframework.messaging.core.unitofwork.UnitOfWorkFactoryorg.axonframework.messaging.eventhandling.processing.streaming.pooled.SplitTask→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventhandling.processing.streaming.pooled.SplitTask→org.axonframework.messaging.core.unitofwork.UnitOfWorkFactoryorg.axonframework.messaging.eventhandling.processing.streaming.pooled.WorkPackage→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventhandling.processing.streaming.pooled.WorkPackage→org.axonframework.messaging.core.unitofwork.UnitOfWorkFactory
- Direction
- messaging.eventhandling.processing.streaming.pooled uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break messaging.eventhandling.processing.streaming.pooled, while a change to messaging.eventhandling.processing.streaming.pooled can't break messaging.core.unitofwork.
- Position
- Below the diagonal: messaging.eventhandling.processing.streaming.pooled uses a module listed above it, which is the healthy direction.
32→11 messaging.eventhandling.processing.streaming.pooled uses messaging.eventhandling✕
- Connections
- 15 pairs of types, where a type in messaging.eventhandling.processing.streaming.pooled uses a type in messaging.eventhandling.
- The types involved
org.axonframework.messaging.eventhandling.processing.streaming.pooled.BatchProcessingEntry→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.messaging.eventhandling.processing.streaming.pooled.BatchProcessor→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.messaging.eventhandling.processing.streaming.pooled.Builder→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.messaging.eventhandling.processing.streaming.pooled.CoordinationTask→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.messaging.eventhandling.processing.streaming.pooled.Coordinator→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.messaging.eventhandling.processing.streaming.pooled.DefaultProcessingEntry→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.messaging.eventhandling.processing.streaming.pooled.DefaultWorkPackageEventFilter→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.messaging.eventhandling.processing.streaming.pooled.EventFilter→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessor→org.axonframework.messaging.eventhandling.EventHandlingComponentorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessor→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorConfiguration→org.axonframework.messaging.eventhandling.EventHandlingComponentorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorConfiguration→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorModule→org.axonframework.messaging.eventhandling.EventHandlingComponentorg.axonframework.messaging.eventhandling.processing.streaming.pooled.ProcessingEntry→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.messaging.eventhandling.processing.streaming.pooled.WorkPackage→org.axonframework.messaging.eventhandling.EventMessage
- Direction
- messaging.eventhandling.processing.streaming.pooled uses messaging.eventhandling, so a change to messaging.eventhandling can break messaging.eventhandling.processing.streaming.pooled, while a change to messaging.eventhandling.processing.streaming.pooled can't break messaging.eventhandling.
- Position
- Below the diagonal: messaging.eventhandling.processing.streaming.pooled uses a module listed above it, which is the healthy direction.
32→13 messaging.eventhandling.processing.streaming.pooled uses messaging.core.sequencing✕
- Connections
- 1 pair of types, where a type in messaging.eventhandling.processing.streaming.pooled uses a type in messaging.core.sequencing.
- The types involved
org.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorConfiguration→org.axonframework.messaging.core.sequencing.SequencingPolicy
- Direction
- messaging.eventhandling.processing.streaming.pooled uses messaging.core.sequencing, so a change to messaging.core.sequencing can break messaging.eventhandling.processing.streaming.pooled, while a change to messaging.eventhandling.processing.streaming.pooled can't break messaging.core.sequencing.
- Position
- Below the diagonal: messaging.eventhandling.processing.streaming.pooled uses a module listed above it, which is the healthy direction.
32→15 messaging.eventhandling.processing.streaming.pooled uses messaging.core✕
- Connections
- 18 pairs of types, where a type in messaging.eventhandling.processing.streaming.pooled uses a type in messaging.core.
- The types involved
org.axonframework.messaging.eventhandling.processing.streaming.pooled.BatchProcessingEntry→org.axonframework.messaging.core.Entryorg.axonframework.messaging.eventhandling.processing.streaming.pooled.BatchProcessor→org.axonframework.messaging.core.Emptyorg.axonframework.messaging.eventhandling.processing.streaming.pooled.BatchProcessor→org.axonframework.messaging.core.Entryorg.axonframework.messaging.eventhandling.processing.streaming.pooled.BatchProcessor→org.axonframework.messaging.core.Messageorg.axonframework.messaging.eventhandling.processing.streaming.pooled.CoordinationTask→org.axonframework.messaging.core.Entryorg.axonframework.messaging.eventhandling.processing.streaming.pooled.CoordinationTask→org.axonframework.messaging.core.MessageStreamorg.axonframework.messaging.eventhandling.processing.streaming.pooled.DefaultProcessingEntry→org.axonframework.messaging.core.Entryorg.axonframework.messaging.eventhandling.processing.streaming.pooled.EventSchedulingProcessingContext→org.axonframework.messaging.core.ApplicationContextorg.axonframework.messaging.eventhandling.processing.streaming.pooled.EventSchedulingProcessingContext→org.axonframework.messaging.core.ResourceKeyorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessor→org.axonframework.messaging.core.Emptyorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessor→org.axonframework.messaging.core.Entryorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessor→org.axonframework.messaging.core.Messageorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorConfiguration→org.axonframework.messaging.core.MessageHandlerInterceptororg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorConfiguration→org.axonframework.messaging.core.QualifiedNameorg.axonframework.messaging.eventhandling.processing.streaming.pooled.ProcessingEntry→org.axonframework.messaging.core.Entryorg.axonframework.messaging.eventhandling.processing.streaming.pooled.WorkPackage→org.axonframework.messaging.core.Contextorg.axonframework.messaging.eventhandling.processing.streaming.pooled.WorkPackage→org.axonframework.messaging.core.Entryorg.axonframework.messaging.eventhandling.processing.streaming.pooled.WorkPackage→org.axonframework.messaging.core.ResourceKey
- Direction
- messaging.eventhandling.processing.streaming.pooled uses messaging.core, so a change to messaging.core can break messaging.eventhandling.processing.streaming.pooled, while a change to messaging.eventhandling.processing.streaming.pooled can't break messaging.core.
- Position
- Below the diagonal: messaging.eventhandling.processing.streaming.pooled uses a module listed above it, which is the healthy direction.
32→17 messaging.eventhandling.processing.streaming.pooled uses messaging.eventhandling.processing.streaming.token✕
- Connections
- 12 pairs of types, where a type in messaging.eventhandling.processing.streaming.pooled uses a type in messaging.eventhandling.processing.streaming.token.
- The types involved
org.axonframework.messaging.eventhandling.processing.streaming.pooled.BatchProcessingEntry→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingTokenorg.axonframework.messaging.eventhandling.processing.streaming.pooled.Builder→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingTokenorg.axonframework.messaging.eventhandling.processing.streaming.pooled.CoordinationTask→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingTokenorg.axonframework.messaging.eventhandling.processing.streaming.pooled.Coordinator→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingTokenorg.axonframework.messaging.eventhandling.processing.streaming.pooled.DefaultProcessingEntry→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingTokenorg.axonframework.messaging.eventhandling.processing.streaming.pooled.MergeTask→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingTokenorg.axonframework.messaging.eventhandling.processing.streaming.pooled.NoToken→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingTokenorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessor→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingTokenorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorConfiguration→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingTokenorg.axonframework.messaging.eventhandling.processing.streaming.pooled.ProcessingEntry→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingTokenorg.axonframework.messaging.eventhandling.processing.streaming.pooled.SegmentToken→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingTokenorg.axonframework.messaging.eventhandling.processing.streaming.pooled.WorkPackage→org.axonframework.messaging.eventhandling.processing.streaming.token.TrackingToken
- Direction
- messaging.eventhandling.processing.streaming.pooled uses messaging.eventhandling.processing.streaming.token, so a change to messaging.eventhandling.processing.streaming.token can break messaging.eventhandling.processing.streaming.pooled, while a change to messaging.eventhandling.processing.streaming.pooled can't break messaging.eventhandling.processing.streaming.token.
- Position
- Below the diagonal: messaging.eventhandling.processing.streaming.pooled uses a module listed above it, which is the healthy direction.
32→22 messaging.eventhandling.processing.streaming.pooled uses messaging.eventhandling.processing.streaming.segmenting✕
- Connections
- 20 pairs of types, where a type in messaging.eventhandling.processing.streaming.pooled uses a type in messaging.eventhandling.processing.streaming.segmenting.
- The types involved
org.axonframework.messaging.eventhandling.processing.streaming.pooled.Builder→org.axonframework.messaging.eventhandling.processing.streaming.segmenting.Segmentorg.axonframework.messaging.eventhandling.processing.streaming.pooled.Builder→org.axonframework.messaging.eventhandling.processing.streaming.segmenting.SegmentChangeListenerorg.axonframework.messaging.eventhandling.processing.streaming.pooled.Builder→org.axonframework.messaging.eventhandling.processing.streaming.segmenting.TrackerStatusorg.axonframework.messaging.eventhandling.processing.streaming.pooled.CoordinationTask→org.axonframework.messaging.eventhandling.processing.streaming.segmenting.Segmentorg.axonframework.messaging.eventhandling.processing.streaming.pooled.Coordinator→org.axonframework.messaging.eventhandling.processing.streaming.segmenting.Segmentorg.axonframework.messaging.eventhandling.processing.streaming.pooled.Coordinator→org.axonframework.messaging.eventhandling.processing.streaming.segmenting.SegmentChangeListenerorg.axonframework.messaging.eventhandling.processing.streaming.pooled.Coordinator→org.axonframework.messaging.eventhandling.processing.streaming.segmenting.TrackerStatusorg.axonframework.messaging.eventhandling.processing.streaming.pooled.DefaultProcessingEntry→org.axonframework.messaging.eventhandling.processing.streaming.segmenting.Segmentorg.axonframework.messaging.eventhandling.processing.streaming.pooled.DefaultWorkPackageEventFilter→org.axonframework.messaging.eventhandling.processing.streaming.segmenting.Segmentorg.axonframework.messaging.eventhandling.processing.streaming.pooled.EventFilter→org.axonframework.messaging.eventhandling.processing.streaming.segmenting.Segmentorg.axonframework.messaging.eventhandling.processing.streaming.pooled.MergeTask→org.axonframework.messaging.eventhandling.processing.streaming.segmenting.Segmentorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessor→org.axonframework.messaging.eventhandling.processing.streaming.segmenting.EventTrackerStatusorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessor→org.axonframework.messaging.eventhandling.processing.streaming.segmenting.Segmentorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessor→org.axonframework.messaging.eventhandling.processing.streaming.segmenting.TrackerStatusorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorConfiguration→org.axonframework.messaging.eventhandling.processing.streaming.segmenting.SegmentChangeListenerorg.axonframework.messaging.eventhandling.processing.streaming.pooled.SegmentToken→org.axonframework.messaging.eventhandling.processing.streaming.segmenting.Segmentorg.axonframework.messaging.eventhandling.processing.streaming.pooled.SplitTask→org.axonframework.messaging.eventhandling.processing.streaming.segmenting.Segmentorg.axonframework.messaging.eventhandling.processing.streaming.pooled.SplitTask→org.axonframework.messaging.eventhandling.processing.streaming.segmenting.TrackerStatusorg.axonframework.messaging.eventhandling.processing.streaming.pooled.WorkPackage→org.axonframework.messaging.eventhandling.processing.streaming.segmenting.Segmentorg.axonframework.messaging.eventhandling.processing.streaming.pooled.WorkPackage→org.axonframework.messaging.eventhandling.processing.streaming.segmenting.TrackerStatus
- Direction
- messaging.eventhandling.processing.streaming.pooled uses messaging.eventhandling.processing.streaming.segmenting, so a change to messaging.eventhandling.processing.streaming.segmenting can break messaging.eventhandling.processing.streaming.pooled, while a change to messaging.eventhandling.processing.streaming.pooled can't break messaging.eventhandling.processing.streaming.segmenting.
- Position
- Below the diagonal: messaging.eventhandling.processing.streaming.pooled uses a module listed above it, which is the healthy direction.
32→23 messaging.eventhandling.processing.streaming.pooled uses messaging.eventstreaming✕
- Connections
- 12 pairs of types, where a type in messaging.eventhandling.processing.streaming.pooled uses a type in messaging.eventstreaming.
- The types involved
org.axonframework.messaging.eventhandling.processing.streaming.pooled.Builder→org.axonframework.messaging.eventstreaming.EventCriteriaorg.axonframework.messaging.eventhandling.processing.streaming.pooled.Builder→org.axonframework.messaging.eventstreaming.StreamableEventSourceorg.axonframework.messaging.eventhandling.processing.streaming.pooled.Builder→org.axonframework.messaging.eventstreaming.TrackingTokenSourceorg.axonframework.messaging.eventhandling.processing.streaming.pooled.Coordinator→org.axonframework.messaging.eventstreaming.EventCriteriaorg.axonframework.messaging.eventhandling.processing.streaming.pooled.Coordinator→org.axonframework.messaging.eventstreaming.StreamableEventSourceorg.axonframework.messaging.eventhandling.processing.streaming.pooled.Coordinator→org.axonframework.messaging.eventstreaming.TrackingTokenSourceorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessor→org.axonframework.messaging.eventstreaming.EventCriteriaorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessor→org.axonframework.messaging.eventstreaming.StreamableEventSourceorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessor→org.axonframework.messaging.eventstreaming.TrackingTokenSourceorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorConfiguration→org.axonframework.messaging.eventstreaming.EventCriteriaorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorConfiguration→org.axonframework.messaging.eventstreaming.StreamableEventSourceorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorConfiguration→org.axonframework.messaging.eventstreaming.TrackingTokenSource
- Direction
- messaging.eventhandling.processing.streaming.pooled uses messaging.eventstreaming, so a change to messaging.eventstreaming can break messaging.eventhandling.processing.streaming.pooled, while a change to messaging.eventhandling.processing.streaming.pooled can't break messaging.eventstreaming.
- Position
- Below the diagonal: messaging.eventhandling.processing.streaming.pooled uses a module listed above it, which is the healthy direction.
32→26 messaging.eventhandling.processing.streaming.pooled uses messaging.eventhandling.processing✕
- Connections
- 2 pairs of types, where a type in messaging.eventhandling.processing.streaming.pooled uses a type in messaging.eventhandling.processing.
- The types involved
org.axonframework.messaging.eventhandling.processing.streaming.pooled.DefaultWorkPackageEventFilter→org.axonframework.messaging.eventhandling.processing.ProcessorEventHandlingComponentsorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessor→org.axonframework.messaging.eventhandling.processing.ProcessorEventHandlingComponents
- Direction
- messaging.eventhandling.processing.streaming.pooled uses messaging.eventhandling.processing, so a change to messaging.eventhandling.processing can break messaging.eventhandling.processing.streaming.pooled, while a change to messaging.eventhandling.processing.streaming.pooled can't break messaging.eventhandling.processing.
- Position
- Below the diagonal: messaging.eventhandling.processing.streaming.pooled uses a module listed above it, which is the healthy direction.
32→27 messaging.eventhandling.processing.streaming.pooled uses messaging.eventhandling.processing.streaming.token.store✕
- Connections
- 8 pairs of types, where a type in messaging.eventhandling.processing.streaming.pooled uses a type in messaging.eventhandling.processing.streaming.token.store.
- The types involved
org.axonframework.messaging.eventhandling.processing.streaming.pooled.Builder→org.axonframework.messaging.eventhandling.processing.streaming.token.store.TokenStoreorg.axonframework.messaging.eventhandling.processing.streaming.pooled.ClaimTask→org.axonframework.messaging.eventhandling.processing.streaming.token.store.TokenStoreorg.axonframework.messaging.eventhandling.processing.streaming.pooled.Coordinator→org.axonframework.messaging.eventhandling.processing.streaming.token.store.TokenStoreorg.axonframework.messaging.eventhandling.processing.streaming.pooled.MergeTask→org.axonframework.messaging.eventhandling.processing.streaming.token.store.TokenStoreorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessor→org.axonframework.messaging.eventhandling.processing.streaming.token.store.TokenStoreorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorConfiguration→org.axonframework.messaging.eventhandling.processing.streaming.token.store.TokenStoreorg.axonframework.messaging.eventhandling.processing.streaming.pooled.SplitTask→org.axonframework.messaging.eventhandling.processing.streaming.token.store.TokenStoreorg.axonframework.messaging.eventhandling.processing.streaming.pooled.WorkPackage→org.axonframework.messaging.eventhandling.processing.streaming.token.store.TokenStore
- Direction
- messaging.eventhandling.processing.streaming.pooled uses messaging.eventhandling.processing.streaming.token.store, so a change to messaging.eventhandling.processing.streaming.token.store can break messaging.eventhandling.processing.streaming.pooled, while a change to messaging.eventhandling.processing.streaming.pooled can't break messaging.eventhandling.processing.streaming.token.store.
- Position
- Below the diagonal: messaging.eventhandling.processing.streaming.pooled uses a module listed above it, which is the healthy direction.
32→37 messaging.eventhandling.processing.streaming.pooled uses messaging.eventhandling.configuration part of a loop✕
- Connections
- 11 pairs of types, where a type in messaging.eventhandling.processing.streaming.pooled uses a type in messaging.eventhandling.configuration.
- The types involved
org.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorConfiguration→org.axonframework.messaging.eventhandling.configuration.EventProcessorConfigurationorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorModule→org.axonframework.messaging.eventhandling.configuration.CompletePhaseorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorModule→org.axonframework.messaging.eventhandling.configuration.CustomizationPhaseorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorModule→org.axonframework.messaging.eventhandling.configuration.EventHandlingPhaseorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorModule→org.axonframework.messaging.eventhandling.configuration.EventProcessorCustomizationorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorModule→org.axonframework.messaging.eventhandling.configuration.EventProcessorModuleorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorModule→org.axonframework.messaging.eventhandling.configuration.RequiredComponentPhaseorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorsConfigurer→org.axonframework.messaging.eventhandling.configuration.CompletePhaseorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorsConfigurer→org.axonframework.messaging.eventhandling.configuration.EventHandlingPhaseorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorsConfigurer→org.axonframework.messaging.eventhandling.configuration.EventProcessingConfigurerorg.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorsConfigurer→org.axonframework.messaging.eventhandling.configuration.RequiredComponentPhase
- Direction
- messaging.eventhandling.processing.streaming.pooled uses messaging.eventhandling.configuration, so a change to messaging.eventhandling.configuration can break messaging.eventhandling.processing.streaming.pooled, while a change to messaging.eventhandling.processing.streaming.pooled can't break messaging.eventhandling.configuration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→1 messaging.eventhandling.processing.subscribing uses common✕
- Connections
- 1 pair of types, where a type in messaging.eventhandling.processing.subscribing uses a type in common.
- The types involved
org.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessor→org.axonframework.common.Registration
- Direction
- messaging.eventhandling.processing.subscribing uses common, so a change to common can break messaging.eventhandling.processing.subscribing, while a change to messaging.eventhandling.processing.subscribing can't break common.
- Position
- Below the diagonal: messaging.eventhandling.processing.subscribing uses a module listed above it, which is the healthy direction.
33→3 messaging.eventhandling.processing.subscribing uses common.infra✕
- Connections
- 2 pairs of types, where a type in messaging.eventhandling.processing.subscribing uses a type in common.infra.
- The types involved
org.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessor→org.axonframework.common.infra.ComponentDescriptororg.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessorConfiguration→org.axonframework.common.infra.ComponentDescriptor
- Direction
- messaging.eventhandling.processing.subscribing uses common.infra, so a change to common.infra can break messaging.eventhandling.processing.subscribing, while a change to messaging.eventhandling.processing.subscribing can't break common.infra.
- Position
- Below the diagonal: messaging.eventhandling.processing.subscribing uses a module listed above it, which is the healthy direction.
33→5 messaging.eventhandling.processing.subscribing uses common.configuration✕
- Connections
- 8 pairs of types, where a type in messaging.eventhandling.processing.subscribing uses a type in common.configuration.
- The types involved
org.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessorConfiguration→org.axonframework.common.configuration.Configurationorg.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessorModule→org.axonframework.common.configuration.BaseModuleorg.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessorModule→org.axonframework.common.configuration.ComponentBuilderorg.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessorModule→org.axonframework.common.configuration.Configurationorg.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessorModule→org.axonframework.common.configuration.ModuleBuilderorg.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessorsConfigurer→org.axonframework.common.configuration.ComponentRegistryorg.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessorsConfigurer→org.axonframework.common.configuration.Configurationorg.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessorsConfigurer→org.axonframework.common.configuration.ModuleBuilder
- Direction
- messaging.eventhandling.processing.subscribing uses common.configuration, so a change to common.configuration can break messaging.eventhandling.processing.subscribing, while a change to messaging.eventhandling.processing.subscribing can't break common.configuration.
- Position
- Below the diagonal: messaging.eventhandling.processing.subscribing uses a module listed above it, which is the healthy direction.
33→7 messaging.eventhandling.processing.subscribing uses messaging.core.unitofwork✕
- Connections
- 2 pairs of types, where a type in messaging.eventhandling.processing.subscribing uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessor→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessorConfiguration→org.axonframework.messaging.core.unitofwork.UnitOfWorkFactory
- Direction
- messaging.eventhandling.processing.subscribing uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break messaging.eventhandling.processing.subscribing, while a change to messaging.eventhandling.processing.subscribing can't break messaging.core.unitofwork.
- Position
- Below the diagonal: messaging.eventhandling.processing.subscribing uses a module listed above it, which is the healthy direction.
33→11 messaging.eventhandling.processing.subscribing uses messaging.eventhandling✕
- Connections
- 4 pairs of types, where a type in messaging.eventhandling.processing.subscribing uses a type in messaging.eventhandling.
- The types involved
org.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessor→org.axonframework.messaging.eventhandling.EventHandlingComponentorg.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessor→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessorConfiguration→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessorModule→org.axonframework.messaging.eventhandling.EventHandlingComponent
- Direction
- messaging.eventhandling.processing.subscribing uses messaging.eventhandling, so a change to messaging.eventhandling can break messaging.eventhandling.processing.subscribing, while a change to messaging.eventhandling.processing.subscribing can't break messaging.eventhandling.
- Position
- Below the diagonal: messaging.eventhandling.processing.subscribing uses a module listed above it, which is the healthy direction.
33→15 messaging.eventhandling.processing.subscribing uses messaging.core✕
- Connections
- 5 pairs of types, where a type in messaging.eventhandling.processing.subscribing uses a type in messaging.core.
- The types involved
org.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessor→org.axonframework.messaging.core.Emptyorg.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessor→org.axonframework.messaging.core.Messageorg.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessor→org.axonframework.messaging.core.SubscribableEventSourceorg.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessorConfiguration→org.axonframework.messaging.core.MessageHandlerInterceptororg.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessorConfiguration→org.axonframework.messaging.core.SubscribableEventSource
- Direction
- messaging.eventhandling.processing.subscribing uses messaging.core, so a change to messaging.core can break messaging.eventhandling.processing.subscribing, while a change to messaging.eventhandling.processing.subscribing can't break messaging.core.
- Position
- Below the diagonal: messaging.eventhandling.processing.subscribing uses a module listed above it, which is the healthy direction.
33→26 messaging.eventhandling.processing.subscribing uses messaging.eventhandling.processing✕
- Connections
- 2 pairs of types, where a type in messaging.eventhandling.processing.subscribing uses a type in messaging.eventhandling.processing.
- The types involved
org.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessor→org.axonframework.messaging.eventhandling.processing.EventProcessororg.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessor→org.axonframework.messaging.eventhandling.processing.ProcessorEventHandlingComponents
- Direction
- messaging.eventhandling.processing.subscribing uses messaging.eventhandling.processing, so a change to messaging.eventhandling.processing can break messaging.eventhandling.processing.subscribing, while a change to messaging.eventhandling.processing.subscribing can't break messaging.eventhandling.processing.
- Position
- Below the diagonal: messaging.eventhandling.processing.subscribing uses a module listed above it, which is the healthy direction.
33→37 messaging.eventhandling.processing.subscribing uses messaging.eventhandling.configuration part of a loop✕
- Connections
- 11 pairs of types, where a type in messaging.eventhandling.processing.subscribing uses a type in messaging.eventhandling.configuration.
- The types involved
org.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessorConfiguration→org.axonframework.messaging.eventhandling.configuration.EventProcessorConfigurationorg.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessorModule→org.axonframework.messaging.eventhandling.configuration.CompletePhaseorg.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessorModule→org.axonframework.messaging.eventhandling.configuration.CustomizationPhaseorg.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessorModule→org.axonframework.messaging.eventhandling.configuration.EventHandlingPhaseorg.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessorModule→org.axonframework.messaging.eventhandling.configuration.EventProcessorCustomizationorg.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessorModule→org.axonframework.messaging.eventhandling.configuration.EventProcessorModuleorg.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessorModule→org.axonframework.messaging.eventhandling.configuration.RequiredComponentPhaseorg.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessorsConfigurer→org.axonframework.messaging.eventhandling.configuration.CompletePhaseorg.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessorsConfigurer→org.axonframework.messaging.eventhandling.configuration.EventHandlingPhaseorg.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessorsConfigurer→org.axonframework.messaging.eventhandling.configuration.EventProcessingConfigurerorg.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessorsConfigurer→org.axonframework.messaging.eventhandling.configuration.RequiredComponentPhase
- Direction
- messaging.eventhandling.processing.subscribing uses messaging.eventhandling.configuration, so a change to messaging.eventhandling.configuration can break messaging.eventhandling.processing.subscribing, while a change to messaging.eventhandling.processing.subscribing can't break messaging.eventhandling.configuration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
34→5 modelling.annotation uses common.configuration✕
- Connections
- 6 pairs of types, where a type in modelling.annotation uses a type in common.configuration.
- The types involved
org.axonframework.modelling.annotation.AnnotationBasedEntityIdResolverDefinition→org.axonframework.common.configuration.Configurationorg.axonframework.modelling.annotation.EntityIdResolverDefinition→org.axonframework.common.configuration.Configurationorg.axonframework.modelling.annotation.InjectEntityParameterResolver→org.axonframework.common.configuration.Configurationorg.axonframework.modelling.annotation.InjectEntityParameterResolverFactory→org.axonframework.common.configuration.Configurationorg.axonframework.modelling.annotation.InjectEntityParameterResolverFactoryConfigurationEnhancer→org.axonframework.common.configuration.ComponentRegistryorg.axonframework.modelling.annotation.InjectEntityParameterResolverFactoryConfigurationEnhancer→org.axonframework.common.configuration.ConfigurationEnhancer
- Direction
- modelling.annotation uses common.configuration, so a change to common.configuration can break modelling.annotation, while a change to modelling.annotation can't break common.configuration.
- Position
- Below the diagonal: modelling.annotation uses a module listed above it, which is the healthy direction.
34→7 modelling.annotation uses messaging.core.unitofwork✕
- Connections
- 3 pairs of types, where a type in modelling.annotation uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.modelling.annotation.AnnotationBasedEntityEvolvingComponent→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.modelling.annotation.AnnotationBasedEntityIdResolver→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.modelling.annotation.InjectEntityParameterResolver→org.axonframework.messaging.core.unitofwork.ProcessingContext
- Direction
- modelling.annotation uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break modelling.annotation, while a change to modelling.annotation can't break messaging.core.unitofwork.
- Position
- Below the diagonal: modelling.annotation uses a module listed above it, which is the healthy direction.
34→11 modelling.annotation uses messaging.eventhandling✕
- Connections
- 1 pair of types, where a type in modelling.annotation uses a type in messaging.eventhandling.
- The types involved
org.axonframework.modelling.annotation.AnnotationBasedEntityEvolvingComponent→org.axonframework.messaging.eventhandling.EventMessage
- Direction
- modelling.annotation uses messaging.eventhandling, so a change to messaging.eventhandling can break modelling.annotation, while a change to modelling.annotation can't break messaging.eventhandling.
- Position
- Below the diagonal: modelling.annotation uses a module listed above it, which is the healthy direction.
34→12 modelling.annotation uses messaging.eventhandling.conversion✕
- Connections
- 1 pair of types, where a type in modelling.annotation uses a type in messaging.eventhandling.conversion.
- The types involved
org.axonframework.modelling.annotation.AnnotationBasedEntityEvolvingComponent→org.axonframework.messaging.eventhandling.conversion.EventConverter
- Direction
- modelling.annotation uses messaging.eventhandling.conversion, so a change to messaging.eventhandling.conversion can break modelling.annotation, while a change to modelling.annotation can't break messaging.eventhandling.conversion.
- Position
- Below the diagonal: modelling.annotation uses a module listed above it, which is the healthy direction.
34→14 modelling.annotation uses messaging.core.annotation✕
- Connections
- 7 pairs of types, where a type in modelling.annotation uses a type in messaging.core.annotation.
- The types involved
org.axonframework.modelling.annotation.AnnotationBasedEntityEvolvingComponent→org.axonframework.messaging.core.annotation.AnnotatedHandlerInspectororg.axonframework.modelling.annotation.AnnotationBasedEntityEvolvingComponent→org.axonframework.messaging.core.annotation.HandlerDefinitionorg.axonframework.modelling.annotation.AnnotationBasedEntityEvolvingComponent→org.axonframework.messaging.core.annotation.MessageHandlingMemberorg.axonframework.modelling.annotation.AnnotationBasedEntityEvolvingComponent→org.axonframework.messaging.core.annotation.ParameterResolverFactoryorg.axonframework.modelling.annotation.InjectEntityParameterResolver→org.axonframework.messaging.core.annotation.ParameterResolverorg.axonframework.modelling.annotation.InjectEntityParameterResolverFactory→org.axonframework.messaging.core.annotation.ParameterResolverorg.axonframework.modelling.annotation.InjectEntityParameterResolverFactory→org.axonframework.messaging.core.annotation.ParameterResolverFactory
- Direction
- modelling.annotation uses messaging.core.annotation, so a change to messaging.core.annotation can break modelling.annotation, while a change to modelling.annotation can't break messaging.core.annotation.
- Position
- Below the diagonal: modelling.annotation uses a module listed above it, which is the healthy direction.
34→15 modelling.annotation uses messaging.core✕
- Connections
- 4 pairs of types, where a type in modelling.annotation uses a type in messaging.core.
- The types involved
org.axonframework.modelling.annotation.AnnotationBasedEntityEvolvingComponent→org.axonframework.messaging.core.Entryorg.axonframework.modelling.annotation.AnnotationBasedEntityEvolvingComponent→org.axonframework.messaging.core.MessageTypeResolverorg.axonframework.modelling.annotation.AnnotationBasedEntityEvolvingComponent→org.axonframework.messaging.core.QualifiedNameorg.axonframework.modelling.annotation.AnnotationBasedEntityIdResolver→org.axonframework.messaging.core.Message
- Direction
- modelling.annotation uses messaging.core, so a change to messaging.core can break modelling.annotation, while a change to modelling.annotation can't break messaging.core.
- Position
- Below the diagonal: modelling.annotation uses a module listed above it, which is the healthy direction.
34→24 modelling.annotation uses modelling✕
- Connections
- 8 pairs of types, where a type in modelling.annotation uses a type in modelling.
- The types involved
org.axonframework.modelling.annotation.AnnotationBasedEntityEvolvingComponent→org.axonframework.modelling.EntityEvolvingComponentorg.axonframework.modelling.annotation.AnnotationBasedEntityIdResolver→org.axonframework.modelling.EntityIdResolverorg.axonframework.modelling.annotation.AnnotationBasedEntityIdResolverDefinition→org.axonframework.modelling.EntityIdResolverorg.axonframework.modelling.annotation.EntityIdResolverDefinition→org.axonframework.modelling.EntityIdResolverorg.axonframework.modelling.annotation.InjectEntity→org.axonframework.modelling.EntityIdResolverorg.axonframework.modelling.annotation.InjectEntityParameterResolver→org.axonframework.modelling.EntityIdResolverorg.axonframework.modelling.annotation.InjectEntityParameterResolver→org.axonframework.modelling.StateManagerorg.axonframework.modelling.annotation.InjectEntityParameterResolverFactory→org.axonframework.modelling.EntityIdResolver
- Direction
- modelling.annotation uses modelling, so a change to modelling can break modelling.annotation, while a change to modelling.annotation can't break modelling.
- Position
- Below the diagonal: modelling.annotation uses a module listed above it, which is the healthy direction.
34→28 modelling.annotation uses modelling.entity✕
- Connections
- 2 pairs of types, where a type in modelling.annotation uses a type in modelling.entity.
- The types involved
org.axonframework.modelling.annotation.AnnotationBasedEntityIdResolverDefinition→org.axonframework.modelling.entity.EntityMetamodelorg.axonframework.modelling.annotation.EntityIdResolverDefinition→org.axonframework.modelling.entity.EntityMetamodel
- Direction
- modelling.annotation uses modelling.entity, so a change to modelling.entity can break modelling.annotation, while a change to modelling.annotation can't break modelling.entity.
- Position
- Below the diagonal: modelling.annotation uses a module listed above it, which is the healthy direction.
35→3 eventsourcing uses common.infra✕
- Connections
- 1 pair of types, where a type in eventsourcing uses a type in common.infra.
- The types involved
org.axonframework.eventsourcing.EventSourcingRepository→org.axonframework.common.infra.ComponentDescriptor
- Direction
- eventsourcing uses common.infra, so a change to common.infra can break eventsourcing, while a change to eventsourcing can't break common.infra.
- Position
- Below the diagonal: eventsourcing uses a module listed above it, which is the healthy direction.
35→7 eventsourcing uses messaging.core.unitofwork✕
- Connections
- 3 pairs of types, where a type in eventsourcing uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.eventsourcing.CriteriaResolver→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.eventsourcing.EventSourcedEntityFactory→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.eventsourcing.EventSourcingRepository→org.axonframework.messaging.core.unitofwork.ProcessingContext
- Direction
- eventsourcing uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break eventsourcing, while a change to eventsourcing can't break messaging.core.unitofwork.
- Position
- Below the diagonal: eventsourcing uses a module listed above it, which is the healthy direction.
35→11 eventsourcing uses messaging.eventhandling✕
- Connections
- 1 pair of types, where a type in eventsourcing uses a type in messaging.eventhandling.
- The types involved
org.axonframework.eventsourcing.EventSourcedEntityFactory→org.axonframework.messaging.eventhandling.EventMessage
- Direction
- eventsourcing uses messaging.eventhandling, so a change to messaging.eventhandling can break eventsourcing, while a change to eventsourcing can't break messaging.eventhandling.
- Position
- Below the diagonal: eventsourcing uses a module listed above it, which is the healthy direction.
35→15 eventsourcing uses messaging.core✕
- Connections
- 1 pair of types, where a type in eventsourcing uses a type in messaging.core.
- The types involved
org.axonframework.eventsourcing.EventSourcingRepository→org.axonframework.messaging.core.ResourceKey
- Direction
- eventsourcing uses messaging.core, so a change to messaging.core can break eventsourcing, while a change to eventsourcing can't break messaging.core.
- Position
- Below the diagonal: eventsourcing uses a module listed above it, which is the healthy direction.
35→20 eventsourcing uses modelling.repository✕
- Connections
- 3 pairs of types, where a type in eventsourcing uses a type in modelling.repository.
- The types involved
org.axonframework.eventsourcing.EventSourcedEntity→org.axonframework.modelling.repository.ManagedEntityorg.axonframework.eventsourcing.EventSourcingRepository→org.axonframework.modelling.repository.LifecycleManagementorg.axonframework.eventsourcing.EventSourcingRepository→org.axonframework.modelling.repository.ManagedEntity
- Direction
- eventsourcing uses modelling.repository, so a change to modelling.repository can break eventsourcing, while a change to eventsourcing can't break modelling.repository.
- Position
- Below the diagonal: eventsourcing uses a module listed above it, which is the healthy direction.
35→23 eventsourcing uses messaging.eventstreaming✕
- Connections
- 1 pair of types, where a type in eventsourcing uses a type in messaging.eventstreaming.
- The types involved
org.axonframework.eventsourcing.CriteriaResolver→org.axonframework.messaging.eventstreaming.EventCriteria
- Direction
- eventsourcing uses messaging.eventstreaming, so a change to messaging.eventstreaming can break eventsourcing, while a change to eventsourcing can't break messaging.eventstreaming.
- Position
- Below the diagonal: eventsourcing uses a module listed above it, which is the healthy direction.
35→24 eventsourcing uses modelling✕
- Connections
- 1 pair of types, where a type in eventsourcing uses a type in modelling.
- The types involved
org.axonframework.eventsourcing.EventSourcingRepository→org.axonframework.modelling.EntityEvolver
- Direction
- eventsourcing uses modelling, so a change to modelling can break eventsourcing, while a change to eventsourcing can't break modelling.
- Position
- Below the diagonal: eventsourcing uses a module listed above it, which is the healthy direction.
35→25 eventsourcing uses eventsourcing.eventstore✕
- Connections
- 1 pair of types, where a type in eventsourcing uses a type in eventsourcing.eventstore.
- The types involved
org.axonframework.eventsourcing.EventSourcingRepository→org.axonframework.eventsourcing.eventstore.EventStore
- Direction
- eventsourcing uses eventsourcing.eventstore, so a change to eventsourcing.eventstore can break eventsourcing, while a change to eventsourcing can't break eventsourcing.eventstore.
- Position
- Below the diagonal: eventsourcing uses a module listed above it, which is the healthy direction.
35→31 eventsourcing uses eventsourcing.handler✕
- Connections
- 1 pair of types, where a type in eventsourcing uses a type in eventsourcing.handler.
- The types involved
org.axonframework.eventsourcing.EventSourcingRepository→org.axonframework.eventsourcing.handler.EntityLifecycleHandler
- Direction
- eventsourcing uses eventsourcing.handler, so a change to eventsourcing.handler can break eventsourcing, while a change to eventsourcing can't break eventsourcing.handler.
- Position
- Below the diagonal: eventsourcing uses a module listed above it, which is the healthy direction.
36→4 extension.springboot.autoconfig uses messaging.core.unitofwork.transaction✕
- Connections
- 3 pairs of types, where a type in extension.springboot.autoconfig uses a type in messaging.core.unitofwork.transaction.
- The types involved
org.axonframework.extension.springboot.autoconfig.JdbcTransactionAutoConfiguration→org.axonframework.messaging.core.unitofwork.transaction.TransactionManagerorg.axonframework.extension.springboot.autoconfig.JpaTransactionAutoConfiguration→org.axonframework.messaging.core.unitofwork.transaction.TransactionManagerorg.axonframework.extension.springboot.autoconfig.NoOpTransactionAutoConfiguration→org.axonframework.messaging.core.unitofwork.transaction.TransactionManager
- Direction
- extension.springboot.autoconfig uses messaging.core.unitofwork.transaction, so a change to messaging.core.unitofwork.transaction can break extension.springboot.autoconfig, while a change to extension.springboot.autoconfig can't break messaging.core.unitofwork.transaction.
- Position
- Below the diagonal: extension.springboot.autoconfig uses a module listed above it, which is the healthy direction.
36→5 extension.springboot.autoconfig uses common.configuration✕
- Connections
- 12 pairs of types, where a type in extension.springboot.autoconfig uses a type in common.configuration.
- The types involved
org.axonframework.extension.springboot.autoconfig.1→org.axonframework.common.configuration.ComponentRegistryorg.axonframework.extension.springboot.autoconfig.1→org.axonframework.common.configuration.ConfigurationEnhancerorg.axonframework.extension.springboot.autoconfig.AggregateBasedJpaEventStorageEngineConfigurationEnhancer→org.axonframework.common.configuration.ComponentRegistryorg.axonframework.extension.springboot.autoconfig.AggregateBasedJpaEventStorageEngineConfigurationEnhancer→org.axonframework.common.configuration.ConfigurationEnhancerorg.axonframework.extension.springboot.autoconfig.AxonAutoConfiguration→org.axonframework.common.configuration.AxonConfigurationorg.axonframework.extension.springboot.autoconfig.AxonAutoConfiguration→org.axonframework.common.configuration.Configurationorg.axonframework.extension.springboot.autoconfig.CorrelationDataProviderAutoConfiguration→org.axonframework.common.configuration.DecoratorDefinitionorg.axonframework.extension.springboot.autoconfig.InterceptorAutoConfiguration→org.axonframework.common.configuration.DecoratorDefinitionorg.axonframework.extension.springboot.autoconfig.JpaEventStoreAutoConfiguration→org.axonframework.common.configuration.ConfigurationEnhancerorg.axonframework.extension.springboot.autoconfig.ReactorAutoConfiguration→org.axonframework.common.configuration.DecoratorDefinitionorg.axonframework.extension.springboot.autoconfig.TracingAutoConfiguration→org.axonframework.common.configuration.ConfigurationEnhancerorg.axonframework.extension.springboot.autoconfig.UpdateCheckerAutoConfiguration→org.axonframework.common.configuration.ConfigurationEnhancer
- Direction
- extension.springboot.autoconfig uses common.configuration, so a change to common.configuration can break extension.springboot.autoconfig, while a change to extension.springboot.autoconfig can't break common.configuration.
- Position
- Below the diagonal: extension.springboot.autoconfig uses a module listed above it, which is the healthy direction.
36→6 extension.springboot.autoconfig uses conversion✕
- Connections
- 11 pairs of types, where a type in extension.springboot.autoconfig uses a type in conversion.
- The types involved
org.axonframework.extension.springboot.autoconfig.AvroConverterAutoConfiguration→org.axonframework.conversion.Converterorg.axonframework.extension.springboot.autoconfig.AvroConverterAutoConfiguration→org.axonframework.conversion.GeneralConverterorg.axonframework.extension.springboot.autoconfig.CBORConverterAutoConfiguration→org.axonframework.conversion.Converterorg.axonframework.extension.springboot.autoconfig.CBORConverterAutoConfiguration→org.axonframework.conversion.GeneralConverterorg.axonframework.extension.springboot.autoconfig.ConverterAutoConfiguration→org.axonframework.conversion.GeneralConverterorg.axonframework.extension.springboot.autoconfig.Jackson2ConverterAutoConfiguration→org.axonframework.conversion.Converterorg.axonframework.extension.springboot.autoconfig.Jackson2ConverterAutoConfiguration→org.axonframework.conversion.GeneralConverterorg.axonframework.extension.springboot.autoconfig.JacksonConverterAutoConfiguration→org.axonframework.conversion.Converterorg.axonframework.extension.springboot.autoconfig.JacksonConverterAutoConfiguration→org.axonframework.conversion.GeneralConverterorg.axonframework.extension.springboot.autoconfig.JdbcAutoConfiguration→org.axonframework.conversion.GeneralConverterorg.axonframework.extension.springboot.autoconfig.JpaAutoConfiguration→org.axonframework.conversion.GeneralConverter
- Direction
- extension.springboot.autoconfig uses conversion, so a change to conversion can break extension.springboot.autoconfig, while a change to extension.springboot.autoconfig can't break conversion.
- Position
- Below the diagonal: extension.springboot.autoconfig uses a module listed above it, which is the healthy direction.
36→8 extension.springboot.autoconfig uses messaging.commandhandling✕
- Connections
- 2 pairs of types, where a type in extension.springboot.autoconfig uses a type in messaging.commandhandling.
- The types involved
org.axonframework.extension.springboot.autoconfig.InterceptorAutoConfiguration→org.axonframework.messaging.commandhandling.CommandMessageorg.axonframework.extension.springboot.autoconfig.ReactorAutoConfiguration→org.axonframework.messaging.commandhandling.CommandMessage
- Direction
- extension.springboot.autoconfig uses messaging.commandhandling, so a change to messaging.commandhandling can break extension.springboot.autoconfig, while a change to extension.springboot.autoconfig can't break messaging.commandhandling.
- Position
- Below the diagonal: extension.springboot.autoconfig uses a module listed above it, which is the healthy direction.
36→9 extension.springboot.autoconfig uses messaging.core.conversion✕
- Connections
- 5 pairs of types, where a type in extension.springboot.autoconfig uses a type in messaging.core.conversion.
- The types involved
org.axonframework.extension.springboot.autoconfig.AvroConverterAutoConfiguration→org.axonframework.messaging.core.conversion.MessageConverterorg.axonframework.extension.springboot.autoconfig.CBORConverterAutoConfiguration→org.axonframework.messaging.core.conversion.MessageConverterorg.axonframework.extension.springboot.autoconfig.ConverterAutoConfiguration→org.axonframework.messaging.core.conversion.MessageConverterorg.axonframework.extension.springboot.autoconfig.Jackson2ConverterAutoConfiguration→org.axonframework.messaging.core.conversion.MessageConverterorg.axonframework.extension.springboot.autoconfig.JacksonConverterAutoConfiguration→org.axonframework.messaging.core.conversion.MessageConverter
- Direction
- extension.springboot.autoconfig uses messaging.core.conversion, so a change to messaging.core.conversion can break extension.springboot.autoconfig, while a change to extension.springboot.autoconfig can't break messaging.core.conversion.
- Position
- Below the diagonal: extension.springboot.autoconfig uses a module listed above it, which is the healthy direction.
36→11 extension.springboot.autoconfig uses messaging.eventhandling✕
- Connections
- 2 pairs of types, where a type in extension.springboot.autoconfig uses a type in messaging.eventhandling.
- The types involved
org.axonframework.extension.springboot.autoconfig.InterceptorAutoConfiguration→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.extension.springboot.autoconfig.ReactorAutoConfiguration→org.axonframework.messaging.eventhandling.EventMessage
- Direction
- extension.springboot.autoconfig uses messaging.eventhandling, so a change to messaging.eventhandling can break extension.springboot.autoconfig, while a change to extension.springboot.autoconfig can't break messaging.eventhandling.
- Position
- Below the diagonal: extension.springboot.autoconfig uses a module listed above it, which is the healthy direction.
36→12 extension.springboot.autoconfig uses messaging.eventhandling.conversion✕
- Connections
- 5 pairs of types, where a type in extension.springboot.autoconfig uses a type in messaging.eventhandling.conversion.
- The types involved
org.axonframework.extension.springboot.autoconfig.AvroConverterAutoConfiguration→org.axonframework.messaging.eventhandling.conversion.EventConverterorg.axonframework.extension.springboot.autoconfig.CBORConverterAutoConfiguration→org.axonframework.messaging.eventhandling.conversion.EventConverterorg.axonframework.extension.springboot.autoconfig.ConverterAutoConfiguration→org.axonframework.messaging.eventhandling.conversion.EventConverterorg.axonframework.extension.springboot.autoconfig.Jackson2ConverterAutoConfiguration→org.axonframework.messaging.eventhandling.conversion.EventConverterorg.axonframework.extension.springboot.autoconfig.JacksonConverterAutoConfiguration→org.axonframework.messaging.eventhandling.conversion.EventConverter
- Direction
- extension.springboot.autoconfig uses messaging.eventhandling.conversion, so a change to messaging.eventhandling.conversion can break extension.springboot.autoconfig, while a change to extension.springboot.autoconfig can't break messaging.eventhandling.conversion.
- Position
- Below the diagonal: extension.springboot.autoconfig uses a module listed above it, which is the healthy direction.
36→14 extension.springboot.autoconfig uses messaging.core.annotation✕
- Connections
- 4 pairs of types, where a type in extension.springboot.autoconfig uses a type in messaging.core.annotation.
- The types involved
org.axonframework.extension.springboot.autoconfig.AxonAutoConfiguration→org.axonframework.messaging.core.annotation.HandlerDefinitionorg.axonframework.extension.springboot.autoconfig.AxonAutoConfiguration→org.axonframework.messaging.core.annotation.HandlerEnhancerDefinitionorg.axonframework.extension.springboot.autoconfig.AxonAutoConfiguration→org.axonframework.messaging.core.annotation.ParameterResolverFactoryorg.axonframework.extension.springboot.autoconfig.SecurityAutoConfiguration→org.axonframework.messaging.core.annotation.HandlerEnhancerDefinition
- Direction
- extension.springboot.autoconfig uses messaging.core.annotation, so a change to messaging.core.annotation can break extension.springboot.autoconfig, while a change to extension.springboot.autoconfig can't break messaging.core.annotation.
- Position
- Below the diagonal: extension.springboot.autoconfig uses a module listed above it, which is the healthy direction.
36→15 extension.springboot.autoconfig uses messaging.core✕
- Connections
- 3 pairs of types, where a type in extension.springboot.autoconfig uses a type in messaging.core.
- The types involved
org.axonframework.extension.springboot.autoconfig.InterceptorAutoConfiguration→org.axonframework.messaging.core.Messageorg.axonframework.extension.springboot.autoconfig.InterceptorAutoConfiguration→org.axonframework.messaging.core.MessageDispatchInterceptororg.axonframework.extension.springboot.autoconfig.InterceptorAutoConfiguration→org.axonframework.messaging.core.MessageHandlerInterceptor
- Direction
- extension.springboot.autoconfig uses messaging.core, so a change to messaging.core can break extension.springboot.autoconfig, while a change to extension.springboot.autoconfig can't break messaging.core.
- Position
- Below the diagonal: extension.springboot.autoconfig uses a module listed above it, which is the healthy direction.
36→18 extension.springboot.autoconfig uses messaging.queryhandling✕
- Connections
- 4 pairs of types, where a type in extension.springboot.autoconfig uses a type in messaging.queryhandling.
- The types involved
org.axonframework.extension.springboot.autoconfig.InterceptorAutoConfiguration→org.axonframework.messaging.queryhandling.QueryMessageorg.axonframework.extension.springboot.autoconfig.QueryShutdownAutoConfiguration→org.axonframework.messaging.queryhandling.QueryShutdownManagerorg.axonframework.extension.springboot.autoconfig.QueryShutdownManagerLifecycle→org.axonframework.messaging.queryhandling.QueryShutdownManagerorg.axonframework.extension.springboot.autoconfig.ReactorAutoConfiguration→org.axonframework.messaging.queryhandling.QueryMessage
- Direction
- extension.springboot.autoconfig uses messaging.queryhandling, so a change to messaging.queryhandling can break extension.springboot.autoconfig, while a change to extension.springboot.autoconfig can't break messaging.queryhandling.
- Position
- Below the diagonal: extension.springboot.autoconfig uses a module listed above it, which is the healthy direction.
36→19 extension.springboot.autoconfig uses messaging.tracing✕
- Connections
- 1 pair of types, where a type in extension.springboot.autoconfig uses a type in messaging.tracing.
- The types involved
org.axonframework.extension.springboot.autoconfig.TracingAutoConfiguration→org.axonframework.messaging.tracing.SpanAttributesProvider
- Direction
- extension.springboot.autoconfig uses messaging.tracing, so a change to messaging.tracing can break extension.springboot.autoconfig, while a change to extension.springboot.autoconfig can't break messaging.tracing.
- Position
- Below the diagonal: extension.springboot.autoconfig uses a module listed above it, which is the healthy direction.
36→21 extension.springboot.autoconfig uses messaging.core.interception✕
- Connections
- 2 pairs of types, where a type in extension.springboot.autoconfig uses a type in messaging.core.interception.
- The types involved
org.axonframework.extension.springboot.autoconfig.InterceptorAutoConfiguration→org.axonframework.messaging.core.interception.DispatchInterceptorRegistryorg.axonframework.extension.springboot.autoconfig.InterceptorAutoConfiguration→org.axonframework.messaging.core.interception.HandlerInterceptorRegistry
- Direction
- extension.springboot.autoconfig uses messaging.core.interception, so a change to messaging.core.interception can break extension.springboot.autoconfig, while a change to extension.springboot.autoconfig can't break messaging.core.interception.
- Position
- Below the diagonal: extension.springboot.autoconfig uses a module listed above it, which is the healthy direction.
36→27 extension.springboot.autoconfig uses messaging.eventhandling.processing.streaming.token.store✕
- Connections
- 2 pairs of types, where a type in extension.springboot.autoconfig uses a type in messaging.eventhandling.processing.streaming.token.store.
- The types involved
org.axonframework.extension.springboot.autoconfig.JdbcAutoConfiguration→org.axonframework.messaging.eventhandling.processing.streaming.token.store.TokenStoreorg.axonframework.extension.springboot.autoconfig.JpaAutoConfiguration→org.axonframework.messaging.eventhandling.processing.streaming.token.store.TokenStore
- Direction
- extension.springboot.autoconfig uses messaging.eventhandling.processing.streaming.token.store, so a change to messaging.eventhandling.processing.streaming.token.store can break extension.springboot.autoconfig, while a change to extension.springboot.autoconfig can't break messaging.eventhandling.processing.streaming.token.store.
- Position
- Below the diagonal: extension.springboot.autoconfig uses a module listed above it, which is the healthy direction.
36→32 extension.springboot.autoconfig uses messaging.eventhandling.processing.streaming.pooled✕
- Connections
- 1 pair of types, where a type in extension.springboot.autoconfig uses a type in messaging.eventhandling.processing.streaming.pooled.
- The types involved
org.axonframework.extension.springboot.autoconfig.EventProcessingAutoConfiguration→org.axonframework.messaging.eventhandling.processing.streaming.pooled.Customization
- Direction
- extension.springboot.autoconfig uses messaging.eventhandling.processing.streaming.pooled, so a change to messaging.eventhandling.processing.streaming.pooled can break extension.springboot.autoconfig, while a change to extension.springboot.autoconfig can't break messaging.eventhandling.processing.streaming.pooled.
- Position
- Below the diagonal: extension.springboot.autoconfig uses a module listed above it, which is the healthy direction.
37→3 messaging.eventhandling.configuration uses common.infra✕
- Connections
- 2 pairs of types, where a type in messaging.eventhandling.configuration uses a type in common.infra.
- The types involved
org.axonframework.messaging.eventhandling.configuration.EventProcessorConfiguration→org.axonframework.common.infra.ComponentDescriptororg.axonframework.messaging.eventhandling.configuration.EventProcessorConfiguration→org.axonframework.common.infra.DescribableComponent
- Direction
- messaging.eventhandling.configuration uses common.infra, so a change to common.infra can break messaging.eventhandling.configuration, while a change to messaging.eventhandling.configuration can't break common.infra.
- Position
- Below the diagonal: messaging.eventhandling.configuration uses a module listed above it, which is the healthy direction.
37→5 messaging.eventhandling.configuration uses common.configuration✕
- Connections
- 17 pairs of types, where a type in messaging.eventhandling.configuration uses a type in common.configuration.
- The types involved
org.axonframework.messaging.eventhandling.configuration.CompletePhase→org.axonframework.common.configuration.ComponentBuilderorg.axonframework.messaging.eventhandling.configuration.CompletePhase→org.axonframework.common.configuration.Configurationorg.axonframework.messaging.eventhandling.configuration.ComponentsPhase→org.axonframework.common.configuration.ComponentBuilderorg.axonframework.messaging.eventhandling.configuration.CustomizationPhase→org.axonframework.common.configuration.Configurationorg.axonframework.messaging.eventhandling.configuration.DefaultEventHandlingComponentsConfigurer→org.axonframework.common.configuration.ComponentBuilderorg.axonframework.messaging.eventhandling.configuration.DefaultEventHandlingComponentsConfigurer→org.axonframework.common.configuration.Configurationorg.axonframework.messaging.eventhandling.configuration.EventBusConfigurationDefaults→org.axonframework.common.configuration.ComponentRegistryorg.axonframework.messaging.eventhandling.configuration.EventBusConfigurationDefaults→org.axonframework.common.configuration.Configurationorg.axonframework.messaging.eventhandling.configuration.EventBusConfigurationDefaults→org.axonframework.common.configuration.ConfigurationEnhancerorg.axonframework.messaging.eventhandling.configuration.EventProcessingConfigurer→org.axonframework.common.configuration.ComponentRegistryorg.axonframework.messaging.eventhandling.configuration.EventProcessingConfigurer→org.axonframework.common.configuration.Configurationorg.axonframework.messaging.eventhandling.configuration.EventProcessorConfiguration→org.axonframework.common.configuration.Configurationorg.axonframework.messaging.eventhandling.configuration.EventProcessorConfiguration→org.axonframework.common.configuration.ConfigurationExtensionsorg.axonframework.messaging.eventhandling.configuration.EventProcessorConfiguration→org.axonframework.common.configuration.ExtendedConfigurationorg.axonframework.messaging.eventhandling.configuration.EventProcessorConfiguration→org.axonframework.common.configuration.ExtensibleConfigurerorg.axonframework.messaging.eventhandling.configuration.EventProcessorModule→org.axonframework.common.configuration.Moduleorg.axonframework.messaging.eventhandling.configuration.SubscribableEventSourceDefinition→org.axonframework.common.configuration.Configuration
- Direction
- messaging.eventhandling.configuration uses common.configuration, so a change to common.configuration can break messaging.eventhandling.configuration, while a change to messaging.eventhandling.configuration can't break common.configuration.
- Position
- Below the diagonal: messaging.eventhandling.configuration uses a module listed above it, which is the healthy direction.
37→7 messaging.eventhandling.configuration uses messaging.core.unitofwork✕
- Connections
- 1 pair of types, where a type in messaging.eventhandling.configuration uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.messaging.eventhandling.configuration.EventProcessorConfiguration→org.axonframework.messaging.core.unitofwork.UnitOfWorkFactory
- Direction
- messaging.eventhandling.configuration uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break messaging.eventhandling.configuration, while a change to messaging.eventhandling.configuration can't break messaging.core.unitofwork.
- Position
- Below the diagonal: messaging.eventhandling.configuration uses a module listed above it, which is the healthy direction.
37→11 messaging.eventhandling.configuration uses messaging.eventhandling✕
- Connections
- 7 pairs of types, where a type in messaging.eventhandling.configuration uses a type in messaging.eventhandling.
- The types involved
org.axonframework.messaging.eventhandling.configuration.CompletePhase→org.axonframework.messaging.eventhandling.EventHandlingComponentorg.axonframework.messaging.eventhandling.configuration.CompletePhase→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.messaging.eventhandling.configuration.ComponentsPhase→org.axonframework.messaging.eventhandling.EventHandlingComponentorg.axonframework.messaging.eventhandling.configuration.DefaultEventHandlingComponentsConfigurer→org.axonframework.messaging.eventhandling.EventHandlingComponentorg.axonframework.messaging.eventhandling.configuration.DefaultEventHandlingComponentsConfigurer→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.messaging.eventhandling.configuration.EventBusConfigurationDefaults→org.axonframework.messaging.eventhandling.EventBusorg.axonframework.messaging.eventhandling.configuration.EventProcessorConfiguration→org.axonframework.messaging.eventhandling.EventMessage
- Direction
- messaging.eventhandling.configuration uses messaging.eventhandling, so a change to messaging.eventhandling can break messaging.eventhandling.configuration, while a change to messaging.eventhandling.configuration can't break messaging.eventhandling.
- Position
- Below the diagonal: messaging.eventhandling.configuration uses a module listed above it, which is the healthy direction.
37→15 messaging.eventhandling.configuration uses messaging.core✕
- Connections
- 5 pairs of types, where a type in messaging.eventhandling.configuration uses a type in messaging.core.
- The types involved
org.axonframework.messaging.eventhandling.configuration.CompletePhase→org.axonframework.messaging.core.MessageHandlerInterceptororg.axonframework.messaging.eventhandling.configuration.CompletePhase→org.axonframework.messaging.core.MessageHandlingExceptionHandlerorg.axonframework.messaging.eventhandling.configuration.DefaultEventHandlingComponentsConfigurer→org.axonframework.messaging.core.MessageHandlerInterceptororg.axonframework.messaging.eventhandling.configuration.EventProcessorConfiguration→org.axonframework.messaging.core.MessageHandlerInterceptororg.axonframework.messaging.eventhandling.configuration.SubscribableEventSourceDefinition→org.axonframework.messaging.core.SubscribableEventSource
- Direction
- messaging.eventhandling.configuration uses messaging.core, so a change to messaging.core can break messaging.eventhandling.configuration, while a change to messaging.eventhandling.configuration can't break messaging.core.
- Position
- Below the diagonal: messaging.eventhandling.configuration uses a module listed above it, which is the healthy direction.
37→26 messaging.eventhandling.configuration uses messaging.eventhandling.processing✕
- Connections
- 1 pair of types, where a type in messaging.eventhandling.configuration uses a type in messaging.eventhandling.processing.
- The types involved
org.axonframework.messaging.eventhandling.configuration.EventProcessorConfiguration→org.axonframework.messaging.eventhandling.processing.EventProcessor
- Direction
- messaging.eventhandling.configuration uses messaging.eventhandling.processing, so a change to messaging.eventhandling.processing can break messaging.eventhandling.configuration, while a change to messaging.eventhandling.configuration can't break messaging.eventhandling.processing.
- Position
- Below the diagonal: messaging.eventhandling.configuration uses a module listed above it, which is the healthy direction.
37→32 messaging.eventhandling.configuration uses messaging.eventhandling.processing.streaming.pooled✕
- Connections
- 3 pairs of types, where a type in messaging.eventhandling.configuration uses a type in messaging.eventhandling.processing.streaming.pooled.
- The types involved
org.axonframework.messaging.eventhandling.configuration.EventProcessingConfigurer→org.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorsConfigurerorg.axonframework.messaging.eventhandling.configuration.EventProcessorModule→org.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorConfigurationorg.axonframework.messaging.eventhandling.configuration.EventProcessorModule→org.axonframework.messaging.eventhandling.processing.streaming.pooled.PooledStreamingEventProcessorModule
- Direction
- messaging.eventhandling.configuration uses messaging.eventhandling.processing.streaming.pooled, so a change to messaging.eventhandling.processing.streaming.pooled can break messaging.eventhandling.configuration, while a change to messaging.eventhandling.configuration can't break messaging.eventhandling.processing.streaming.pooled.
- Position
- Below the diagonal: messaging.eventhandling.configuration uses a module listed above it, which is the healthy direction.
37→33 messaging.eventhandling.configuration uses messaging.eventhandling.processing.subscribing✕
- Connections
- 3 pairs of types, where a type in messaging.eventhandling.configuration uses a type in messaging.eventhandling.processing.subscribing.
- The types involved
org.axonframework.messaging.eventhandling.configuration.EventProcessingConfigurer→org.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessorsConfigurerorg.axonframework.messaging.eventhandling.configuration.EventProcessorModule→org.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessorConfigurationorg.axonframework.messaging.eventhandling.configuration.EventProcessorModule→org.axonframework.messaging.eventhandling.processing.subscribing.SubscribingEventProcessorModule
- Direction
- messaging.eventhandling.configuration uses messaging.eventhandling.processing.subscribing, so a change to messaging.eventhandling.processing.subscribing can break messaging.eventhandling.configuration, while a change to messaging.eventhandling.configuration can't break messaging.eventhandling.processing.subscribing.
- Position
- Below the diagonal: messaging.eventhandling.configuration uses a module listed above it, which is the healthy direction.
37→39 messaging.eventhandling.configuration uses messaging.core.configuration part of a loop✕
- Connections
- 1 pair of types, where a type in messaging.eventhandling.configuration uses a type in messaging.core.configuration.
- The types involved
org.axonframework.messaging.eventhandling.configuration.EventProcessingConfigurer→org.axonframework.messaging.core.configuration.MessagingConfigurer
- Direction
- messaging.eventhandling.configuration uses messaging.core.configuration, so a change to messaging.core.configuration can break messaging.eventhandling.configuration, while a change to messaging.eventhandling.configuration can't break messaging.core.configuration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
38→3 modelling.entity.annotation uses common.infra✕
- Connections
- 4 pairs of types, where a type in modelling.entity.annotation uses a type in common.infra.
- The types involved
org.axonframework.modelling.entity.annotation.AnnotatedEntityIdResolver→org.axonframework.common.infra.ComponentDescriptororg.axonframework.modelling.entity.annotation.AnnotatedEntityIdResolver→org.axonframework.common.infra.DescribableComponentorg.axonframework.modelling.entity.annotation.AnnotatedEntityMetamodel→org.axonframework.common.infra.ComponentDescriptororg.axonframework.modelling.entity.annotation.AnnotatedEntityMetamodel→org.axonframework.common.infra.DescribableComponent
- Direction
- modelling.entity.annotation uses common.infra, so a change to common.infra can break modelling.entity.annotation, while a change to modelling.entity.annotation can't break common.infra.
- Position
- Below the diagonal: modelling.entity.annotation uses a module listed above it, which is the healthy direction.
38→5 modelling.entity.annotation uses common.configuration✕
- Connections
- 1 pair of types, where a type in modelling.entity.annotation uses a type in common.configuration.
- The types involved
org.axonframework.modelling.entity.annotation.AnnotatedEntityIdResolverDefinition→org.axonframework.common.configuration.Configuration
- Direction
- modelling.entity.annotation uses common.configuration, so a change to common.configuration can break modelling.entity.annotation, while a change to modelling.entity.annotation can't break common.configuration.
- Position
- Below the diagonal: modelling.entity.annotation uses a module listed above it, which is the healthy direction.
38→7 modelling.entity.annotation uses messaging.core.unitofwork✕
- Connections
- 5 pairs of types, where a type in modelling.entity.annotation uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.modelling.entity.annotation.AnnotatedEntityIdResolver→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.modelling.entity.annotation.AnnotatedEntityMetamodel→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.modelling.entity.annotation.EntityDispatchHandlingMember→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.modelling.entity.annotation.RoutingKeyCommandTargetResolver→org.axonframework.messaging.core.unitofwork.ProcessingContextorg.axonframework.modelling.entity.annotation.RoutingKeyEventTargetMatcher→org.axonframework.messaging.core.unitofwork.ProcessingContext
- Direction
- modelling.entity.annotation uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break modelling.entity.annotation, while a change to modelling.entity.annotation can't break messaging.core.unitofwork.
- Position
- Below the diagonal: modelling.entity.annotation uses a module listed above it, which is the healthy direction.
38→8 modelling.entity.annotation uses messaging.commandhandling✕
- Connections
- 3 pairs of types, where a type in modelling.entity.annotation uses a type in messaging.commandhandling.
- The types involved
org.axonframework.modelling.entity.annotation.AnnotatedEntityMetamodel→org.axonframework.messaging.commandhandling.CommandMessageorg.axonframework.modelling.entity.annotation.AnnotatedEntityMetamodel→org.axonframework.messaging.commandhandling.CommandResultMessageorg.axonframework.modelling.entity.annotation.RoutingKeyCommandTargetResolver→org.axonframework.messaging.commandhandling.CommandMessage
- Direction
- modelling.entity.annotation uses messaging.commandhandling, so a change to messaging.commandhandling can break modelling.entity.annotation, while a change to modelling.entity.annotation can't break messaging.commandhandling.
- Position
- Below the diagonal: modelling.entity.annotation uses a module listed above it, which is the healthy direction.
38→9 modelling.entity.annotation uses messaging.core.conversion✕
- Connections
- 2 pairs of types, where a type in modelling.entity.annotation uses a type in messaging.core.conversion.
- The types involved
org.axonframework.modelling.entity.annotation.AnnotatedEntityIdResolver→org.axonframework.messaging.core.conversion.MessageConverterorg.axonframework.modelling.entity.annotation.AnnotatedEntityMetamodel→org.axonframework.messaging.core.conversion.MessageConverter
- Direction
- modelling.entity.annotation uses messaging.core.conversion, so a change to messaging.core.conversion can break modelling.entity.annotation, while a change to modelling.entity.annotation can't break messaging.core.conversion.
- Position
- Below the diagonal: modelling.entity.annotation uses a module listed above it, which is the healthy direction.
38→11 modelling.entity.annotation uses messaging.eventhandling✕
- Connections
- 2 pairs of types, where a type in modelling.entity.annotation uses a type in messaging.eventhandling.
- The types involved
org.axonframework.modelling.entity.annotation.AnnotatedEntityMetamodel→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.modelling.entity.annotation.RoutingKeyEventTargetMatcher→org.axonframework.messaging.eventhandling.EventMessage
- Direction
- modelling.entity.annotation uses messaging.eventhandling, so a change to messaging.eventhandling can break modelling.entity.annotation, while a change to modelling.entity.annotation can't break messaging.eventhandling.
- Position
- Below the diagonal: modelling.entity.annotation uses a module listed above it, which is the healthy direction.
38→12 modelling.entity.annotation uses messaging.eventhandling.conversion✕
- Connections
- 1 pair of types, where a type in modelling.entity.annotation uses a type in messaging.eventhandling.conversion.
- The types involved
org.axonframework.modelling.entity.annotation.AnnotatedEntityMetamodel→org.axonframework.messaging.eventhandling.conversion.EventConverter
- Direction
- modelling.entity.annotation uses messaging.eventhandling.conversion, so a change to messaging.eventhandling.conversion can break modelling.entity.annotation, while a change to modelling.entity.annotation can't break messaging.eventhandling.conversion.
- Position
- Below the diagonal: modelling.entity.annotation uses a module listed above it, which is the healthy direction.
38→14 modelling.entity.annotation uses messaging.core.annotation✕
- Connections
- 5 pairs of types, where a type in modelling.entity.annotation uses a type in messaging.core.annotation.
- The types involved
org.axonframework.modelling.entity.annotation.AnnotatedEntityMetamodel→org.axonframework.messaging.core.annotation.AnnotatedHandlerInspectororg.axonframework.modelling.entity.annotation.AnnotatedEntityMetamodel→org.axonframework.messaging.core.annotation.HandlerDefinitionorg.axonframework.modelling.entity.annotation.AnnotatedEntityMetamodel→org.axonframework.messaging.core.annotation.MessageHandlingMemberorg.axonframework.modelling.entity.annotation.AnnotatedEntityMetamodel→org.axonframework.messaging.core.annotation.ParameterResolverFactoryorg.axonframework.modelling.entity.annotation.EntityDispatchHandlingMember→org.axonframework.messaging.core.annotation.MessageHandlingMember
- Direction
- modelling.entity.annotation uses messaging.core.annotation, so a change to messaging.core.annotation can break modelling.entity.annotation, while a change to modelling.entity.annotation can't break messaging.core.annotation.
- Position
- Below the diagonal: modelling.entity.annotation uses a module listed above it, which is the healthy direction.
38→15 modelling.entity.annotation uses messaging.core✕
- Connections
- 9 pairs of types, where a type in modelling.entity.annotation uses a type in messaging.core.
- The types involved
org.axonframework.modelling.entity.annotation.AnnotatedEntityIdResolver→org.axonframework.messaging.core.Messageorg.axonframework.modelling.entity.annotation.AnnotatedEntityMetamodel→org.axonframework.messaging.core.Messageorg.axonframework.modelling.entity.annotation.AnnotatedEntityMetamodel→org.axonframework.messaging.core.MessageTypeResolverorg.axonframework.modelling.entity.annotation.AnnotatedEntityMetamodel→org.axonframework.messaging.core.QualifiedNameorg.axonframework.modelling.entity.annotation.AnnotatedEntityMetamodel→org.axonframework.messaging.core.Singleorg.axonframework.modelling.entity.annotation.AnnotatedEntityModelRoutingKeyMatcher→org.axonframework.messaging.core.Messageorg.axonframework.modelling.entity.annotation.AnnotatedEntityModelRoutingKeyMatcher→org.axonframework.messaging.core.MessageTypeorg.axonframework.modelling.entity.annotation.EntityDispatchHandlingMember→org.axonframework.messaging.core.Messageorg.axonframework.modelling.entity.annotation.EntityDispatchHandlingMember→org.axonframework.messaging.core.MessageStream
- Direction
- modelling.entity.annotation uses messaging.core, so a change to messaging.core can break modelling.entity.annotation, while a change to modelling.entity.annotation can't break messaging.core.
- Position
- Below the diagonal: modelling.entity.annotation uses a module listed above it, which is the healthy direction.
38→24 modelling.entity.annotation uses modelling✕
- Connections
- 2 pairs of types, where a type in modelling.entity.annotation uses a type in modelling.
- The types involved
org.axonframework.modelling.entity.annotation.AnnotatedEntityIdResolver→org.axonframework.modelling.EntityIdResolverorg.axonframework.modelling.entity.annotation.AnnotatedEntityIdResolverDefinition→org.axonframework.modelling.EntityIdResolver
- Direction
- modelling.entity.annotation uses modelling, so a change to modelling can break modelling.entity.annotation, while a change to modelling.entity.annotation can't break modelling.
- Position
- Below the diagonal: modelling.entity.annotation uses a module listed above it, which is the healthy direction.
38→28 modelling.entity.annotation uses modelling.entity✕
- Connections
- 8 pairs of types, where a type in modelling.entity.annotation uses a type in modelling.entity.
- The types involved
org.axonframework.modelling.entity.annotation.AbstractEntityChildModelDefinition→org.axonframework.modelling.entity.EntityMetamodelorg.axonframework.modelling.entity.annotation.AnnotatedEntityIdResolverDefinition→org.axonframework.modelling.entity.EntityMetamodelorg.axonframework.modelling.entity.annotation.AnnotatedEntityMetamodel→org.axonframework.modelling.entity.EntityMetamodelorg.axonframework.modelling.entity.annotation.AnnotatedEntityMetamodel→org.axonframework.modelling.entity.EntityMetamodelBuilderorg.axonframework.modelling.entity.annotation.EntityDispatchHandlingMember→org.axonframework.modelling.entity.EntityCommandHandlerInterceptorChainorg.axonframework.modelling.entity.annotation.ListEntityChildModelDefinition→org.axonframework.modelling.entity.EntityMetamodelorg.axonframework.modelling.entity.annotation.MapEntityChildModelDefinition→org.axonframework.modelling.entity.EntityMetamodelorg.axonframework.modelling.entity.annotation.SingleEntityChildModelDefinition→org.axonframework.modelling.entity.EntityMetamodel
- Direction
- modelling.entity.annotation uses modelling.entity, so a change to modelling.entity can break modelling.entity.annotation, while a change to modelling.entity.annotation can't break modelling.entity.
- Position
- Below the diagonal: modelling.entity.annotation uses a module listed above it, which is the healthy direction.
38→34 modelling.entity.annotation uses modelling.annotation✕
- Connections
- 1 pair of types, where a type in modelling.entity.annotation uses a type in modelling.annotation.
- The types involved
org.axonframework.modelling.entity.annotation.AnnotatedEntityIdResolverDefinition→org.axonframework.modelling.annotation.EntityIdResolverDefinition
- Direction
- modelling.entity.annotation uses modelling.annotation, so a change to modelling.annotation can break modelling.entity.annotation, while a change to modelling.entity.annotation can't break modelling.annotation.
- Position
- Below the diagonal: modelling.entity.annotation uses a module listed above it, which is the healthy direction.
39→5 messaging.core.configuration uses common.configuration✕
- Connections
- 9 pairs of types, where a type in messaging.core.configuration uses a type in common.configuration.
- The types involved
org.axonframework.messaging.core.configuration.MessagingConfigurationDefaults→org.axonframework.common.configuration.ComponentRegistryorg.axonframework.messaging.core.configuration.MessagingConfigurationDefaults→org.axonframework.common.configuration.Configurationorg.axonframework.messaging.core.configuration.MessagingConfigurationDefaults→org.axonframework.common.configuration.ConfigurationEnhancerorg.axonframework.messaging.core.configuration.MessagingConfigurer→org.axonframework.common.configuration.ApplicationConfigurerorg.axonframework.messaging.core.configuration.MessagingConfigurer→org.axonframework.common.configuration.AxonConfigurationorg.axonframework.messaging.core.configuration.MessagingConfigurer→org.axonframework.common.configuration.ComponentBuilderorg.axonframework.messaging.core.configuration.MessagingConfigurer→org.axonframework.common.configuration.ComponentRegistryorg.axonframework.messaging.core.configuration.MessagingConfigurer→org.axonframework.common.configuration.LifecycleRegistryorg.axonframework.messaging.core.configuration.MessagingConfigurer→org.axonframework.common.configuration.ModuleBuilder
- Direction
- messaging.core.configuration uses common.configuration, so a change to common.configuration can break messaging.core.configuration, while a change to messaging.core.configuration can't break common.configuration.
- Position
- Below the diagonal: messaging.core.configuration uses a module listed above it, which is the healthy direction.
39→6 messaging.core.configuration uses conversion✕
- Connections
- 1 pair of types, where a type in messaging.core.configuration uses a type in conversion.
- The types involved
org.axonframework.messaging.core.configuration.MessagingConfigurationDefaults→org.axonframework.conversion.DelegatingGeneralConverter
- Direction
- messaging.core.configuration uses conversion, so a change to conversion can break messaging.core.configuration, while a change to messaging.core.configuration can't break conversion.
- Position
- Below the diagonal: messaging.core.configuration uses a module listed above it, which is the healthy direction.
39→7 messaging.core.configuration uses messaging.core.unitofwork✕
- Connections
- 2 pairs of types, where a type in messaging.core.configuration uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.messaging.core.configuration.MessagingConfigurationDefaults→org.axonframework.messaging.core.unitofwork.UnitOfWorkFactoryorg.axonframework.messaging.core.configuration.MessagingConfigurer→org.axonframework.messaging.core.unitofwork.UnitOfWorkFactory
- Direction
- messaging.core.configuration uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break messaging.core.configuration, while a change to messaging.core.configuration can't break messaging.core.unitofwork.
- Position
- Below the diagonal: messaging.core.configuration uses a module listed above it, which is the healthy direction.
39→8 messaging.core.configuration uses messaging.commandhandling✕
- Connections
- 5 pairs of types, where a type in messaging.core.configuration uses a type in messaging.commandhandling.
- The types involved
org.axonframework.messaging.core.configuration.MessagingConfigurationDefaults→org.axonframework.messaging.commandhandling.CommandBusorg.axonframework.messaging.core.configuration.MessagingConfigurationDefaults→org.axonframework.messaging.commandhandling.CommandMessageorg.axonframework.messaging.core.configuration.MessagingConfigurationDefaults→org.axonframework.messaging.commandhandling.RoutingStrategyorg.axonframework.messaging.core.configuration.MessagingConfigurer→org.axonframework.messaging.commandhandling.CommandBusorg.axonframework.messaging.core.configuration.MessagingConfigurer→org.axonframework.messaging.commandhandling.CommandMessage
- Direction
- messaging.core.configuration uses messaging.commandhandling, so a change to messaging.commandhandling can break messaging.core.configuration, while a change to messaging.core.configuration can't break messaging.commandhandling.
- Position
- Below the diagonal: messaging.core.configuration uses a module listed above it, which is the healthy direction.
39→9 messaging.core.configuration uses messaging.core.conversion✕
- Connections
- 1 pair of types, where a type in messaging.core.configuration uses a type in messaging.core.conversion.
- The types involved
org.axonframework.messaging.core.configuration.MessagingConfigurationDefaults→org.axonframework.messaging.core.conversion.DelegatingMessageConverter
- Direction
- messaging.core.configuration uses messaging.core.conversion, so a change to messaging.core.conversion can break messaging.core.configuration, while a change to messaging.core.configuration can't break messaging.core.conversion.
- Position
- Below the diagonal: messaging.core.configuration uses a module listed above it, which is the healthy direction.
39→11 messaging.core.configuration uses messaging.eventhandling✕
- Connections
- 2 pairs of types, where a type in messaging.core.configuration uses a type in messaging.eventhandling.
- The types involved
org.axonframework.messaging.core.configuration.MessagingConfigurer→org.axonframework.messaging.eventhandling.EventMessageorg.axonframework.messaging.core.configuration.MessagingConfigurer→org.axonframework.messaging.eventhandling.EventSink
- Direction
- messaging.core.configuration uses messaging.eventhandling, so a change to messaging.eventhandling can break messaging.core.configuration, while a change to messaging.core.configuration can't break messaging.eventhandling.
- Position
- Below the diagonal: messaging.core.configuration uses a module listed above it, which is the healthy direction.
39→12 messaging.core.configuration uses messaging.eventhandling.conversion✕
- Connections
- 1 pair of types, where a type in messaging.core.configuration uses a type in messaging.eventhandling.conversion.
- The types involved
org.axonframework.messaging.core.configuration.MessagingConfigurationDefaults→org.axonframework.messaging.eventhandling.conversion.DelegatingEventConverter
- Direction
- messaging.core.configuration uses messaging.eventhandling.conversion, so a change to messaging.eventhandling.conversion can break messaging.core.configuration, while a change to messaging.core.configuration can't break messaging.eventhandling.conversion.
- Position
- Below the diagonal: messaging.core.configuration uses a module listed above it, which is the healthy direction.
39→13 messaging.core.configuration uses messaging.core.sequencing✕
- Connections
- 1 pair of types, where a type in messaging.core.configuration uses a type in messaging.core.sequencing.
- The types involved
org.axonframework.messaging.core.configuration.MessagingConfigurationDefaults→org.axonframework.messaging.core.sequencing.SequencingPolicy
- Direction
- messaging.core.configuration uses messaging.core.sequencing, so a change to messaging.core.sequencing can break messaging.core.configuration, while a change to messaging.core.configuration can't break messaging.core.sequencing.
- Position
- Below the diagonal: messaging.core.configuration uses a module listed above it, which is the healthy direction.
39→14 messaging.core.configuration uses messaging.core.annotation✕
- Connections
- 1 pair of types, where a type in messaging.core.configuration uses a type in messaging.core.annotation.
- The types involved
org.axonframework.messaging.core.configuration.MessagingConfigurer→org.axonframework.messaging.core.annotation.ParameterResolverFactory
- Direction
- messaging.core.configuration uses messaging.core.annotation, so a change to messaging.core.annotation can break messaging.core.configuration, while a change to messaging.core.configuration can't break messaging.core.annotation.
- Position
- Below the diagonal: messaging.core.configuration uses a module listed above it, which is the healthy direction.
39→15 messaging.core.configuration uses messaging.core✕
- Connections
- 5 pairs of types, where a type in messaging.core.configuration uses a type in messaging.core.
- The types involved
org.axonframework.messaging.core.configuration.MessagingConfigurationDefaults→org.axonframework.messaging.core.MessageTypeResolverorg.axonframework.messaging.core.configuration.MessagingConfigurer→org.axonframework.messaging.core.Messageorg.axonframework.messaging.core.configuration.MessagingConfigurer→org.axonframework.messaging.core.MessageDispatchInterceptororg.axonframework.messaging.core.configuration.MessagingConfigurer→org.axonframework.messaging.core.MessageHandlerInterceptororg.axonframework.messaging.core.configuration.MessagingConfigurer→org.axonframework.messaging.core.MessageTypeResolver
- Direction
- messaging.core.configuration uses messaging.core, so a change to messaging.core can break messaging.core.configuration, while a change to messaging.core.configuration can't break messaging.core.
- Position
- Below the diagonal: messaging.core.configuration uses a module listed above it, which is the healthy direction.
39→18 messaging.core.configuration uses messaging.queryhandling✕
- Connections
- 4 pairs of types, where a type in messaging.core.configuration uses a type in messaging.queryhandling.
- The types involved
org.axonframework.messaging.core.configuration.MessagingConfigurationDefaults→org.axonframework.messaging.queryhandling.QueryBusorg.axonframework.messaging.core.configuration.MessagingConfigurer→org.axonframework.messaging.queryhandling.QueryBusorg.axonframework.messaging.core.configuration.MessagingConfigurer→org.axonframework.messaging.queryhandling.QueryMessageorg.axonframework.messaging.core.configuration.MessagingConfigurer→org.axonframework.messaging.queryhandling.SubscriptionQueryUpdateMessage
- Direction
- messaging.core.configuration uses messaging.queryhandling, so a change to messaging.queryhandling can break messaging.core.configuration, while a change to messaging.core.configuration can't break messaging.queryhandling.
- Position
- Below the diagonal: messaging.core.configuration uses a module listed above it, which is the healthy direction.
39→21 messaging.core.configuration uses messaging.core.interception✕
- Connections
- 2 pairs of types, where a type in messaging.core.configuration uses a type in messaging.core.interception.
- The types involved
org.axonframework.messaging.core.configuration.MessagingConfigurationDefaults→org.axonframework.messaging.core.interception.DispatchInterceptorRegistryorg.axonframework.messaging.core.configuration.MessagingConfigurationDefaults→org.axonframework.messaging.core.interception.HandlerInterceptorRegistry
- Direction
- messaging.core.configuration uses messaging.core.interception, so a change to messaging.core.interception can break messaging.core.configuration, while a change to messaging.core.configuration can't break messaging.core.interception.
- Position
- Below the diagonal: messaging.core.configuration uses a module listed above it, which is the healthy direction.
39→37 messaging.core.configuration uses messaging.eventhandling.configuration✕
- Connections
- 1 pair of types, where a type in messaging.core.configuration uses a type in messaging.eventhandling.configuration.
- The types involved
org.axonframework.messaging.core.configuration.MessagingConfigurer→org.axonframework.messaging.eventhandling.configuration.EventProcessingConfigurer
- Direction
- messaging.core.configuration uses messaging.eventhandling.configuration, so a change to messaging.eventhandling.configuration can break messaging.core.configuration, while a change to messaging.core.configuration can't break messaging.eventhandling.configuration.
- Position
- Below the diagonal: messaging.core.configuration uses a module listed above it, which is the healthy direction.
40→1 eventsourcing.configuration uses common✕
- Connections
- 10 pairs of types, where a type in eventsourcing.configuration uses a type in common.
- The types involved
org.axonframework.eventsourcing.configuration.1→org.axonframework.common.TypeReferenceorg.axonframework.eventsourcing.configuration.12156→org.axonframework.common.TypeReferenceorg.axonframework.eventsourcing.configuration.12456→org.axonframework.common.TypeReferenceorg.axonframework.eventsourcing.configuration.2→org.axonframework.common.TypeReferenceorg.axonframework.eventsourcing.configuration.3→org.axonframework.common.TypeReferenceorg.axonframework.eventsourcing.configuration.4→org.axonframework.common.TypeReferenceorg.axonframework.eventsourcing.configuration.5→org.axonframework.common.TypeReferenceorg.axonframework.eventsourcing.configuration.7058→org.axonframework.common.TypeReferenceorg.axonframework.eventsourcing.configuration.7350→org.axonframework.common.TypeReferenceorg.axonframework.eventsourcing.configuration.7864→org.axonframework.common.TypeReference
- Direction
- eventsourcing.configuration uses common, so a change to common can break eventsourcing.configuration, while a change to eventsourcing.configuration can't break common.
- Position
- Below the diagonal: eventsourcing.configuration uses a module listed above it, which is the healthy direction.
40→3 eventsourcing.configuration uses common.infra✕
- Connections
- 2 pairs of types, where a type in eventsourcing.configuration uses a type in common.infra.
- The types involved
org.axonframework.eventsourcing.configuration.RepresentationConvertingEntityIdResolver→org.axonframework.common.infra.ComponentDescriptororg.axonframework.eventsourcing.configuration.RepresentationConvertingEntityIdResolver→org.axonframework.common.infra.DescribableComponent
- Direction
- eventsourcing.configuration uses common.infra, so a change to common.infra can break eventsourcing.configuration, while a change to eventsourcing.configuration can't break common.infra.
- Position
- Below the diagonal: eventsourcing.configuration uses a module listed above it, which is the healthy direction.
40→5 eventsourcing.configuration uses common.configuration✕
- Connections
- 23 pairs of types, where a type in eventsourcing.configuration uses a type in common.configuration.
- The types involved
org.axonframework.eventsourcing.configuration.AnnotatedEventSourcedEntityModule→org.axonframework.common.configuration.BaseModuleorg.axonframework.eventsourcing.configuration.AnnotatedEventSourcedEntityModule→org.axonframework.common.configuration.ComponentBuilderorg.axonframework.eventsourcing.configuration.AnnotatedEventSourcedEntityModule→org.axonframework.common.configuration.Configurationorg.axonframework.eventsourcing.configuration.CriteriaResolverPhase→org.axonframework.common.configuration.ComponentBuilderorg.axonframework.eventsourcing.configuration.EntityFactoryPhase→org.axonframework.common.configuration.ComponentBuilderorg.axonframework.eventsourcing.configuration.EventSourcingConfigurationDefaults→org.axonframework.common.configuration.ComponentRegistryorg.axonframework.eventsourcing.configuration.EventSourcingConfigurationDefaults→org.axonframework.common.configuration.Configurationorg.axonframework.eventsourcing.configuration.EventSourcingConfigurationDefaults→org.axonframework.common.configuration.ConfigurationEnhancerorg.axonframework.eventsourcing.configuration.EventSourcingConfigurer→org.axonframework.common.configuration.ApplicationConfigurerorg.axonframework.eventsourcing.configuration.EventSourcingConfigurer→org.axonframework.common.configuration.AxonConfigurationorg.axonframework.eventsourcing.configuration.EventSourcingConfigurer→org.axonframework.common.configuration.ComponentBuilderorg.axonframework.eventsourcing.configuration.EventSourcingConfigurer→org.axonframework.common.configuration.ComponentRegistryorg.axonframework.eventsourcing.configuration.EventSourcingConfigurer→org.axonframework.common.configuration.LifecycleRegistryorg.axonframework.eventsourcing.configuration.EventSourcingConfigurer→org.axonframework.common.configuration.ModuleBuilderorg.axonframework.eventsourcing.configuration.OptionalPhase→org.axonframework.common.configuration.ComponentBuilderorg.axonframework.eventsourcing.configuration.OptionalPhase→org.axonframework.common.configuration.ModuleBuilderorg.axonframework.eventsourcing.configuration.SimpleEventSourcedEntityModule→org.axonframework.common.configuration.BaseModuleorg.axonframework.eventsourcing.configuration.SimpleEventSourcedEntityModule→org.axonframework.common.configuration.ComponentBuilderorg.axonframework.eventsourcing.configuration.SimpleEventSourcedEntityModule→org.axonframework.common.configuration.ComponentDefinitionorg.axonframework.eventsourcing.configuration.SimpleEventSourcedEntityModule→org.axonframework.common.configuration.Configurationorg.axonframework.eventsourcing.configuration.SimpleEventSourcedEntityModule→org.axonframework.common.configuration.LifecycleRegistryorg.axonframework.eventsourcing.configuration.SnapshotSourcingConfigurationEnhancer→org.axonframework.common.configuration.ComponentRegistryorg.axonframework.eventsourcing.configuration.SnapshotSourcingConfigurationEnhancer→org.axonframework.common.configuration.ConfigurationEnhancer
- Direction
- eventsourcing.configuration uses common.configuration, so a change to common.configuration can break eventsourcing.configuration, while a change to eventsourcing.configuration can't break common.configuration.
- Position
- Below the diagonal: eventsourcing.configuration uses a module listed above it, which is the healthy direction.
40→7 eventsourcing.configuration uses messaging.core.unitofwork✕
- Connections
- 1 pair of types, where a type in eventsourcing.configuration uses a type in messaging.core.unitofwork.
- The types involved
org.axonframework.eventsourcing.configuration.RepresentationConvertingEntityIdResolver→org.axonframework.messaging.core.unitofwork.ProcessingContext
- Direction
- eventsourcing.configuration uses messaging.core.unitofwork, so a change to messaging.core.unitofwork can break eventsourcing.configuration, while a change to eventsourcing.configuration can't break messaging.core.unitofwork.
- Position
- Below the diagonal: eventsourcing.configuration uses a module listed above it, which is the healthy direction.
40→8 eventsourcing.configuration uses messaging.commandhandling✕
- Connections
- 1 pair of types, where a type in eventsourcing.configuration uses a type in messaging.commandhandling.
- The types involved
org.axonframework.eventsourcing.configuration.SimpleEventSourcedEntityModule→org.axonframework.messaging.commandhandling.CommandHandlingComponent
- Direction
- eventsourcing.configuration uses messaging.commandhandling, so a change to messaging.commandhandling can break eventsourcing.configuration, while a change to eventsourcing.configuration can't break messaging.commandhandling.
- Position
- Below the diagonal: eventsourcing.configuration uses a module listed above it, which is the healthy direction.
40→9 eventsourcing.configuration uses messaging.core.conversion✕
- Connections
- 1 pair of types, where a type in eventsourcing.configuration uses a type in messaging.core.conversion.
- The types involved
org.axonframework.eventsourcing.configuration.RepresentationConvertingEntityIdResolver→org.axonframework.messaging.core.conversion.MessageConverter
- Direction
- eventsourcing.configuration uses messaging.core.conversion, so a change to messaging.core.conversion can break eventsourcing.configuration, while a change to eventsourcing.configuration can't break messaging.core.conversion.
- Position
- Below the diagonal: eventsourcing.configuration uses a module listed above it, which is the healthy direction.
40→15 eventsourcing.configuration uses messaging.core✕
- Connections
- 2 pairs of types, where a type in eventsourcing.configuration uses a type in messaging.core.
- The types involved
org.axonframework.eventsourcing.configuration.RepresentationConvertingEntityIdResolver→org.axonframework.messaging.core.Messageorg.axonframework.eventsourcing.configuration.RepresentationConvertingEntityIdResolver→org.axonframework.messaging.core.QualifiedName
- Direction
- eventsourcing.configuration uses messaging.core, so a change to messaging.core can break eventsourcing.configuration, while a change to eventsourcing.configuration can't break messaging.core.
- Position
- Below the diagonal: eventsourcing.configuration uses a module listed above it, which is the healthy direction.
40→20 eventsourcing.configuration uses modelling.repository✕
- Connections
- 1 pair of types, where a type in eventsourcing.configuration uses a type in modelling.repository.
- The types involved
org.axonframework.eventsourcing.configuration.SimpleEventSourcedEntityModule→org.axonframework.modelling.repository.Repository
- Direction
- eventsourcing.configuration uses modelling.repository, so a change to modelling.repository can break eventsourcing.configuration, while a change to eventsourcing.configuration can't break modelling.repository.
- Position
- Below the diagonal: eventsourcing.configuration uses a module listed above it, which is the healthy direction.
40→24 eventsourcing.configuration uses modelling✕
- Connections
- 4 pairs of types, where a type in eventsourcing.configuration uses a type in modelling.
- The types involved
org.axonframework.eventsourcing.configuration.AnnotatedEventSourcedEntityModule→org.axonframework.modelling.EntityIdResolverorg.axonframework.eventsourcing.configuration.OptionalPhase→org.axonframework.modelling.EntityIdResolverorg.axonframework.eventsourcing.configuration.RepresentationConvertingEntityIdResolver→org.axonframework.modelling.EntityIdResolverorg.axonframework.eventsourcing.configuration.SimpleEventSourcedEntityModule→org.axonframework.modelling.EntityIdResolver
- Direction
- eventsourcing.configuration uses modelling, so a change to modelling can break eventsourcing.configuration, while a change to eventsourcing.configuration can't break modelling.
- Position
- Below the diagonal: eventsourcing.configuration uses a module listed above it, which is the healthy direction.
40→25 eventsourcing.configuration uses eventsourcing.eventstore✕
- Connections
- 6 pairs of types, where a type in eventsourcing.configuration uses a type in eventsourcing.eventstore.
- The types involved
org.axonframework.eventsourcing.configuration.EventSourcingConfigurationDefaults→org.axonframework.eventsourcing.eventstore.EventStorageEngineorg.axonframework.eventsourcing.configuration.EventSourcingConfigurationDefaults→org.axonframework.eventsourcing.eventstore.StorageEngineBackedEventStoreorg.axonframework.eventsourcing.configuration.EventSourcingConfigurationDefaults→org.axonframework.eventsourcing.eventstore.TagResolverorg.axonframework.eventsourcing.configuration.EventSourcingConfigurer→org.axonframework.eventsourcing.eventstore.EventStorageEngineorg.axonframework.eventsourcing.configuration.EventSourcingConfigurer→org.axonframework.eventsourcing.eventstore.EventStoreorg.axonframework.eventsourcing.configuration.EventSourcingConfigurer→org.axonframework.eventsourcing.eventstore.TagResolver
- Direction
- eventsourcing.configuration uses eventsourcing.eventstore, so a change to eventsourcing.eventstore can break eventsourcing.configuration, while a change to eventsourcing.configuration can't break eventsourcing.eventstore.
- Position
- Below the diagonal: eventsourcing.configuration uses a module listed above it, which is the healthy direction.
40→28 eventsourcing.configuration uses modelling.entity✕
- Connections
- 3 pairs of types, where a type in eventsourcing.configuration uses a type in modelling.entity.
- The types involved
org.axonframework.eventsourcing.configuration.MessagingModelPhase→org.axonframework.modelling.entity.EntityMetamodelorg.axonframework.eventsourcing.configuration.MessagingModelPhase→org.axonframework.modelling.entity.EntityMetamodelBuilderorg.axonframework.eventsourcing.configuration.SimpleEventSourcedEntityModule→org.axonframework.modelling.entity.EntityMetamodel
- Direction
- eventsourcing.configuration uses modelling.entity, so a change to modelling.entity can break eventsourcing.configuration, while a change to eventsourcing.configuration can't break modelling.entity.
- Position
- Below the diagonal: eventsourcing.configuration uses a module listed above it, which is the healthy direction.
40→34 eventsourcing.configuration uses modelling.annotation✕
- Connections
- 1 pair of types, where a type in eventsourcing.configuration uses a type in modelling.annotation.
- The types involved
org.axonframework.eventsourcing.configuration.AnnotatedEventSourcedEntityModule→org.axonframework.modelling.annotation.EntityIdResolverDefinition
- Direction
- eventsourcing.configuration uses modelling.annotation, so a change to modelling.annotation can break eventsourcing.configuration, while a change to eventsourcing.configuration can't break modelling.annotation.
- Position
- Below the diagonal: eventsourcing.configuration uses a module listed above it, which is the healthy direction.
40→35 eventsourcing.configuration uses eventsourcing✕
- Connections
- 6 pairs of types, where a type in eventsourcing.configuration uses a type in eventsourcing.
- The types involved
org.axonframework.eventsourcing.configuration.AnnotatedEventSourcedEntityModule→org.axonframework.eventsourcing.CriteriaResolverorg.axonframework.eventsourcing.configuration.AnnotatedEventSourcedEntityModule→org.axonframework.eventsourcing.EventSourcedEntityFactoryorg.axonframework.eventsourcing.configuration.CriteriaResolverPhase→org.axonframework.eventsourcing.CriteriaResolverorg.axonframework.eventsourcing.configuration.EntityFactoryPhase→org.axonframework.eventsourcing.EventSourcedEntityFactoryorg.axonframework.eventsourcing.configuration.SimpleEventSourcedEntityModule→org.axonframework.eventsourcing.CriteriaResolverorg.axonframework.eventsourcing.configuration.SimpleEventSourcedEntityModule→org.axonframework.eventsourcing.EventSourcedEntityFactory
- Direction
- eventsourcing.configuration uses eventsourcing, so a change to eventsourcing can break eventsourcing.configuration, while a change to eventsourcing.configuration can't break eventsourcing.
- Position
- Below the diagonal: eventsourcing.configuration uses a module listed above it, which is the healthy direction.
40→38 eventsourcing.configuration uses modelling.entity.annotation✕
- Connections
- 1 pair of types, where a type in eventsourcing.configuration uses a type in modelling.entity.annotation.
- The types involved
org.axonframework.eventsourcing.configuration.AnnotatedEventSourcedEntityModule→org.axonframework.modelling.entity.annotation.AnnotatedEntityMetamodel
- Direction
- eventsourcing.configuration uses modelling.entity.annotation, so a change to modelling.entity.annotation can break eventsourcing.configuration, while a change to eventsourcing.configuration can't break modelling.entity.annotation.
- Position
- Below the diagonal: eventsourcing.configuration uses a module listed above it, which is the healthy direction.
40→39 eventsourcing.configuration uses messaging.core.configuration✕
- Connections
- 1 pair of types, where a type in eventsourcing.configuration uses a type in messaging.core.configuration.
- The types involved
org.axonframework.eventsourcing.configuration.EventSourcingConfigurer→org.axonframework.messaging.core.configuration.MessagingConfigurer
- Direction
- eventsourcing.configuration uses messaging.core.configuration, so a change to messaging.core.configuration can break eventsourcing.configuration, while a change to eventsourcing.configuration can't break messaging.core.configuration.
- Position
- Below the diagonal: eventsourcing.configuration uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Event Sourcing
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 51 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 13 | Medium |
Roadmap
Top priorities: Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Replace Hibernate ddl-auto with Flyway or Liquibase, with `ddl-auto` set to `validate` so the production schema can evolve safely and reproducibly; Resolve the 474 No direct assertions finding(s) in Test Quality — start with MigrateAggregateDeadlineHandlerTest.java (37), Axon4ToAxoniq5LegacySagaTest.java (31), MoveSagaFieldToHandlerParameterTest.java (29).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +4.0 pts | Medium | Security & performance tooling |
| Replace Hibernate ddl-auto with Flyway or Liquibase, with `ddl-auto` set to `validate` so the production schema can evolve safely and reproducibly. | +4.0 pts | Medium | Schema migrations |
| Resolve the 6 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +1.4 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. | +1.2 pts | Low | Static Analysis (SAST) |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.2 pts | Medium | Release Hygiene |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. | +0.8 pts | Low | Static Analysis (SAST) |
| Keep implementation types off the public surface (Java: package-private (no modifier), or leave its package out of `module-info` exports; Kotlin: `internal`) so internals can change without breaking consumers. | +1.5 pts | Medium | Library API & versioning |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. | +0.7 pts | Low | Project Cohesion |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.9 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java | 5.6 | Mixed | Cyclomatic Complexity: CoordinationTask.run (cyclomatic 20) |
| REDACTED | 5.7 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerBuilders.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| migration/src/main/java/org/axonframework/migration/MigrateMessageInterceptorSignatures.java | 6.0 | Mixed | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 72 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 72 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 1140 of 1160 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.java, .kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 1,333 test(s) behind this row are the ones the code-model census could read, and this repository also carries at least 22 test source file(s) (.kt) that it cannot: it reads the test types the .java frontend declared, so a suite in any other language is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.java, .kt) and this repository declares a JVM test suite (repository root, Maven), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because central.sonatype.com — the registry that answers it — was asked and did not reply (the build stopped because central.sonatype.com, a repository this project declares, refused it with HTTP 403 — what this scan's egress allowlist returns for a host that is not on it; 59 dependencies were resolved and graded first, but the graph is partial so the result is reported and not scored). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add central.sonatype.com to the allowlist and re-run — not to build anything.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (pom.xml), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (osv) WERE scanned and every vulnerability they reported is included in this result; npm was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that npm is free of known-vulnerable dependencies.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `common/src/main/java/org/axonframework/common/ReflectionUtils.java`, `common/src/main/java/org/axonframework/common/infra/FilesystemStyleComponentDescriptor.java`, `eventsourcing/src/main/java/org/axonframework/eventsourcing/annotation/reflection/AnnotationBasedEventSourcedEntityFactory.java`, `eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/AggregateSequenceNumberPosition.java`, `eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/DefaultSourcingCondition.java`, … (+9 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D43 Malicious Dependencies — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (osv) WERE scanned and every vulnerability they reported is included in this result; npm was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that npm is free of known-vulnerable dependencies.
- AX9 CQS / query purity — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 1 query handler was classified, but the query-purity walk could not open its body: it recognises a value-returning entry point named Execute/Handle/Consume (±Async), or one implementing a member of the handler interface the type was classified on, and the handlers in this repository have neither. Scoring the set anyway would report every unopened handler as pure, so AX9 abstains instead of publishing a perfect score it did not measure.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (examples/university-multi-tenancy-examples/docker-compose.yaml). compose up failed (exit 1 — a container did not start, exited, or never became healthy) — no service selected; runtime evidence skipped.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- ES3 PII in the event store — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds persisted events that carry personal data no crypto-shredding strategy covers. It measured 12 of 13 valid (92.3 %) on held-out repositories, below the 95 % it must show (docs/plans/deterministic-engine/adjudication/ES3-H3H4.md), so by the pre-registered fallback (PREREGISTRATION v21) the events it finds are counted here, not reported as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Java, Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
13 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was MoveSagaFieldToHandlerParameter.planFor at 27. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being SequencingPolicyEventMessageHandlingMember.parseParameter at 19 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: messaging/src/main/java/org/axonframework/messaging/eventhandling/annotation/MethodSequencingPolicyEventHandlerDefinition.java (SequencingPolicyEventMessageHandlingMember.parseParameter at 19). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 13 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with MoveSagaFieldToHandlerParameter.planFor (cyclomatic 27), 15003.visitClassDeclaration (cyclomatic 20), CoordinationTask.run (cyclomatic 20). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 13 together lifts Cyclomatic Complexity from 8.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
31 method(s) exceeded the cognitive complexity threshold of 15; the worst was MoveSagaFieldToHandlerParameter.planFor at 40.
What to do
- Bring the 3 bodies over 30 down to 30 or less in Cognitive Complexity — start with MoveSagaFieldToHandlerParameter.planFor (cognitive 40), MigrateSnapshotTriggerDefinitionToAnnotation.detectTriggerType (cognitive 37), 1.removeGatewayFromConstructors (cognitive 36). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 7.0 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
37 god class(es) detected.
What to do
- Resolve the 12 MethodTooLong finding(s) in God Classes — start with MigrateCommandGatewayInEventHandler.java, MigrateCommandGatewayInSagaEventHandler.java, AddEventTagAnnotation.java. — One of this dimension's main actionable groups (12 warning-level).
- Resolve the 11 TooManyMethods finding(s) in God Classes — start with PooledStreamingEventProcessorConfiguration.java, ReflectionUtils.java, JdbcTokenStore.java. — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 9 ClassTooLong finding(s) in God Classes — start with Coordinator.java, AddEventTagAnnotation.java, MigrateCommandGatewayInEventHandler.java. — One of this dimension's main actionable groups (9 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
178 duplicated block group(s) detected. A further 14 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 63 of the 192 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 13 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with AddCommandAnnotation.java (2), DefaultComponentRegistry.java, MetricsConfigurationEnhancer.java. — One of this dimension's main actionable groups (13 warning-level).
- Resolve the 12 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with SimpleEventSourcedEntityModule.java (3), ReflectionUtils.java, JacksonConverter.java. — One of this dimension's main actionable groups (12 warning-level).
- Resolve the 11 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with MigrateCommandGatewayInEventHandler.java (2), JdbcTokenStore.java, SimpleQueryBus.java. — One of this dimension's main actionable groups (11 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
23 production modules (Maven), 0 dependency cycle(s), 1 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 15 of the 23 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Unstable project axon-spring-boot-starter finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
5 of 380 classes have LCOM4 above 3.
What to do
- Resolve the 5 Low cohesion finding(s) in Cohesion (LCOM4) — start with Coordinator.java, WorkPackage.java, TokenSchema.java. — One of this dimension's main actionable groups (5 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
What to do
- Enforce Architectural Integrity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D9 · Test Distribution
1333 test methods: 1333 unit, 0 integration, 0 BDD, 0 e2e.
D10 · Test Quality
4 skipped (4 with a documented reason), 606 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1333 tests (4 harness-style project(s) excluded from the assertion penalty). Measured on the .java suite only — at least 22 test source file(s) (.kt) went unread, so its test quality is unmeasured and is not in these counts.
What to do
- Resolve the 474 No direct assertions finding(s) in Test Quality — start with MigrateAggregateDeadlineHandlerTest.java (37), Axon4ToAxoniq5LegacySagaTest.java (31), MoveSagaFieldToHandlerParameterTest.java (29). — One of this dimension's main actionable groups (474 recommendation-level).
- Resolve the 132 No assertions finding(s) in Test Quality — start with TracingEventHandlingComponentTest.java (17), TracingQueryBusTest.java (8), AxonTestFixtureExcludesWhenInputsTest.java (8). — One of this dimension's main actionable groups (132 warning-level).
- Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 40 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 53 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 451 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph.
D15 · Churn × Complexity Hotspots
Top hotspots: migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java (7×20=140); migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java (6×19=114); migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java (5×19=95)
What to do
- Resolve the 5 Hotspot finding(s) in Churn × Complexity Hotspots — start with MigrateAggregateDeadlineHandler.java, AddAggregateScopeToDeadlineCalls.java, AddEventTagAnnotation.java. — One of this dimension's main actionable groups (5 warning-level).
D16 · Bus Factor
121 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is migration/src/main/java/org/axonframework/migration/MigrateSagaLifecycle.java. Counted over 698 of the 1161 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 6 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (6 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
111 deducted task-comment markers across 177770 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 110 TodoComment finding(s) in Explicit Debt — start with MigrateAggregateDeadlineHandlerTest.java (21), AddAggregateScopeToDeadlineCallsTest.java (9), MarkUnsupportedSagaTestFixtureCallsTest.java (7). — One of this dimension's main actionable groups (110 warning-level).
- Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with SimpleQueryBusSubscriptionQueryTest.java. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 143 document(s) read across 1 unit(s).
D20 · ADR Quality
0 of 1 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
D26 · Project Cohesion
3 of 15 build units (Maven, npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
62 % of calls cross a namespace and 49 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 High interface indirection finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
51 finding(s): 0 critical, 44 high, 7 medium, 0 low. 31 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 15 file(s) — `common/src/main/java/org/axonframework/common/ReflectionUtils.java` (line 544, line 547), `common/src/main/java/org/axonframework/common/infra/FilesystemStyleComponentDescriptor.java` (line 275, line 279, line 280, …), `eventsourcing/src/main/java/org/axonframework/eventsourcing/annotation/reflection/AnnotationBasedEventSourcedEntityFactory.java` (line 479, line 480), `eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/AggregateSequenceNumberPosition.java` (line 41, line 42, lines 66–69, …), `eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/DefaultSourcingCondition.java` (line 61), … (+10 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 5 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 31 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (31 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (osv). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (osv), and the findings above are real and complete for them. npm was not scanned (npm: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
D31 · IaC & Container Security
trivy and checkov found no infrastructure-as-code or container misconfigurations.
D34 · Knowledge Freshness
14 of 698 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/core/interception/ReactorDispatchInterceptorRegistry.java. Counted over 698 of the 1161 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: MappedMessageStream.java↔OnErrorContinueMessageStream.java 67%; FluxMessageStream.java↔MappedMessageStream.java 60%; FailedMessageStream.java↔MappedMessageStream.java 60%
What to do
- Resolve the 3 Change coupling finding(s) in Change Coupling — start with MessageStreamUtils.java, MergedMessageStream.java, EventProcessorProperties.java. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Change-coupling hub finding(s) in Change Coupling — start with MappedMessageStream.java, OnNextMessageStream.java. — One of this dimension's main actionable groups (2 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 6 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (osv). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (osv), and the findings above are real and complete for them. npm was not scanned (npm: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 4 platform declaration(s) and 89 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX1 · Captive dependencies
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons
- `SpringParameterResolverFactoryBean` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (factories; e.g. `factories` in `setAdditionalFactories` at line 85). — extensions/spring/spring/src/main/java/org/axonframework/extension/spring/config/annotation/SpringParameterResolverFactoryBean.java:42
- `SpringComponentRegistry` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (disableEnhancerScanning, beanFactory, factories; e.g. `disableEnhancerScanning` in `disableEnhancerScanning` at line 266). — extensions/spring/spring/src/main/java/org/axonframework/extension/spring/config/SpringComponentRegistry.java:104
What to do
- Java/Kotlin: keep container singletons stateless — move per-request data into locals or a request-scoped bean — or back the state with java.util.concurrent types (ConcurrentHashMap, AtomicInteger/AtomicReference), guard it with synchronized / a Lock (Kotlin: withLock), or mark a flag that is only ever overwritten volatile (@Volatile).
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
ES1 · Fold determinism
ES2 · Immutable events
IC1 · Incompleteness & stubs
- `position` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/ConsistencyMarkers.java:79
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×17) — common/src/test/java/org/axonframework/common/configuration/ApplicationConfigurerTestSuite.java:668, common/src/test/java/org/axonframework/common/configuration/ApplicationConfigurerTestSuite.java:699, eventsourcing/src/test/java/org/axonframework/eventsourcing/eventstore/StorageEngineBackedEventStoreTestSuite.java:249, …
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
- Clear the softer debt: re-enable or delete @Disabled/@Ignore tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace @SuppressWarnings("all") with targeted, justified suppressions.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 30 of 52 project(s) that lack one — worth up to 1.2 pts.
M2 · Architecture documentation
What to do
- Grow the ADR log (currently 1) — reach 8 to raise the maturity tier; document significant decisions as they're made.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
- 1045/1386 types (75%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
- Keep implementation types off the public surface (Java: package-private (no modifier), or leave its package out of `module-info` exports; Kotlin: `internal`) so internals can change without breaking consumers.
P2 · Observability
- Only 8/10 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `docs/_playbook`, `extensions/spring/spring-boot-compatibility-tests/common`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 12 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience
P8 · Schema migrations
- Hibernate ddl-auto builds the schema from the model at startup and keeps no migration history, so there is no reviewed, repeatable upgrade path for an existing production database — a renamed column is dropped and re-added rather than migrated. Adopt Flyway or Liquibase, with `ddl-auto` set to `validate`, so every schema change is a versioned file applied the same way in every environment. (×4) — extensions/spring/spring-boot-compatibility-tests/common/src/main/resources/application.yml:10, examples/workflow-bike-rental/src/main/resources/application.yaml:24, examples/university-java-springboot-4/src/main/resources/application.yml:14, …
What to do
- Replace Hibernate ddl-auto with Flyway or Liquibase, with `ddl-auto` set to `validate` so the production schema can evolve safely and reproducibly.
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×3) — update/src/main/java/org/axonframework/update/detection/KotlinVersion.java:49, update/src/main/java/org/axonframework/update/api/UpdateCheckResponse.java:158, extensions/spring/spring/src/main/java/org/axonframework/extension/spring/conversion/avro/SpecificRecordBaseClasspathAvroSchemaLoader.java:76
- `catch (RuntimeException)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×3) — migration/src/main/java/org/axonframework/migration/ConvertCommandHandlerConstructorToCompanionObject.java:213, migration/src/main/java/org/axonframework/migration/MigrateEventGatewayPublishInEventHandler.java:481, migration/src/main/java/org/axonframework/migration/ReplaceAggregateLifecycleApply.java:274
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `info` at line 138 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/jpa/JpaPollingEventCoordinator.java:138
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- 144/145 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
What to do
- Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 84% | Strong | Solid. |
| Architecture | 78% | Strong | Solid. |
| Maturity | 81% | Strong | Solid. |
| Readiness | 52% | Adequate — gated by P3, P8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 66% | Checked 5 of 11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event Sourcing | 100% | Exemplary | Strongest area. |
| Performance | 100% | Exemplary | Solid. |
Unscored — 3 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 24 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 44 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — 1 query handler detected, but its entry-point body could not be walked — the query-purity oracle recognises a value-returning Execute/Handle/Consume (±Async) entry point or one that implements the classifying handler interface's member, and this codebase's handlers were classified but never read. This is an engine limitation, not a finding about the repository.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 1 — a container did not start, exited, or never became healthy) — no service selected; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .java suite was found but not re-run
- D12 Dependency Hygiene — Dependency currency not established — central.sonatype.com did not answer
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Java, JavaScript, Kotlin not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (examples), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .java, .kt source were not judged.
- D25 ADR Conformance — None of 1 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- D32 Data Compliance (PII/GDPR) — 14 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (6 signals for this style, 3 needed — the count is met but a required primary signal is absent): 1 aggregate root(s) (entities that raise its domain events); 1 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 394 value object(s); 37 domain event(s); a Domain/Aggregates/ValueObjects layer; 3 repository port(s) loading or saving an aggregate/entity; a DDD annotation stack (jMolecules/Axon @AggregateRoot/@Aggregate/@ValueObject — persistence @Entity does not count); a top-level examples/ tree: a library or framework whose examples are its consumers — these types are building blocks, not a domain
- ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 31 event handler(s); 7 CQRS handler(s)
- ED5 Idempotency — Not assessed, and this one is on us: 37 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
- ES3 PII in the event store — This check finds persisted events that carry personal data no crypto-shredding strategy covers. It measured 12 of 13 valid (92.3 %) on held-out repositories, below the 95 % it must show (docs/plans/deterministic-engine/adjudication/ES3-H3H4.md), so by the pre-registered fallback (PREREGISTRATION v21) the events it finds are counted here, not reported as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- M4 Documentation accuracy — Not applicable: the 143 current-state document(s) make no claim of a kind M4 checks. 18 claim(s) of kinds M4 does not check were not checked (path 16, command argument 1, environment variable 1); M4 checks only links and versions and artefact counts.
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no C# was loaded; this repository's Java and Kotlin were read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter; a Kotlin request outside a suspend function has no caller's cancellation to honour
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 44 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 564 finding(s)
- No assertions: closesTheSpanAtContextCompletionWhenTheTransactionIsAbandoned eventsourcing/src/test/java/org/axonframework/eventsourcing/eventstore/tracing/TracingEventStorageEngineTest.java:107
- No assertions: addsResolvedTagsToTheActiveSpan eventsourcing/src/test/java/org/axonframework/eventsourcing/handler/tracing/annotation/TracingEventTagsHandlerEnhancerDefinitionTest.java:64
- No assertions: resolvesEventTagAnnotationsFromTheHandlersDeclaredPayloadType eventsourcing/src/test/java/org/axonframework/eventsourcing/handler/tracing/annotation/TracingEventTagsHandlerEnhancerDefinitionTest.java:82
- No assertions: opensASourcingSpanCarryingEntityTypeAndIdentifier eventsourcing/src/test/java/org/axonframework/eventsourcing/handler/tracing/TracingEntityLifecycleHandlerTest.java:53
- No assertions: opensAnInternalSpanWithQualifiedNameAndIdentifier eventsourcing/src/test/java/org/axonframework/eventsourcing/snapshot/store/tracing/TracingSnapshotStoreTest.java:58
- No assertions: opensAnInternalSpanForLoad eventsourcing/src/test/java/org/axonframework/eventsourcing/snapshot/store/tracing/TracingSnapshotStoreTest.java:94
- No assertions: leavesTheStorageEngineUndecoratedWhenEventStoreTracingIsDisabled eventsourcing/src/test/java/org/axonframework/eventsourcing/tracing/configuration/EventStorageEngineTracingConfigurationTest.java:84
- No assertions: tracesTheConfiguredStorageEngineUntilTheAppendTransactionRollsBack eventsourcing/src/test/java/org/axonframework/eventsourcing/tracing/configuration/EventStorageEngineTracingConfigurationTest.java:52
- No assertions: opensAnInternalSpanWithEntityTypeAndIdentifier modelling/src/test/java/org/axonframework/modelling/repository/tracing/TracingRepositoryTest.java:53
- No assertions: opensAnInternalSpanForPersist modelling/src/test/java/org/axonframework/modelling/repository/tracing/TracingRepositoryTest.java:73
- No assertions: attachBranchesContextSoDownstreamSpansNestUnderIt modelling/src/test/java/org/axonframework/modelling/repository/tracing/TracingRepositoryTest.java:141
- No assertions: loadBranchesContextSoDownstreamSpansNestUnderIt modelling/src/test/java/org/axonframework/modelling/repository/tracing/TracingRepositoryTest.java:94
- No assertions: loadOrCreateBranchesContextSoDownstreamSpansNestUnderIt modelling/src/test/java/org/axonframework/modelling/repository/tracing/TracingRepositoryTest.java:110
- No assertions: persistBranchesContextSoDownstreamSpansNestUnderIt modelling/src/test/java/org/axonframework/modelling/repository/tracing/TracingRepositoryTest.java:126
- No assertions: givenCoursesNotFullyBookedInFaculty_ThenNoNotificationSent examples/university-demo/src/test/java/org/axonframework/examples/demo/university/faculty/automation/allcoursesfullybookednotifier/WhenAllCoursesFullyBookedThenSendNotificationAxonFixtureTest.java:132
- No assertions: givenCourseCreatedAndRenamed_WhenChangeCapacity_ThenSuccess examples/university-demo/src/test/java/org/axonframework/examples/demo/university/faculty/write/changecoursecapacity/ChangeCourseCapacityAxonFixtureTest.java:71
- No assertions: givenCourseCreated_WhenChangeCapacityToTheSameName_ThenSuccess_NoEvents examples/university-demo/src/test/java/org/axonframework/examples/demo/university/faculty/write/changecoursecapacity/ChangeCourseCapacityAxonFixtureTest.java:58
- No assertions: givenCourseCreated_WhenChangeCapacity_ThenSuccess examples/university-demo/src/test/java/org/axonframework/examples/demo/university/faculty/write/changecoursecapacity/ChangeCourseCapacityAxonFixtureTest.java:45
- No assertions: givenStudentEnrolledInFaculty_WhenEnrollStudentInFaculty_ThenNothing examples/university-demo/src/test/java/org/axonframework/examples/demo/university/faculty/write/enrollstudent/EnrollStudentInFacultyFixtureTest.java:41
- No assertions: givenStudentNotEnrolledInFaculty_WhenEnrollStudentInFaculty_ThenStudentEnrolledInFaculty examples/university-demo/src/test/java/org/axonframework/examples/demo/university/faculty/write/enrollstudent/EnrollStudentInFacultyFixtureTest.java:27
- No assertions: givenCourseCreatedAndRenamed_WhenRenameCourse_ThenSuccess examples/university-demo/src/test/java/org/axonframework/examples/demo/university/faculty/write/renamecourse/RenameCourseAxonFixtureTest.java:71
- No assertions: givenCourseCreated_WhenRenameCourseToTheSameName_ThenSuccess_NoEvents examples/university-demo/src/test/java/org/axonframework/examples/demo/university/faculty/write/renamecourse/RenameCourseAxonFixtureTest.java:58
- No assertions: givenCourseCreated_WhenRenameCourse_ThenSuccess examples/university-demo/src/test/java/org/axonframework/examples/demo/university/faculty/write/renamecourse/RenameCourseAxonFixtureTest.java:45
- No assertions: studentAlreadySubscribedAnotherCourse examples/university-demo/src/test/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseAxonFixtureTest.java:82
- No assertions: studentSubscribedIfAnotherOneAlreadySubscribed examples/university-demo/src/test/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseAxonFixtureTest.java:98
- TodoComment migration/src/test/java/org/axonframework/migration/AddAggregateScopeToDeadlineCallsTest.java:632
- TodoComment migration/src/test/java/org/axonframework/migration/AddAggregateScopeToDeadlineCallsTest.java:682
- TodoComment migration/src/test/java/org/axonframework/migration/AddAggregateScopeToDeadlineCallsTest.java:737
- TodoComment migration/src/test/java/org/axonframework/migration/AddAggregateScopeToDeadlineCallsTest.java:854
- TodoComment migration/src/test/java/org/axonframework/migration/AddAggregateScopeToDeadlineCallsTest.java:800
- TodoComment migration/src/test/java/org/axonframework/migration/AddAggregateScopeToDeadlineCallsTest.java:807
- TodoComment migration/src/test/java/org/axonframework/migration/AddAggregateScopeToDeadlineCallsTest.java:914
- TodoComment migration/src/test/java/org/axonframework/migration/AddAggregateScopeToDeadlineCallsTest.java:959
- TodoComment migration/src/test/java/org/axonframework/migration/AddAggregateScopeToDeadlineCallsTest.java:998
- TodoComment migration/src/test/java/org/axonframework/migration/AddEventTagAnnotationFieldMatchingTest.java:81
- TodoComment migration/src/test/java/org/axonframework/migration/AddEventTagAnnotationFieldMatchingTest.java:142
- TodoComment migration/src/test/java/org/axonframework/migration/AddEventTagAnnotationFieldMatchingTest.java:190
- TodoComment migration/src/test/java/org/axonframework/migration/AddEventTagAnnotationFieldMatchingTest.java:238
- TodoComment migration/src/test/java/org/axonframework/migration/AddEventTagAnnotationFieldMatchingTest.java:297
- TodoComment migration/src/test/java/org/axonframework/migration/AddEventTagAnnotationKotlinTest.java:92
- TodoComment migration/src/test/java/org/axonframework/migration/AddEventTagAnnotationKotlinTest.java:202
- TodoComment migration/src/test/java/org/axonframework/migration/AddEventTagAnnotationKotlinTest.java:262
- TodoComment migration/src/test/java/org/axonframework/migration/AddEventTagAnnotationFieldMatchingTest.java:203
- TodoComment migration/src/test/java/org/axonframework/migration/Axon4ToAxon5EventSourcingTest.java:181
- TodoComment migration/src/test/java/org/axonframework/migration/Axon4ToAxon5MessagingTest.java:794
- TodoComment migration/src/test/java/org/axonframework/migration/Axon4ToAxon5MessagingTest.java:837
- TodoComment migration/src/test/java/org/axonframework/migration/Axon4ToAxon5MessagingTest.java:852
- TodoComment migration/src/test/java/org/axonframework/migration/Axon4ToAxon5QueryResponseTypesTest.java:239
- TodoComment migration/src/test/java/org/axonframework/migration/Axon4ToAxon5QueryResponseTypesTest.java:263
- TodoComment migration/src/test/java/org/axonframework/migration/Axon4ToAxon5QueryResponseTypesTest.java:297
- Duplicated block (9 lines × 2) common/src/main/java/org/axonframework/common/configuration/DefaultComponentRegistry.java:202
- Duplicated block (9 lines × 2) extensions/metrics/metrics-dropwizard/src/main/java/org/axonframework/extension/metrics/dropwizard/MetricsConfigurationEnhancer.java:91
- Duplicated block (9 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenEntry.java:233
- Duplicated block (9 lines × 2) migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:340
- Duplicated block (9 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:344
- Duplicated block (9 lines × 2) modelling/src/main/java/org/axonframework/modelling/entity/annotation/RoutingKeyCommandTargetResolverDefinition.java:54
- Duplicated block (9 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessorModule.java:204
- Duplicated block (9 lines × 2) extensions/spring/spring-boot-autoconfigure/src/main/java/org/axonframework/extension/springboot/autoconfig/InterceptorAutoConfiguration.java:71
- Duplicated block (9 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessorsConfigurer.java:167
- Duplicated block (9 lines × 2) migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:150
- Duplicated block (9 lines × 2) modelling/src/main/java/org/axonframework/modelling/entity/annotation/ListEntityChildModelDefinition.java:66
- Duplicated block (9 lines × 2) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/automation/NotificationAutomationConfiguration.java:28
- Duplicated block (9 lines × 2) examples/saga-recipes/src/main/java/org/axonframework/examples/sagarecipes/payment/write/confirmpayment/ConfirmPaymentCommandHandler.java:57
- MethodTooLong: MigrateCommandGatewayInEventHandler.getVisitor migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:96
- MethodTooLong: MigrateCommandGatewayInSagaEventHandler.getVisitor migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:85
- MethodTooLong: AddEventTagAnnotation.getVisitor migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:369
- MethodTooLong: MigrateSagaLifecycle.getVisitor migration/src/main/java/org/axonframework/migration/MigrateSagaLifecycle.java:106
- MethodTooLong: MigrateEventGatewayPublishInEventHandler.getVisitor migration/src/main/java/org/axonframework/migration/MigrateEventGatewayPublishInEventHandler.java:93
- MethodTooLong: MigrateAxonTestFixtureFluentApi.getVisitor migration/src/main/java/org/axonframework/migration/MigrateAxonTestFixtureFluentApi.java:90
- MethodTooLong: MigrateDeadlineManagerBuilders.getVisitor migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerBuilders.java:171
- MethodTooLong: MigrateMessageInterceptorSignatures.getVisitor migration/src/main/java/org/axonframework/migration/MigrateMessageInterceptorSignatures.java:129
- MethodTooLong: CoordinationTask.run messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java:782
- MethodTooLong: ReplaceAggregateLifecycleApply.getVisitor migration/src/main/java/org/axonframework/migration/ReplaceAggregateLifecycleApply.java:92
- MethodTooLong: ConvertCommandHandlerConstructorToCompanionObject.getVisitor migration/src/main/java/org/axonframework/migration/ConvertCommandHandlerConstructorToCompanionObject.java:86
- MethodTooLong: AddEntityCreatorAnnotation.getVisitor migration/src/main/java/org/axonframework/migration/AddEntityCreatorAnnotation.java:72
- Duplicated block (5 lines × 2) common/src/main/java/org/axonframework/common/ReflectionUtils.java:394
- Duplicated block (5 lines × 2) conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java:99
- Duplicated block (5 lines × 2) eventsourcing/src/main/java/org/axonframework/eventsourcing/configuration/SimpleEventSourcedEntityModule.java:246
- Duplicated block (5 lines × 2) eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/inmemory/InMemoryEventStorageEngine.java:336
- Duplicated block (5 lines × 2) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:966
- Duplicated block (5 lines × 2) migration/src/main/java/org/axonframework/migration/ConfigureEventSourcedAnnotation.java:231
- Duplicated block (5 lines × 2) migration/src/main/java/org/axonframework/migration/MethodParameters.java:261
- Duplicated block (5 lines × 2) modelling/src/main/java/org/axonframework/modelling/entity/annotation/AnnotatedEntityMetamodel.java:667
- Duplicated block (5 lines × 2) eventsourcing/src/main/java/org/axonframework/eventsourcing/configuration/SimpleEventSourcedEntityModule.java:80
- Duplicated block (5 lines × 2) eventsourcing/src/main/java/org/axonframework/eventsourcing/configuration/SimpleEventSourcedEntityModule.java:88
- Duplicated block (5 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:309
- Duplicated block (5 lines × 2) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java:56
- TooManyMethods: PooledStreamingEventProcessorConfiguration messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessorConfiguration.java:102
- TooManyMethods: ReflectionUtils common/src/main/java/org/axonframework/common/ReflectionUtils.java:61
- TooManyMethods: JdbcTokenStore messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenStore.java:64
- TooManyMethods: MessagingConfigurer messaging/src/main/java/org/axonframework/messaging/core/configuration/MessagingConfigurer.java:89
- TooManyMethods: WorkPackage messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/WorkPackage.java:89
- TooManyMethods: ResourceOverridingProcessingContext messaging/src/main/java/org/axonframework/messaging/core/unitofwork/ResourceOverridingProcessingContext.java:41
- TooManyMethods: UnitOfWorkProcessingContext messaging/src/main/java/org/axonframework/messaging/core/unitofwork/UnitOfWork.java:206
- TooManyMethods: PooledStreamingEventProcessor messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessor.java:90
- TooManyMethods: SpringComponentRegistry extensions/spring/spring/src/main/java/org/axonframework/extension/spring/config/SpringComponentRegistry.java:104
- TooManyMethods: 1 migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:86
- TooManyMethods: AnnotatedEntityMetamodel modelling/src/main/java/org/axonframework/modelling/entity/annotation/AnnotatedEntityMetamodel.java:108
- Duplicated block (8 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenStore.java:449
- Duplicated block (8 lines × 2) messaging/src/main/java/org/axonframework/messaging/queryhandling/SimpleQueryBus.java:258
- Duplicated block (8 lines × 2) migration/src/main/java/org/axonframework/migration/AddAxonTestFixtureTearDown.java:199
- Duplicated block (8 lines × 2) migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:312
- Duplicated block (8 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:130
- Duplicated block (8 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:373
- Duplicated block (8 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java:356
- Duplicated block (8 lines × 2) messaging/src/main/java/org/axonframework/messaging/core/configuration/MessagingConfigurationDefaults.java:394
- Duplicated block (8 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenEntry.java:185
- Duplicated block (8 lines × 2) update/src/main/java/org/axonframework/update/configuration/PropertyFileUsagePropertyProvider.java:121
- Duplicated block (8 lines × 2) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/enrollstudent/EnrollStudentInFacultyConfiguration.java:10
- Duplicated block (7 lines × 2) examples/university-message-transformation/src/main/java/org/axonframework/examples/demo/coursecatalog/InteractiveShell.java:290
- Duplicated block (7 lines × 2) messaging/src/main/java/org/axonframework/messaging/core/DelayedMessageStream.java:59
- Duplicated block (7 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:761
- Duplicated block (7 lines × 2) common/src/main/java/org/axonframework/common/configuration/ComponentDefinition.java:178
- Duplicated block (7 lines × 2) common/src/main/java/org/axonframework/common/configuration/ComponentDefinition.java:220
- Duplicated block (7 lines × 2) common/src/main/java/org/axonframework/common/configuration/DefaultComponentRegistry.java:213
- Duplicated block (7 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenEntry.java:217
- Duplicated block (7 lines × 2) messaging/src/main/java/org/axonframework/messaging/commandhandling/configuration/SimpleCommandHandlingModule.java:63
- Duplicated block (7 lines × 2) messaging/src/main/java/org/axonframework/messaging/commandhandling/interception/InterceptingCommandHandlingComponent.java:61
- Duplicated block (7 lines × 2) examples/saga-recipes/src/main/java/org/axonframework/examples/sagarecipes/rental/write/approverequest/ApproveRequestCommandHandler.java:126
- Duplicated block (7 lines × 2) examples/saga-recipes/src/main/java/org/axonframework/examples/sagarecipes/saga/eventsourced/AppendingPaymentProcess.java:208
- Duplicated block (6 lines × 2) common/src/main/java/org/axonframework/common/jdbc/ConnectionWrapperFactory.java:58
- Duplicated block (6 lines × 2) messaging/src/main/java/org/axonframework/messaging/core/CloseCallbackMessageStream.java:50
- Duplicated block (6 lines × 2) messaging/src/main/java/org/axonframework/messaging/core/FlatMappedMessageStream.java:59
- Duplicated block (6 lines × 2) messaging/src/main/java/org/axonframework/messaging/core/MergedMessageStream.java:76
- Duplicated block (6 lines × 2) migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:136
- Duplicated block (6 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:328
- Duplicated block (6 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessorModule.java:277
- Duplicated block (6 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenEntry.java:100
- Duplicated block (6 lines × 2) modelling/src/main/java/org/axonframework/modelling/entity/annotation/ListEntityChildModelDefinition.java:77
- Duplicated block (6 lines × 2) examples/university-message-transformation/src/main/java/org/axonframework/examples/demo/coursecatalog/catalog/transformations/WelcomeMessageBetaCleanup.java:60
- Duplicated block (6 lines × 2) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/UniversityAxonApplication.java:37
- ClassTooLong: Coordinator messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java:86
- ClassTooLong: AddEventTagAnnotation migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:103
- ClassTooLong: MigrateCommandGatewayInEventHandler migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:69
- ClassTooLong: MigrateDeadlineManagerBuilders migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerBuilders.java:90
- ClassTooLong: JdbcTokenStore messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenStore.java:64
- ClassTooLong: AddAggregateScopeToDeadlineCalls migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java:101
- ClassTooLong: SpringComponentRegistry extensions/spring/spring/src/main/java/org/axonframework/extension/spring/config/SpringComponentRegistry.java:104
- ClassTooLong: WorkPackage messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/WorkPackage.java:89
- ClassTooLong: MigrateAggregateDeadlineHandler migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java:99
- Members sharing a duplicated core (4 members, 50+ identical tokens) migration/src/main/java/org/axonframework/migration/AddAxonTestFixtureTearDown.java:198
- Members sharing a duplicated core (4 members, 50+ identical tokens) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:112
- Members sharing a duplicated core (4 members, 50+ identical tokens) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:127
- Members sharing a duplicated core (4 members, 50+ identical tokens) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:142
- Members sharing a duplicated core (4 members, 50+ identical tokens) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java:98
- Members sharing a duplicated core (4 members, 50+ identical tokens) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java:68
- Members sharing a duplicated core (4 members, 50+ identical tokens) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/changecoursecapacity/ChangeCourseCapacityController.java:42
- Members sharing a duplicated core (4 members, 50+ identical tokens) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseController.java:47
- Members sharing a duplicated core (4 members, 50+ identical tokens) examples/workflow-bike-rental/src/main/java/org/axonframework/examples/workflow/bikerental/rental/BikeStatusProjector.java:50
- Duplicated block (10 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/ProcessorEventHandlingComponents.java:254
- Duplicated block (10 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:221
- Duplicated block (10 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:244
- Duplicated block (10 lines × 2) modelling/src/main/java/org/axonframework/modelling/entity/ConcreteEntityMetamodel.java:234
- Duplicated block (10 lines × 2) modelling/src/main/java/org/axonframework/modelling/entity/ConcreteEntityMetamodel.java:250
- Duplicated block (10 lines × 2) messaging/src/main/java/org/axonframework/messaging/core/SimpleContext.java:72
- Duplicated block (10 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/MergeTask.java:94
- Duplicated block (10 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/GapAwareTrackingToken.java:240
- Duplicated block (10 lines × 2) REDACTED:68
- Duplicated block (12 lines × 2) eventsourcing/src/main/java/org/axonframework/eventsourcing/handler/SimpleEntityLifecycleHandler.java:85
- Duplicated block (12 lines × 2) messaging/src/main/java/org/axonframework/messaging/core/interception/annotation/MessageHandlerInterceptorDefinition.java:113
- Duplicated block (12 lines × 2) messaging/src/main/java/org/axonframework/messaging/core/unitofwork/transaction/TransactionManager.java:82
- Duplicated block (12 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessor.java:471
- Duplicated block (12 lines × 2) migration/src/main/java/org/axonframework/migration/MarkSagaResourceInjection.java:138
- Duplicated block (12 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:330
- Duplicated block (12 lines × 2) common/src/main/java/org/axonframework/common/caching/EhCacheAdapter.java:94
- Duplicated block (12 lines × 2) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/ConfigurationProperties.java:36
- Duplicated block (6 lines × 3) migration/src/main/java/org/axonframework/migration/ConfigureEventSourcedAnnotation.java:291
- Duplicated block (6 lines × 3) migration/src/main/java/org/axonframework/migration/MarkSagaResourceInjection.java:140
- Duplicated block (6 lines × 3) messaging/src/main/java/org/axonframework/messaging/commandhandling/annotation/AnnotatedCommandHandlingComponent.java:149
- Duplicated block (6 lines × 3) messaging/src/main/java/org/axonframework/messaging/commandhandling/GenericCommandResultMessage.java:148
- Duplicated block (6 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:59
- Duplicated block (6 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:67
- Duplicated block (6 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:75
- Duplicated block (6 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:83
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Swallowed exception (caught, then discarded) update/src/main/java/org/axonframework/update/detection/KotlinVersion.java:49
- Swallowed exception (caught, then discarded) update/src/main/java/org/axonframework/update/api/UpdateCheckResponse.java:158
- Swallowed exception (caught, then discarded) migration/src/main/java/org/axonframework/migration/ConvertCommandHandlerConstructorToCompanionObject.java:213
- Swallowed exception (caught, then discarded) migration/src/main/java/org/axonframework/migration/MigrateEventGatewayPublishInEventHandler.java:481
- Swallowed exception (caught, then discarded) migration/src/main/java/org/axonframework/migration/ReplaceAggregateLifecycleApply.java:274
- Swallowed exception (caught, then discarded) extensions/spring/spring/src/main/java/org/axonframework/extension/spring/conversion/avro/SpecificRecordBaseClasspathAvroSchemaLoader.java:76
- Hotspot: migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java:245
- Hotspot: migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java:333
- Hotspot: migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:234
- Hotspot: migration/src/main/java/org/axonframework/migration/MoveSagaFieldToHandlerParameter.java migration/src/main/java/org/axonframework/migration/MoveSagaFieldToHandlerParameter.java:257
- Hotspot: migration/src/main/java/org/axonframework/migration/MigrateAxonTestFixtureFluentApi.java migration/src/main/java/org/axonframework/migration/MigrateAxonTestFixtureFluentApi.java:93
- FileTooLong: pooled/Coordinator.java messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java
- FileTooLong: migration/AddEventTagAnnotation.java migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java
- FileTooLong: migration/MigrateCommandGatewayInEventHandler.java migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java
- FileTooLong: migration/MigrateDeadlineManagerBuilders.java migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerBuilders.java
- FileTooLong: config/SpringComponentRegistry.java extensions/spring/spring/src/main/java/org/axonframework/extension/spring/config/SpringComponentRegistry.java
- Duplicated block (15 lines × 2) conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java:109
- Duplicated block (15 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventstreaming/TagAndTypeFilteredEventCriteria.java:91
- Duplicated block (15 lines × 2) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/ConfigurationProperties.java:19
- Duplicated block (15 lines × 2) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/renamecourse/RenameCourseController.java:59
- Duplicated block (15 lines × 2) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentConfiguration.java:9
- Duplicated block (11 lines × 2) common/src/main/java/org/axonframework/common/infra/FilesystemStyleComponentDescriptor.java:137
- Duplicated block (11 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:206
- Duplicated block (11 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:422
- Duplicated block (11 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:438
- Duplicated block (11 lines × 2) conversion/src/main/java/org/axonframework/conversion/jackson/ByteArrayToJsonNodeConverter.java:60
- Low cohesion: Builder (LCOM4 20) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java:419
- Low cohesion: Builder (LCOM4 14) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/WorkPackage.java:791
- Low cohesion: Builder (LCOM4 8) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/TokenSchema.java:138
- Low cohesion: SubscribingEventProcessorConfiguration (LCOM4 7) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/subscribing/SubscribingEventProcessorConfiguration.java:52
- Low cohesion: Builder (LCOM4 4) extensions/metrics/metrics-micrometer/src/main/java/org/axonframework/extension/metrics/micrometer/MessageTimerMonitor.java:136
- Duplicated block (8 lines × 3) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:328
- Duplicated block (8 lines × 3) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/UniversityAxonApplication.java:60
- Duplicated block (8 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/automation/WhenCourseFullyBookedThenSendNotification.java:83
- Duplicated block (8 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/changecoursecapacity/ChangeCourseCapacityCommandHandler.java:50
- Duplicated block (7 lines × 3) migration/src/main/java/org/axonframework/migration/MarkSagaResourceInjection.java:138
- Duplicated block (7 lines × 3) extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/commandhandling/gateway/DefaultReactorCommandGateway.java:75
- Duplicated block (7 lines × 3) messaging/src/main/java/org/axonframework/messaging/commandhandling/interception/CommandMessageHandlerInterceptorChain.java:66
- Duplicated block (7 lines × 3) messaging/src/main/java/org/axonframework/messaging/eventhandling/configuration/EventProcessingConfigurer.java:157
- Schema created by Hibernate ddl-auto (no migration path) extensions/spring/spring-boot-compatibility-tests/common/src/main/resources/application.yml:10
- Schema created by Hibernate ddl-auto (no migration path) examples/workflow-bike-rental/src/main/resources/application.yaml:24
- Schema created by Hibernate ddl-auto (no migration path) examples/university-java-springboot-4/src/main/resources/application.yml:14
- Schema created by Hibernate ddl-auto (no migration path) examples/university-java-springboot-3/src/main/resources/application.yml:14
- REDACTED
- REDACTED
- REDACTED
- Change coupling: MessageStreamUtils.java ↔ SingleValueMessageStream.java messaging/src/main/java/org/axonframework/messaging/core/MessageStreamUtils.java:1
- Change coupling: MergedMessageStream.java ↔ SingleValueMessageStream.java messaging/src/main/java/org/axonframework/messaging/core/MergedMessageStream.java:1
- Change coupling: EventProcessorProperties.java ↔ SpringCustomizations.java extensions/spring/spring-boot-autoconfigure/src/main/java/org/axonframework/extension/springboot/EventProcessorProperties.java:1
- Duplicated block (14 lines × 2) conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java:152
- Duplicated block (14 lines × 2) migration/src/main/java/org/axonframework/migration/ConvertCommandHandlerConstructorToCompanionObject.java:156
- Duplicated block (14 lines × 2) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java:93
- Duplicated block (13 lines × 2) migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:552
- Duplicated block (13 lines × 2) messaging/src/main/java/org/axonframework/messaging/commandhandling/SimpleCommandHandlingComponent.java:70
- Duplicated block (13 lines × 2) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/UniversityAxonApplication.java:58
- Duplicated block (11 lines × 3) extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/commandhandling/gateway/DefaultReactorCommandGateway.java:137
- Duplicated block (11 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/automation/WhenCourseFullyBookedThenSendNotification.java:99
- Duplicated block (11 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:95
- Duplicated block (10–11 lines × 2) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:325
- Duplicated block (10–11 lines × 2) migration/src/main/java/org/axonframework/migration/FlagSerializerBeans.java:92
- Duplicated block (10–11 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java:303
- Duplicated block (9 lines × 3) messaging/src/main/java/org/axonframework/messaging/commandhandling/annotation/AnnotatedCommandHandlingComponent.java:84
- Duplicated block (9 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java:80
- Duplicated block (9 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:55
- Duplicated block (5 lines × 3) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:374
- Duplicated block (5 lines × 3) messaging/src/main/java/org/axonframework/messaging/eventhandling/configuration/EventProcessingConfigurer.java:141
- Duplicated block (5 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java:53
- Duplicated block (7 lines × 4) extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/core/interception/DefaultReactorDispatchInterceptorRegistry.java:184
- Duplicated block (7 lines × 4) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java:99
- Duplicated block (7 lines × 4) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:58
- Duplicated block (17 lines × 2) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java:126
- Duplicated block (17 lines × 2) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/changecoursecapacity/ChangeCourseCapacityConfiguration.java:10
- Duplicated block (17 lines × 2) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/unsubscribestudent/UnsubscribeStudentConfiguration.java:9
- Stateful singleton: SpringParameterResolverFactoryBean extensions/spring/spring/src/main/java/org/axonframework/extension/spring/config/annotation/SpringParameterResolverFactoryBean.java:42
- Stateful singleton: SpringComponentRegistry extensions/spring/spring/src/main/java/org/axonframework/extension/spring/config/SpringComponentRegistry.java:104
- REDACTED
- REDACTED
- Change-coupling hub: MappedMessageStream.java → EmptyMessageStream.java, FailedMessageStream.java, FluxMessageStream.java, OnErrorContinueMessageStream.java messaging/src/main/java/org/axonframework/messaging/core/MappedMessageStream.java
- Change-coupling hub: OnNextMessageStream.java → ConcatenatingMessageStream.java, FailedMessageStream.java, FluxMessageStream.java, OnErrorContinueMessageStream.java messaging/src/main/java/org/axonframework/messaging/core/OnNextMessageStream.java
- REDACTED
- REDACTED
- Members sharing a duplicated core (6 members, 50+ identical tokens) messaging/src/main/java/org/axonframework/messaging/commandhandling/GenericCommandMessage.java:155
- Members sharing a duplicated core (6 members, 50+ identical tokens) migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java:717
- Members sharing a duplicated core (5 members, 50+ identical tokens) messaging/src/main/java/org/axonframework/messaging/monitoring/interception/MonitoringCommandHandlerInterceptor.java:55
- Members sharing a duplicated core (5 members, 50+ identical tokens) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:235
- Duplicated block (25 lines × 2) common/src/main/java/org/axonframework/common/configuration/DefaultComponentRegistry.java:327
- Duplicated block (25 lines × 2) messaging/src/main/java/org/axonframework/messaging/commandhandling/configuration/SimpleCommandHandlingModule.java:112
- Duplicated block (16 lines × 2) conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java:135
- Duplicated block (16 lines × 2) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/changecoursecapacity/ChangeCourseCapacityController.java:43
- Duplicated block (9 lines × 4) migration/src/main/java/org/axonframework/migration/MarkSagaResourceInjection.java:221
- Duplicated block (9 lines × 4) examples/workflow-bike-rental/src/main/java/org/axonframework/examples/workflow/bikerental/rental/BikeStatusProjector.java:55
- Duplicated block (19 lines × 2) extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/core/interception/DefaultReactorDispatchInterceptorRegistry.java:74
- Duplicated block (19 lines × 2) examples/spring-cloud/springboot3/src/main/java/org/axonframework/examples/springcloud/UniversityApplication.java:42
- Duplicated block (23 lines × 2) eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/tracing/TracingEventStore.java:68
- Duplicated block (23 lines × 2) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/enrollstudent/EnrollStudentInFacultyController.java:59
- Duplicated block (43 lines × 3) REDACTED:80
- Duplicated block (43 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/InMemoryCourseStatsRepository.java:1
- Duplicated block (12 lines × 4) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:113
- Duplicated block (12 lines × 4) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:128
- MoveSagaFieldToHandlerParameter.planFor (cyclomatic 27) migration/src/main/java/org/axonframework/migration/MoveSagaFieldToHandlerParameter.java:257
- 15003.visitClassDeclaration (cyclomatic 20) migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java:245
- CoordinationTask.run (cyclomatic 20) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java:782
- 17091.visitMethodInvocation (cyclomatic 19) migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java:333
- 11940.visitClassDeclaration (cyclomatic 19) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:234
- 1.visitMethodInvocation (cyclomatic 19) migration/src/main/java/org/axonframework/migration/MigrateAxonTestFixtureFluentApi.java:93
- 1.methodsNeedingContext (cyclomatic 18) migration/src/main/java/org/axonframework/migration/MigrateEventGatewayPublishInEventHandler.java:154
- AddAggregateScopeToDeadlineCalls.commandIdentifier (cyclomatic 17) migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java:532
- Aggregate.of (cyclomatic 17) migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java:743
- 1.removeGatewayFromConstructors (cyclomatic 17) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:760
- MigrateSnapshotTriggerDefinitionToAnnotation.detectTriggerType (cyclomatic 17) migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java:367
- 5.visitMethodInvocation (cyclomatic 16) migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerBuilders.java:738
- AvroConverter.convert (cyclomatic 16) conversion/src/main/java/org/axonframework/conversion/avro/AvroConverter.java:123
- FixmeComment integrationtests/src/test/java/org/axonframework/integrationtests/queryhandling/SimpleQueryBusSubscriptionQueryTest.java:52
- MoveSagaFieldToHandlerParameter.planFor (cognitive 40) migration/src/main/java/org/axonframework/migration/MoveSagaFieldToHandlerParameter.java:257
- MigrateSnapshotTriggerDefinitionToAnnotation.detectTriggerType (cognitive 37) migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java:367
- 1.removeGatewayFromConstructors (cognitive 36) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:760
- 15003.visitClassDeclaration (cognitive 28) migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java:245
- AddCommandAnnotation.hasRoutingKeyAttribute (cognitive 27) migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:338
- AddEventAnnotation.findRevisionValue (cognitive 27) migration/src/main/java/org/axonframework/migration/AddEventAnnotation.java:176
- 1.removeGatewayFromConstructors (cognitive 27) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:546
- 11940.visitClassDeclaration (cognitive 26) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:234
- 1.methodsNeedingContext (cognitive 26) migration/src/main/java/org/axonframework/migration/MigrateEventGatewayPublishInEventHandler.java:154
- CoordinationTask.run (cognitive 26) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java:782
- Aggregate.of (cognitive 25) migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java:743
- 20014.classFields (cognitive 25) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:846
- AvroConverter.convert (cognitive 24) conversion/src/main/java/org/axonframework/conversion/avro/AvroConverter.java:123
- 20014.resolveIndent (cognitive 23) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:773
- 1.unitOfWorkFactoryInScope (cognitive 23) migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerBuilders.java:339
- AddCommandAnnotation.findFieldName (cognitive 22) migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:309
- 5.visitMethodInvocation (cognitive 22) migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerBuilders.java:738
- MigrateSnapshotTriggerDefinitionToAnnotation.isSnapshotTriggerDefinitionMethod (cognitive 21) migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java:287
- 17091.visitMethodInvocation (cognitive 20) migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java:333
- 6861.visitAnnotation (cognitive 20) migration/src/main/java/org/axonframework/migration/ConfigureEventSourcedAnnotation.java:148
- SpringUtils.isQualifierMatch (cognitive 20) extensions/spring/spring/src/main/java/org/axonframework/extension/spring/SpringUtils.java:87
- JacksonConverter.convert (cognitive 20) conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java:107
- AddAggregateScopeToDeadlineCalls.commandIdentifier (cognitive 19) migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java:532
- AddAggregateScopeToDeadlineCalls.identifier (cognitive 19) migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java:664
- MigrateAggregateDeadlineHandler.aggregateTypeOf (cognitive 19) migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java:363
- MigrateAggregateDeadlineHandler.commandNamesOf (cognitive 19) migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java:402
- Jackson2Converter.convert (cognitive 19) conversion/src/main/java/org/axonframework/conversion/jackson2/Jackson2Converter.java:91
- CoordinationTask.coordinateWorkPackages (cognitive 18) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java:1362
- 1.visitNewClass (cognitive 17) migration/src/main/java/org/axonframework/migration/MigrateAggregateTestFixtureSetup.java:105
- AnnotationBasedEventSourcedEntityFactory.addEntityCreatorExecutable (cognitive 17) eventsourcing/src/main/java/org/axonframework/eventsourcing/annotation/reflection/AnnotationBasedEventSourcedEntityFactory.java:182
- 1.extractClassLiteralType (cognitive 16) migration/src/main/java/org/axonframework/migration/MigrateAggregateTestFixtureSetup.java:186
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Near-duplicate member pair (45 shared lines) conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java:108
- Duplicated block (18–21 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:286
- Duplicated block (17–18 lines × 2) common/src/main/java/org/axonframework/common/configuration/DefaultComponentRegistry.java:402
- Duplicated block (18 lines × 2) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:290
- Duplicated block (13–15 lines × 2) common/src/main/java/org/axonframework/common/jdbc/ConnectionWrapperFactory.java:69
- Duplicated block (14–15 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:149
- Duplicated block (13 lines × 3) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/segmenting/AddedTrackerStatus.java:44
- Duplicated block (6–13 lines × 3) extensions/metrics/metrics-micrometer/src/main/java/org/axonframework/extension/metrics/micrometer/MetricsConfigurationEnhancer.java:131
- Duplicated block (9–13 lines × 2) migration/src/main/java/org/axonframework/migration/ConfigureEventSourcedAnnotation.java:291
- Duplicated block (11–12 lines × 3) messaging/src/main/java/org/axonframework/messaging/commandhandling/configuration/CommandHandlingModule.java:246
- Duplicated block (9–12 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:503
- Duplicated block (11 lines × 5) messaging/src/main/java/org/axonframework/messaging/monitoring/interception/MonitoringCommandHandlerInterceptor.java:57
- Duplicated block (8–10 lines × 3) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:276
- Duplicated block (7–10 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:799
- Duplicated block (4–10 lines × 3) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:775
- Duplicated block (9 lines × 6) messaging/src/main/java/org/axonframework/messaging/commandhandling/GenericCommandMessage.java:156
- Duplicated block (7–9 lines × 2) eventsourcing/src/main/java/org/axonframework/eventsourcing/annotation/reflection/AnnotationBasedEventSourcedEntityFactory.java:399
- Duplicated block (7–8 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenStore.java:582
- Duplicated block (6 lines × 6) migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java:721
- Duplicated block (4–5 lines × 3) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:510
- Duplicated block (26 lines × 2) conversion/src/main/java/org/axonframework/conversion/DelegatingGeneralConverter.java:44
- Duplicated block (63 lines × 2) conversion/src/main/java/org/axonframework/conversion/jackson/JsonNodeToObjectNodeConverter.java:1
- Duplicated block (144 lines × 2) extensions/spring/spring-boot-autoconfigure/src/main/java/org/axonframework/extension/springboot/autoconfig/CBORConverterAutoConfiguration.java:1
- Duplicated block (59 lines × 2) messaging/src/main/java/org/axonframework/messaging/commandhandling/CommandExecutionException.java:42
- Duplicated block (5 lines × 5) extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/core/interception/DefaultReactorDispatchInterceptorRegistry.java:107
- Duplicated block (23–24 lines × 2) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/createcourse/CreateCourseController.java:64
- Duplicated block (18 lines × 4) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:145
- Duplicated block (14–16 lines × 4) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseController.java:53
- Duplicated block (14 lines × 4) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/changecoursecapacity/ChangeCourseCapacityController.java:48
- Duplicated block (10–11 lines × 4) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java:73
- Duplicated block (9–11 lines × 2) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/read/coursestats/CourseStatsConfiguration.java:20
- Duplicated block (116 lines × 2) examples/saga-recipes/src/main/java/org/axonframework/examples/sagarecipes/saga/verticalslices/whenpaymentcancelledthenrejectrequest/WhenPaymentCancelledThenRejectRequest.java:1
- Duplicated block (21 lines × 4) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/read/coursestats/InMemoryCourseStatsRepository.java:1
- Duplicated block (31 lines × 4) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/shared/ids/CourseId.java:1
- Duplicated block (41 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStats.java:1
- Duplicated block (43 lines × 2) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjectionConfiguration.java:1
- Duplicated block (16 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/createcourse/CourseCreation.java:41
- Duplicated block (55 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/enrollstudent/EnrollStudentInFacultyCommandHandler.java:1
- Duplicated block (21 lines × 2) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/renamecourse/CourseRenaming.java:39
- Duplicated block (10 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:47
- Unstable project axon-spring-boot-starter
- Unfinished stub — throws a "not implemented" exception eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/ConsistencyMarkers.java:79
- Coverage collected but not gated
Minor — 548 finding(s)
- No direct assertions: givenPreparedPaymentWhenCancelPaymentThenPaymentCancelled examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/payment/write/cancelpayment/CancelPaymentCommandHandlerTest.java:45
- No direct assertions: givenNoPaymentAtAllWhenCancelPaymentThenIgnoredSilently examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/payment/write/cancelpayment/CancelPaymentCommandHandlerTest.java:115
- No direct assertions: givenPaymentAlreadyCancelledWhenCancelPaymentAgainThenIgnoredSilently examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/payment/write/cancelpayment/CancelPaymentCommandHandlerTest.java:98
- No direct assertions: givenPaymentAlreadyConfirmedWhenCancelPaymentThenIgnoredSilently examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/payment/write/cancelpayment/CancelPaymentCommandHandlerTest.java:64
- No direct assertions: givenPaymentAlreadyRejectedWhenCancelPaymentThenIgnoredSilently examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/payment/write/cancelpayment/CancelPaymentCommandHandlerTest.java:81
- No direct assertions: givenNoPaymentWhenConfirmPaymentThenRejected examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/payment/write/confirmpayment/ConfirmPaymentCommandHandlerTest.java:56
- No direct assertions: givenPreparedPaymentWhenConfirmPaymentThenPaymentConfirmed examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/payment/write/confirmpayment/ConfirmPaymentCommandHandlerTest.java:40
- No direct assertions: givenPaymentAlreadyCancelledWhenConfirmPaymentThenIgnoredSilently examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/payment/write/confirmpayment/ConfirmPaymentCommandHandlerTest.java:89
- No direct assertions: givenPaymentAlreadyConfirmedWhenConfirmPaymentAgainThenNoEventsAndSuccess examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/payment/write/confirmpayment/ConfirmPaymentCommandHandlerTest.java:72
- No direct assertions: givenPaymentAlreadyPreparedWhenPreparePaymentForSameReferenceThenNoEventsAndSuccess examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/payment/write/preparepayment/PreparePaymentCommandHandlerTest.java:72
- No direct assertions: paymentContextKnowsNothingAboutRentingOrTheSaga examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/payment/PaymentContextIsolationTest.java:44
- No direct assertions: rentalContextKnowsNothingAboutPaymentOrTheSaga examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/payment/PaymentContextIsolationTest.java:54
- No direct assertions: givenPendingRequestWhenApproveRequestThenBikeInUse examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/rental/write/approverequest/ApproveRequestCommandHandlerTest.java:51
- No direct assertions: givenBikeReservedByAnotherRenterWhenApproveRequestThenNoEventsAndSuccess examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/rental/write/approverequest/ApproveRequestCommandHandlerTest.java:107
- No direct assertions: givenNeverRequestedBikeWhenApproveRequestThenNoEventsAndSuccess examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/rental/write/approverequest/ApproveRequestCommandHandlerTest.java:127
- No direct assertions: givenRequestAlreadyApprovedWhenApproveRequestAgainThenNoEventsAndSuccess examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/rental/write/approverequest/ApproveRequestCommandHandlerTest.java:71
- No direct assertions: givenRequestAlreadyRejectedWhenApproveRequestThenNoEventsAndSuccess examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/rental/write/approverequest/ApproveRequestCommandHandlerTest.java:89
- No direct assertions: givenNoBikeWhenRegisterBikeThenBikeRegistered examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/rental/write/registerbike/RegisterBikeCommandHandlerTest.java:37
- No direct assertions: givenRegisteredBikeWhenRegisterBikeAgainThenNoEventsAndSuccess examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/rental/write/registerbike/RegisterBikeCommandHandlerTest.java:52
- No direct assertions: givenPendingRequestWhenRejectRequestThenRequestRejected examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/rental/write/rejectrequest/RejectRequestCommandHandlerTest.java:46
- No direct assertions: givenNeverRequestedBikeWhenRejectRequestThenNoEventsAndSuccess examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/rental/write/rejectrequest/RejectRequestCommandHandlerTest.java:106
- No direct assertions: givenRequestAlreadyApprovedWhenRejectRequestThenNoEventsAndSuccess examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/rental/write/rejectrequest/RejectRequestCommandHandlerTest.java:88
- No direct assertions: givenRequestAlreadyRejectedWhenRejectRequestAgainThenNoEventsAndSuccess examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/rental/write/rejectrequest/RejectRequestCommandHandlerTest.java:66
- No direct assertions: givenAvailableBikeWhenRequestBikeThenBikeRequested examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/rental/write/requestbike/RequestBikeCommandHandlerTest.java:48
- No direct assertions: givenUnregisteredBikeWhenRequestBikeThenRejected examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/rental/write/requestbike/RequestBikeCommandHandlerTest.java:64
- Duplicated predicate migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:329
- Duplicated predicate migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:454
- Duplicated predicate migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:135
- Duplicated predicate update/src/main/java/org/axonframework/update/configuration/PropertyFileUsagePropertyProvider.java:113
- Duplicated predicate modelling/src/main/java/org/axonframework/modelling/entity/annotation/RoutingKeyCommandTargetResolverDefinition.java:55
- Duplicated predicate migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:152
- Duplicated predicate migration/src/main/java/org/axonframework/migration/AddEventAnnotation.java:109
- Duplicated predicate migration/src/main/java/org/axonframework/migration/ConvertCommandHandlerConstructorToCompanionObject.java:162
- Duplicated predicate migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:254
- Duplicated predicate migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:427
- Duplicated predicate migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:372
- Duplicated predicate migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:140
- Duplicated predicate migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:332
- Duplicated predicate modelling/src/main/java/org/axonframework/modelling/entity/ConcreteEntityMetamodel.java:159
- Duplicated predicate modelling/src/main/java/org/axonframework/modelling/entity/ConcreteEntityMetamodel.java:143
- Duplicated predicate migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:298
- Duplicated predicate migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:290
- Duplicated predicate migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:249
- Duplicated predicate common/src/main/java/org/axonframework/common/util/PriorityCallable.java:79
- Duplicated predicate messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenEntry.java:203
- Duplicated predicate messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/ProcessorEventHandlingComponents.java:143
- Duplicated predicate migration/src/main/java/org/axonframework/migration/MarkSagaResourceInjection.java:214
- Duplicated predicate migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:831
- Duplicated predicate migration/src/main/java/org/axonframework/migration/AddAxonTestFixtureTearDown.java:204
- Disabled test common/src/test/java/org/axonframework/common/configuration/ApplicationConfigurerTestSuite.java:668
- Disabled test common/src/test/java/org/axonframework/common/configuration/ApplicationConfigurerTestSuite.java:699
- Disabled test eventsourcing/src/test/java/org/axonframework/eventsourcing/eventstore/StorageEngineBackedEventStoreTestSuite.java:249
- Disabled test extensions/spring/spring-boot-autoconfigure/src/test/java/org/axonframework/extension/springboot/AxonHandlerConfigurationTest.java:49
- Disabled test extensions/spring/spring-boot-autoconfigure/src/test/java/org/axonframework/extension/springboot/autoconfig/InterceptorAutoConfigurationTest.java:73
- Disabled test extensions/spring/spring-boot-autoconfigure/src/test/java/org/axonframework/extension/springboot/autoconfig/InterceptorAutoConfigurationTest.java:97
- Disabled test extensions/spring/spring-boot-autoconfigure/src/test/java/org/axonframework/extension/springboot/autoconfig/InterceptorAutoConfigurationTest.java:122
- Disabled test extensions/spring/spring-boot-autoconfigure/src/test/java/org/axonframework/extension/springboot/autoconfig/RepositoryWiringTest.java:40
- Disabled test messaging/src/test/java/org/axonframework/messaging/core/ConcatenatingMessageStreamTest.java:126
- Disabled test messaging/src/test/java/org/axonframework/messaging/core/OnErrorContinueMessageStreamTest.java:68
- Disabled test messaging/src/test/java/org/axonframework/messaging/core/annotation/AnnotatedHandlerAttributesTest.java:143
- Disabled test messaging/src/test/java/org/axonframework/messaging/core/interception/ExceptionHandlerTest.java:141
- Disabled test messaging/src/test/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessorTest.java:613
- Disabled test messaging/src/test/java/org/axonframework/messaging/queryhandling/FutureAsResponseTypeToQueryHandlersTest.java:140
- Disabled test messaging/src/test/java/org/axonframework/messaging/queryhandling/FutureAsResponseTypeToQueryHandlersTest.java:154
- Disabled test messaging/src/test/java/org/axonframework/messaging/queryhandling/annotation/InterceptingAnnotatedQueryHandlingComponentTest.java:51
- Disabled test modelling/src/test/java/org/axonframework/modelling/entity/annotation/AnnotatedEntityMetamodelCommandHandlerInheritanceTest.java:114
- Orphaned file extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/core/interception/ReactorDispatchInterceptorRegistry.java:1
- Orphaned file extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/core/interception/DefaultReactorDispatchInterceptorRegistry.java:1
- Orphaned file extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/commandhandling/gateway/DefaultReactorCommandGateway.java:1
- Orphaned file extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/queryhandling/gateway/DefaultReactorQueryGateway.java:1
- Orphaned file extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/queryhandling/gateway/ReactorQueryGateway.java:1
- Orphaned file extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/eventhandling/gateway/DefaultReactorEventGateway.java:1
- Orphaned file extensions/spring/spring-boot-autoconfigure/src/main/java/org/axonframework/extension/springboot/autoconfig/ReactorAutoConfiguration.java:1
- Orphaned file extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/core/configuration/ReactorConfigurationDefaults.java:1
- Orphaned file messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jpa/JpaTokenStoreConfiguration.java:1
- Orphaned file extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/commandhandling/gateway/ReactorCommandGateway.java:1
- Orphaned file extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/eventhandling/gateway/ReactorEventGateway.java:1
- Orphaned file messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/LegacyTokenTypeMapper.java:1
- Orphaned file extensions/spring/spring/src/main/java/org/axonframework/extension/spring/data/JacksonPageDeserializer.java:1
- Orphaned file extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/core/interception/ReactorDispatchInterceptorFactory.java:1
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- Off-boarding risk: anonymized user #3
- Off-boarding risk: anonymized user #4
- Off-boarding risk: anonymized user #5
- Off-boarding risk: anonymized user #6
- Further sole-owners (lower concentration)
- Projects may be oversized for their cohesion
- High interface indirection
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- Large public API surface
- Logging is not universal
- No SAST REDACTED:4
- No changelog
- Interpolated log message defeats structured logging eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/jpa/JpaPollingEventCoordinator.java:138
- Java packages are not null-marked everywhere
- Silent fallback default in catch update/src/main/java/org/axonframework/update/detection/KotlinVersion.java:49
Minor — 4 finding(s)
- Skipped (documented): nextThenMapTest messaging/src/test/java/org/axonframework/messaging/core/MessageStreamTestSuite.java:280
- Skipped (documented): nextThenReduceTest messaging/src/test/java/org/axonframework/messaging/core/MessageStreamTestSuite.java:271
- Skipped (documented): peekThenMapTest messaging/src/test/java/org/axonframework/messaging/core/MessageStreamTestSuite.java:289
- Skipped (documented): peekThenReduceTest messaging/src/test/java/org/axonframework/messaging/core/MessageStreamTestSuite.java:298
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-dc338a975dc34ae28bf26f8b056b5c6b/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-dc338a975dc34ae28bf26f8b056b5c6b/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 51 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 0 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 14 file(s) — `common/src/main/java/org/axonframework/common/ReflectionUtils.java`, `common/src/main/java/org/axonframework/common/infra/FilesystemStyleComponentDescriptor.java`, `eventsourcing/src/main/java/org/axonframework/eventsourcing/annotation/reflection/AnnotationBasedEventSourcedEntityFactory.java`, `eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/AggregateSequenceNumberPosition.java`, `eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/DefaultSourcingCondition.java`, … (+9 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | — |