java.time.LocalDate with @Future javax.validation annotation

[abhijitkottur]

The @Future annotation does't seem to have any effect on the json schema.

.
.
.
@Future
private LocalDate date;
.
.
.

The generate schema looks like

.
.
.
"date": {
	"type": "array",
	"items": {
		"type": "integer"
	}
},
.
.
.

Is there any other way to enforce date validation?

[mbknor]

There is currently no support for javax.validation.constraints.Future.

You have two choices:

Send PR with added support for it.

Use the @JsonSchemaInject-annotation to insert the schema-code you want.
https://github.com/mbknor/mbknor-jackson-jsonSchema#flexible

[kog]

I actually considered writing this as part of my earlier javax.validation contributions, but I don't think it's actually possible for v4 schema. I'm not exactly an expert on JSON schema, so if I've missed something, or someone knows how to do this, please do chime in.

Neither JSON nor the json-schema-validation draft spec contain a first-class type for date/time, This means that you get to use either a numeric value (think epochal timestamp) or a string. The validation spec does contain defined formats for dates and times as strings, but that doesn't really help us because a @Future annotation concerns the value of the field.

Without first class support for date/time you can't really do something like "is X after <some date/time>" because you have no way to make the comparison. And even if you could somehow compare it, there's no concept of "now" to compare it to.

I did look at json-schema-org/json-schema-spec#99 as well as the related json-schema-org/json-schema-spec#116, but it looks like these are still open.