This definitely makes sense to me.
As I already wrote, according to the Jakarta REST Specification, support for JSONB is optional. As a consequence the Jakarta REST TCK must not ENFORCE support for JSONB. What we can do is to add OPTIONAL support to the TCK. Feel free to file
As I already wrote, according to the Jakarta REST Specification, support for JSONB is optional. As a consequence the Jakarta REST TCK must not ENFORCE support for JSONB.
What we can do is to add OPTIONAL support to the TCK. Feel free to file a PR. :-)
-Markus
Am 20.03.2026 um 02:38 schrieb Hantsy Bai:
To provide a consistent experience for JSONB and Faces/Persistence, I think the Jakarta REST TCK should add ser/deser for JSR 310 data types.
Payara declared that it had passed the TCK, but Jakarta REST did not support JSR-310.
—
Reply to this email directly,
view it on GitHub, or
unsubscribe.
You are receiving this because you are subscribed to this thread.
Message
ID: <jakartaee/rest/issues/1339/4094806572@github.com>