Fix Websocket dynamic registration mapping order #3580
Merged
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.
Related to https://stackoverflow.com/questions/67923303/dynamic-registration-of-websocket-output-adapter-is-not-working
By default the
AbstractHandlerMapping
comes with theorder = Ordered.LOWEST_PRECEDENCE
which sortsadded mappings to the end of chain.
At the same time Spring Boot registers a
SimpleUrlHandlerMapping
as a fallback for all not handled requestsleaving our own mapping behind consideration
order = 0
to theIntegrationDynamicWebSocketHandlerMapping
bean registration to let it to beconsulted before
SimpleUrlHandlerMapping
web-sockets.adoc
that@EnableWebsocket
would disable Spring Integration dynamic WebSocketendpoints