[bv-dev] Proposal for supporting new Java 8 date/time types
misterm at gmail.com
Fri Oct 7 15:52:03 EDT 2016
A little bit time drained here. I have it all in my head, but the time to
write it down is scarce.... Hopefully I'll follow on Tuesday or Wednesday.
If you want to split it in two parts so we can do the rest later
(Duration/Period/TemporalAmounts/Comparables) and publish what we have now,
I'd be fine with it.
On Thu, Oct 6, 2016 at 6:32 AM, Gunnar Morling <gunnar at hibernate.org> wrote:
> Hi Michael,
> How is it going with the date/time proposal? Anything we should publish on
> the website?
> Regarding cross-field validation, can you detail your idea around "pair of
> 2016-09-28 16:18 GMT+02:00 Michael Nascimento <misterm at gmail.com>:
>> On Wed, Sep 28, 2016 at 11:10 AM, Gunnar Morling <gunnar at hibernate.org>
>>> For reference, that's the question:
>>> > One of the most common scenarios with date/time types (applies to
>>> ranges of all types
>>> > though) is to have a start and end property for which start must be
>>> (sometimes equal or)
>>> > greater than now and end must be (sometimes equal or) greater than
>>> start. Are we not
>>> > supporting this somehow?
>>> There is no explicit support for this in the spec. Currently you'd have
>>> to write your custom class-level constraint for this sort of cross-field
>>> validation (or use something as @ScriptAssert from the RI).
>> I think my team was using class-level constraints for that before :-(
>>> I definitely see how it's a sore point.
>> It is. It would be really nice to support this, probably for any pair of
>> Comparables. What do you think?
>> beanvalidation-dev mailing list
>> beanvalidation-dev at lists.jboss.org
> beanvalidation-dev mailing list
> beanvalidation-dev at lists.jboss.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the beanvalidation-dev