|
I have this fixed at least for the test I added previously. Initially, I was getting a column named items_collection&&element_name because org.hibernate.cfg.Ejb3Column#redefineColumnName was passed "items.collection&&element.name" as the propertyName. So in org.hibernate.cfg.Ejb3Column#redefineColumnName I added the following:
if ( propertyName.contains( ".collection&&element." ) ) {
propertyName = propertyName.replace( "collection&&element.", "" );
}
This reduces the propertyName to the more reasonable "items.name". The component-based naming strategy now produces items_name as the column name; the standard naming strategy produces name.
|