Feature Request
Currently we're deserializing a JsonObject request body twice:
- one in the
AbstractJerseyJsonLdInterceptor subclasses
- one in the jersey's
MessageBodyReader implementation
this should be changed, not only for performance issues (that could be negligible), but also because it's blocking the migration to Jackson 3, as Jersey 4 is still not providing a module to support jackson 3 out of the box, so passing to a single deserialization+validation managed by EDC that would solve the issue
DR will come
Which Areas Would Be Affected?
e.g., DPF, CI, build, transfer, etc.
Why Is the Feature Desired?
Are there any requirements?
Who will sponsor this feature?
Please @-mention the committer that will sponsor your feature.
Solution Proposal
Register a global MessageBodyReader<JsonObject> and add the "version" attribute to the SchemaType annotation, that will permit the reader implementation to know which validator apply
Feature Request
Currently we're deserializing a
JsonObjectrequest body twice:AbstractJerseyJsonLdInterceptorsubclassesMessageBodyReaderimplementationthis should be changed, not only for performance issues (that could be negligible), but also because it's blocking the migration to Jackson 3, as Jersey 4 is still not providing a module to support jackson 3 out of the box, so passing to a single deserialization+validation managed by EDC that would solve the issue
DR will come
Which Areas Would Be Affected?
e.g., DPF, CI, build, transfer, etc.
Why Is the Feature Desired?
Are there any requirements?
Who will sponsor this feature?
Please @-mention the committer that will sponsor your feature.
Solution Proposal
Register a global
MessageBodyReader<JsonObject>and add the "version" attribute to theSchemaTypeannotation, that will permit the reader implementation to know which validator apply