Hi Gunnar,

I agree with the implementation of @Past and @Future with the possibility to customize the TZ.

The date can be provided by an external client (e.g. via web service) and it should be possible to validate it against the timezone of the external client (e.g. time of payment to a local branch) or the local server TZ (e.g. international transaction).

Personally I don't see the need to add other types to the validation, they can be easily converted in other Java types (Month -> Integer etc.) or require specific use cases (e.g. HijraEra).

Most of the uses cases that I see ask only the validation of a date (e.g. @Past date for an event, @Future date today for a payment) or (less frequently) date and time.

Cheers


On Tue, Aug 30, 2016 at 2:39 PM, Gunnar Morling <gunnar@hibernate.org> wrote:
Anyone with thoughts/input on supporting the JSR 310 types?

2016-08-25 12:10 GMT+02:00 Gunnar Morling <gunnar@hibernate.org>:
Hi,

I've pushed another proposal to the website [1], it's about adding @Past/@Future support for the date/time types added in Java 8 (java.time.* package, added by JSR 310). The proposal essentially standardizes the proprietary support we had in HV, plus some additions.

Please let me know what you think, especially on the questions towards the end. Either put comments inline on the source on GitHub [2] or let's have a discussion here.

I haven't been using JSR 310 extensively myself, so any feedback by those who have is more than welcome.

Thanks,

--Gunnar




_______________________________________________
beanvalidation-dev mailing list
beanvalidation-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev