[jbosstools-dev] Diffenerent interpretation of NamingStrategy methods.

Max Rydahl Andersen max.andersen at redhat.com
Tue Aug 11 10:21:36 EDT 2009


>> The best solution is to check where NS is called inside Hibernate 
>> Annotation and figure that out from here.
>> Here is a summary to get you started:
>> - classToTableName called when the table name is not explicit
>> - propertyToColumnName called when the column is not explicit on a 
>> property
>> - tableName overrides an explicit table name
>> - overrides an explicit column name
>> - collectionTableName called fi the collection table is not explicit
>> - joinKeyColumnName called on a join key (explicit or implicit it seems)
>> - foreignKeyColumnName same for a FK
>> - logicalColumnName returns the name tht should be used in 
>> @Annotations when referencing a given column (eg in @UniqueConstraint)
>> - logicalCollectionTableName same here
>> - logicalCollectionColumnName same here
>>
thanks for that list.
>> That being said, shouldn't you guys use the Hibenate metamodel instead?
sure, can it run on incomplete and possibly non-compiled classes being 
edited live ?

/max


More information about the jbosstools-dev mailing list