Hi all,
Hardy, Gunnar and I started a discussion that is worth more Eyeballs.
It started after the addition of a `regexp` attribute on @Email to be able to
restrict the shape of the email via an extra regexp.
Here is the exchange
> Emmanuel:
> I don't understand. Is this feature different than
BTW I don't know when the properties have been added to URL, but if it's still
possible, I'd use an array on protocol, host, port to be able to do:
@URL(host={"hibernate.org", ""www.hibernate.org"})
On 11 avr. 2012, at 10:52, Emmanuel Bernard wrote:
> Hi all,
> Hardy, Gunnar and I started
On Apr 11, 2012, at 10:52 AM, Emmanuel Bernard wrote:
> When adding a feature, we have always implicitly asked ourselves this pool of
> questions:
>
> 1. Does it feel like the right way of doing things?
>If it's not, we have been prone to wait till we mature on the idea. Take
> collection
On Apr 11, 2012, at 11:11 AM, Emmanuel Bernard wrote:
> BTW I don't know when the properties have been added to URL, but if it's
> still possible, I'd use an array on protocol, host, port to be able to do:
>
>@URL(host={"hibernate.org", ""www.hibernate.org"})
Good point. In retrospect this
On 11 avr. 2012, at 12:03, Hardy Ferentschik wrote:
>>
>> If we go back to our example, @Email(regexp=""^((?!\\.org).)*$") is not
>> really 5 nor even 2 times better than @Email
>> @Pattern((regexp=""^((?!\\.org).)*$")
>
> I am not sure how one would measure this leverage factor so I stay out
> To me, it adds complexity :
>
> - in HV's code but that's not a strong factor in this case
> - more doc
> - as a user looking at @Email when I use it, I have to understand why such an
> option has been added and if I need it
>
> And I don't see why you don't add regexp to CreditCardNumber, Mo
On 11 avr. 2012, at 17:12, Hardy Ferentschik wrote:
>>
>> To me, it adds complexity :
>>
>> - in HV's code but that's not a strong factor in this case
>> - more doc
>> - as a user looking at @Email when I use it, I have to understand why such
>> an option has been added and if I need it
>>
>>
Hi,
> When adding a feature, we have always implicitly asked ourselves this pool of
> questions:
>
> 1. Does it feel like the right way of doing things?
> If it's not, we have been prone to wait till we mature on the idea. Take
> collection element constraints as a good example. We know the r
The main pieces of identifier handling are in place now on the metamodel
branch. Probably still needs some work in terms of building persisters,
etc but what doesn't on that branch ;)
Anyway, one thing in particular I was hoping to get a discussion on is
the org.hibernate.metamodel.spi.binding
