jakartaee / jakartaee/messaging
Support Record as Payload
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 49
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
When I upgraded my Cargotracker fork to Jakarta EE 11, I encountered an issue with JMS: If the record does not implement Serializabile, it will throw an exception when the message payload is a record or includes a record field.
A simple Serializable requirement is unreasonable for modern applications.
We must consider global message codecs(which support JSON, Cbor, Probuff, XML, etc.) and type converters(which convert between different types) for HTTP and message protocols to unite the behaviors and allow developers to apply them to the current REST, Websocket, Messaging, Faces, etc.
I think the first step is to unite the message codecs in WebScoket and JMS and make the message payload encode/decode configurable.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named; start by reproducing the Jakarta EE 11 JMS failure with a record payload and reviewing the existing JMS and WebSocket codec behavior. Before implementation, narrow the proposal to a specific configurable codec change and define tests showing record payloads work without requiring Serializable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100