Consider United Message Encode/Decode Conversion

[hantsy]

Record support is a big feature in Jakarta EE 11.

Unfortunately, when I tried to update my Cargotracker to Jakarta EE 11 and replace the Persistence @Embeddedable class with a record class, but I found if a record field exists in the JMS payload, it will cause an exception that indicates the record class did not implement Serializable.

I would like there exists a united message codec infrastructure to encode/decode varied formats or Mediatypes (JSON, XML, Corb, Probuff, etc), and make the current HTTP/Messaging specifications including REST, WebSocket, JMS, and future RPC, etc. adapt the same MessageCodecs to handle the encoding/decoding work like what it does in the new Spring WebFlux stack.

And make it configurable like spring boot CodecsCustomizer.