No. And possibly. This is one of those things similar to "use new id generator mappings". For new development I think it probably makes sense for WildFly users to expect JPA-compliant implicit naming. The difficulty is how changing that would affect existing applications.
On Mon, Jul 13, 2015 at 5:37 PM Scott Marlow <smar...@redhat.com> wrote: > Or should WildFly perhaps use > > hibernate.implicit_naming_strategy=org.hibernate.boot.model.naming.ImplicitNamingStrategyJpaCompliantImpl > as the default? > > Scott > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
