> I guess it's best to continue the discussion at BVAL-232.
Replied there.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Hi,
> Do you think we should support the following?
>
> @DateInOrder
> void bookHotel(@NotNull @Valid Customer customer, Date from, Date to);
IMO that would be a useful feature. The following approaches came up
when discussing the idea earlier this year [1]:
1) A generic approach in the spirit o
I've created http://opensource.atlassian.com/projects/hibernate/browse/BVAL-232
On 8 juil. 2011, at 21:02, Kevin Pollet wrote:
> +1
> Good idea!!
>
> --Kevin
>
> Le 8 juil. 2011 à 16:03, Emmanuel Bernard a écrit :
>
>> Do you think we should support the following?
>>
>> @DateInOrder
>> void
+1
Good idea!!
--Kevin
Le 8 juil. 2011 à 16:03, Emmanuel Bernard a écrit :
> Do you think we should support the following?
>
> @DateInOrder
> void bookHotel(@NotNull @Valid Customer customer, Date from, Date to);
>
> ie like we have properly level and class level constraints, we could get
> me
I think you should.
2011/7/8 Emmanuel Bernard
> BTW I forgot but do we support Constructor validation?
>
> On 8 juil. 2011, at 16:02, Emmanuel Bernard wrote:
>
> > Do you think we should support the following?
> >
> > @DateInOrder
> > void bookHotel(@NotNull @Valid Customer customer, Date from,
BTW I forgot but do we support Constructor validation?
On 8 juil. 2011, at 16:02, Emmanuel Bernard wrote:
> Do you think we should support the following?
>
> @DateInOrder
> void bookHotel(@NotNull @Valid Customer customer, Date from, Date to);
>
> ie like we have properly level and class level
Good idea.
On Fri, 08 Jul 2011 16:02:03 +0200, Emmanuel Bernard
wrote:
> Do you think we should support the following?
>
> @DateInOrder
> void bookHotel(@NotNull @Valid Customer customer, Date from, Date to);
>
> ie like we have properly level and class level constraints, we could get
> met
Cool Stuff !! +1
2011/7/8 Emmanuel Bernard
> Do you think we should support the following?
>
> @DateInOrder
> void bookHotel(@NotNull @Valid Customer customer, Date from, Date to);
>
> ie like we have properly level and class level constraints, we could get
> method level constraints receiving a
