{{ message }}
Repository navigation
Fail fast on invalid deliverer configuration - #119
Merged
Merged
Conversation
rawo
self-requested a review
September 28, 2026 08:08
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
MessageDeliverer.typevalues at startup instead of silently replacing a deliverer (Duplicate deliverer types silently select one deliverer #117).OutboxEntryProcessorfor applications that inject it into a customOutboxProcessor. Also accept a customOutboxEntryProcessorthat owns its deliverer without a separateMessageDelivererbean.Verification
main.ktlintCheckforokapi-coreandokapi-spring-boot.This is independent of #116, which concerns claiming entries with unsupported delivery types across instances.