Skip to content

fix: read the OAS 3.1 type back for every schema subclass - #3348

Merged
bnasslahsen merged 1 commit into
spring-boot-3from
backport/3314-schema-type-deserializer
Sep 6, 2026
Merged

fix: read the OAS 3.1 type back for every schema subclass#3348
bnasslahsen merged 1 commit into
spring-boot-3from
backport/3314-schema-type-deserializer

Conversation

@bnasslahsen

Copy link
Copy Markdown
Collaborator

Backport of #3344 to the Spring Boot 3 line.

The type deserializer was only registered for JsonSchema, so cloning any other schema subclass still failed and logged a Json Processing Exception warning for every constrained parameter.

Extend the swagger-core mixin so that it can be registered on Schema itself without dropping the serialization it declares, register it on the standalone mappers too, and carry the deserializer over to the sorting mixin that replaces it.

Fixes #3314

The type deserializer was only registered for JsonSchema, so cloning any
other schema subclass still failed and logged a Json Processing Exception
warning for every constrained parameter. Extend the swagger-core mixin so
that it can be registered on Schema itself without dropping the
serialization it declares, register it on the standalone mappers too, and
carry the deserializer over to the sorting mixin that replaces it.

Fixes #3314

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@bnasslahsen
bnasslahsen merged commit e167d6f into spring-boot-3 Sep 6, 2026
1 check passed
@bnasslahsen
bnasslahsen deleted the backport/3314-schema-type-deserializer branch September 6, 2026 09:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant