HHH-9490 - Migrate from dom4j to jaxb for XML processing;

HHH-9492 - Migrate to new bootstrap API (MetadataSources, etc);
HHH-7078 - Split NamingStrategy into ImplicitNamingStrategy/PhysicalNamingStrategy;
HHH-6005 - Better handling of implicit column naming with @ElementCollection of @Embeddables;
HHH-9633 - Add tests that explicitly test the "main" NamingStrategy impls
This commit is contained in:
Steve Ebersole 2015-03-10 17:10:35 -05:00
parent 9caca0ce37
commit ca31abfe61
1 changed files with 3 additions and 1 deletions

View File

@ -50,4 +50,6 @@ either an additional SecondPass or done in a `ManyToOne#isValid` override of `Si
reason the validation failed (non-unique many-to-one marked for orphan delete) but not the property name/path.
Simply returning false from `ManyToOne#isValid` would instead lead to a misleading exception message, which
would at least have the proper context to know the property name/path.
* Should `org.hibernate.boot.MetadataBuilder` be folded into `org.hibernate.boot.MetadataSources`?
* Should `org.hibernate.boot.MetadataBuilder` be folded into `org.hibernate.boot.MetadataSources`?
* Consider an additional "naming strategy contract" specifically for logical naming. This would be non-pluggable, and
would be the thing that generates the names we use to cross-reference and locate tables, columns, etc.