-
Notifications
You must be signed in to change notification settings - Fork 1.1k
GH-3788 Support byte[] for JMS properties mapping #3789
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
Conversation
Fixes spring-projects#3788 Some JMS vendors carry some important information in their JMS messages. That information can be stored in the specific properties as `byte[]`. * Add `byte[]` as a supported property type into a `DefaultJmsHeaderMapper` * Verify `byte[]` property mapping and propagation via embedded ActiveMQ broker. **Cherry-pick to `5.5.x`**
Cherry-picked to 5.5.x, changed jakarta imports to javax, but getting this error.
We either need to omit the test in 5.5.x or change it to use Artemis. Let me know if you want me to omit the test, or if you want to do the move to Artemis (I am not sure what else had to be changed for that).
|
Sounds like Artemis is OK with |
So, let's consider to not back-port then to avoid possible breaking changes in the behavior! |
Yes, I suppose someone could be relying on a |
Fixes #3788
Some JMS vendors carry some important information in their JMS messages.
That information can be stored in the specific properties as
byte[]
.byte[]
as a supported property type into aDefaultJmsHeaderMapper
byte[]
property mapping and propagation via embedded ActiveMQbroker.
Cherry-pick to
5.5.x