>
> org.hibernate.boot.model.naming.ImplicitNamingStrategyComponentPathImpl is
>> the corolary. These may or may not migrate directly due to the *split*.
>> The old NamingStrategy actually covered implicit naming, physical naming
>> and logical naming; whereas we have now split these out into dist
Hi Steve,
On Tue, Sep 15, 2015 at 6:49 PM, Steve Ebersole wrote:
> The naming strategies are giving me a hard time: we used the
>> DefaultComponentSafeNamingStrategy before and there is no real equivalent
>> in ORM 5.
>>
>
> org.hibernate.boot.model.naming.ImplicitNamingStrategyComponentPathImpl
>
> The naming strategies are giving me a hard time: we used the
> DefaultComponentSafeNamingStrategy before and there is no real equivalent
> in ORM 5.
>
org.hibernate.boot.model.naming.ImplicitNamingStrategyComponentPathImpl is
the corolary. These may or may not migrate directly due to the *spl
Hi all,
(starting with kudos to Steve for the 5 release, it's the first problem I
find in my migration journey)
I'm currently working on porting 2 of our existing applications to ORM 5 (I
already ported our template application to start new projects).
The naming strategies are giving me a hard t
