Correct documentation for userDestinationPrefix in MessageBrokerRegistry
#32272
Conversation
This file contains 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
…Destination in DefaultUserDestinationResolver
spring-projects-issues
added
the
status: waiting-for-triage
rstoyanchev
reviewed
Feb 15, 2024
rstoyanchev
added
status: invalid
|
Actually, I think you're right on the format of the target destination. My apologies! |
rstoyanchev
added
in: messaging
rstoyanchev
changed the title
rstoyanchev
changed the title
userDestinationPrefix in MessageBrokerRegistry
jdicke
approved these changes
Feb 16, 2024
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.
Changes documentation for setUserDestinationPrefix to match getTargetDestination in DefaultUserDestinationResolver
Current documentation is misleading, because the default implementation appends "-user" + sessionId to the actualDestination
@pivotal-cla This is an Obvious Fix