Re: [hibernate-dev] hibernate-tools jira HBX-577
Hi, This is my proposal to solve JIRA issue HBX-577 "hbm2java for annotation from existing inheritance mapping" I figured out how-to do "joined-subclass" and "table-per-class-herarchy" but couldn't test it. This solution relies on tag, example: attribute="class-inheritance-type">single-table-per-class-herarchy 1) Please post patches in jira ;) 2) why is a meta attribute needed in meta when you can deduce it from the Configuration ? /max ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Group sequence adjustments
Some comments on groups On Fri, 20 Feb 2009 15:40:21 +0100, Emmanuel Bernard wrote: To implement such ordering, a group can be defined as a sequence of other groups. Each group in a group sequence must be processed sequentially in the order defined b...@groupsequence.value when the group defined as a sequence is requested. Note that a group member of a sequence can itself be composed of several groups via inheritance or sequence definition. In this case, each composed group must respect the sequence order as well. An example would be good here. Showing the exact execution order in the case of group sequence containing say three groups whereof say two have superinterfaces. Groups defining a sequence and groups composing a sequence must not be involved in a cyclic dependency either directly or indirectly, either through cascaded sequence definition or group inheritance. Groups defining a sequence should not directly inherit other groups. In other words, the interface hosting the group sequence should not have any super interface. Groups defining a sequence should not be used directly in constraint declarations. In other words, the interface hosting the group sequence should not be used in a constraint declaration. What does "must not" and "should not" mean in these paragraphs? Should a ValidationException be thrown? Is it up to the provider? --Hardy ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Group sequence adjustments
On Feb 20, 2009, at 16:50, Hardy Ferentschik wrote: Some comments on groups On Fri, 20 Feb 2009 15:40:21 +0100, Emmanuel Bernard > wrote: To implement such ordering, a group can be defined as a sequence of other groups. Each group in a group sequence must be processed sequentially in the order defined b...@groupsequence.value when the group defined as a sequence is requested. Note that a group member of a sequence can itself be composed of several groups via inheritance or sequence definition. In this case, each composed group must respect the sequence order as well. An example would be good here. Showing the exact execution order in the case of group sequence containing say three groups whereof say two have superinterfaces. good idea Groups defining a sequence and groups composing a sequence must not be involved in a cyclic dependency either directly or indirectly, either through cascaded sequence definition or group inheritance. Groups defining a sequence should not directly inherit other groups. In other words, the interface hosting the group sequence should not have any super interface. Groups defining a sequence should not be used directly in constraint declarations. In other words, the interface hosting the group sequence should not be used in a constraint declaration. What does "must not" and "should not" mean in these paragraphs? Should a ValidationException be thrown? Is it up to the provider? yes when I will incorporate exceptions, must not will be accompanied with an exception should not is left to the provider. --Hardy ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Hibernate Search road map
I updated the road map http://www.hibernate.org/357.html#A12 Mass indexing Dictionary / spellchecker support Work on easier query building More like this? Built-in clustering with JBoss cache Statistics custom LockFactory feel free to propose other new features. ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] [Bean Validation] Constraints plural
2009/2/19 Hardy Ferentschik :
> On Wed, 18 Feb 2009 16:35:30 +0100, Emmanuel Bernard
> wrote:
>
>> @Max.Plural( {
>>@Max(30, groups=JoeSixPack.class),
>>@Max(100, groups=PowerUser.class)
>> } )
>
> +1 for this approach from me as well. Instead of Plural we could also
> consider Many or Multiple.
>
> --Hardy
+1 for the inner annotations for me as well, so I don't have to
remember all the plural forms.
I agree with Hardy about "Multiple" or "Many" instead of "Plural", but
being no native speaker
my opinion about it shouldn't matter much.
Sanne
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
