GitHub user artnaseef added a comment to the discussion: Path forward for full UTF-8 correctness
My 2 cents - unless there is a problem in the internals of ActiveMQ that create inconsistency there, a solution closer to the clients will keep the complexity of any fix here down. Making a change to client libraries, or even the client connection handling in the broker (ideally with an optional connection setting or similar to choose), can isolate the problem and fix well. Another way to word this: convert the text into the broker's internal standard as early as possible, and convert it back out as late as possible. Also, didn't the initial reporter mention it worked right in one version and then broke in another? If so, what changed? Hope this helps. GitHub link: https://github.com/apache/activemq/discussions/2658#discussioncomment-18905511 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information, visit: https://activemq.apache.org/contact
