Skip to content

SPR-14901 Allow customization of STOMP message header encoding #1236

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

dreis2211
Copy link
Contributor

@dreis2211 dreis2211 commented Nov 11, 2016

@dreis2211 dreis2211 force-pushed the stomp-header-encoding branch from 43f650c to 5245328 Compare November 11, 2016 20:48
@dreis2211 dreis2211 changed the title Allow customization of STOMP message header encoding SPR-14901 Allow customization of STOMP message header encoding Nov 11, 2016
@rstoyanchev
Copy link
Contributor

Could we go without the STOMP codec registration? I had the impression you were okay with the latest results?

@dreis2211 dreis2211 force-pushed the stomp-header-encoding branch from 479da19 to 0756709 Compare December 3, 2016 19:43
@dreis2211
Copy link
Contributor Author

Finally had some time to work on this again. Please also see my latest comment in the ticket.

@rstoyanchev
Copy link
Contributor

This is now merged and backported to 4.3.x.

Note that I've added synchronization around the cache updates and an additional access-only cache map since the LinkedHashMap cannot be accessed and updated concurrently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants