On 06 Feb 2014, at 14:52, Steve Ebersole <st...@hibernate.org> wrote:
> > On Thu, Feb 6, 2014 at 7:01 AM, Emmanuel Bernard <emman...@hibernate.org> > wrote: > For OGM the impact is less but in > Integrator.integrate > we use Configuration to be able to conditionally add a naming strategy > configuration.setNamingStrategy(). > See this actually illustrates the problems with Configuration, so thanks for > that :). Setting the naming strategy there would have had no effect because > its "too late in the game". And there is really no corollary in the new code > because of that (setting the naming strategy is available earlier). > You are right, it looks like we do set it in our custom persistence provider impl for JPA and in OgmConfiguration otherwise. How can I set naming strategy in a transparent fashion to people in the new code way? OgmConfiguration will be gone in the new scheme. _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
