Jackson is ignoring the type validations for the offsetdatetime objects.

[veerachopperla]

We are using jackson for generating the API classes using open api.

below is the attribute spec used in the openapi.

        searchStartDate:
          type: string
          format: date-time
          nullable: true
        searchEndDate:
          type: string
          format: date-time
          nullable: true

When we try to post the API request, if the input for the searchEndDate is giving as Object instead of date-time value the jackson is setting null value to the deserialized object instead of throwing any type validation error.

  "searchEndDate": "2022-12-01T00:00:00.000Z",
    "searchStartDate": {
        "!": "...",
        "Hello": "World"
    }

In the above request body json, the searchStartDate is set as NULL in the deserialized object. We want to throw exception by jackson as the input value is not of type date-time. Can you please suggest how to achieve this.

we tried using the ALLOW_COERCION_OF_SCALARS, but that doesn't help here as it is doing the strict checks only for the primitive types.

Please do suggest is there any way to force jackson to validate these date time objects.

[cowtowncoder]

Ok, first things first: Jackson does not use OpenApi so you are probably not using Jackson: you might be using something that uses Jackson annotations, but if so, there's nothing Jackson can do wrt applicability.

So before being able to help you, we'd need a problem reproduction using Jackson.
Description of your issue with some other library/framework is not sufficient here -- handling may or may not be by Jackson; using whatever configuration setting. We need to be able to reproduce the issue.

Also: many if not most issues are hidden when people disable DeserializationFeature.FAIL_ON_UNKNOWN_PROPERTIES -- for reproduction make sure not to disable that.