On 03/28/2017 11:30 AM, Scott Marlow wrote: > Hi, > > Would it be possible for a WildFly deployment unit processor to detect > Hibernate ORM native applications, by detecting the presence of a > particular configuration file that is always present? I'm not sure if > this is possible, but if it is, perhaps WildFly could automatically > add the (supported) Hibernate orm module to the native application, if > the deployment is clearly marked as a Hibernate native application, as > well as also exporting Javassist to the deployment.
A related question, is there a standard Hibernate annotation class that native Hibernate applications always use that we could scan for the same reasons, as an alternative to scanning for Hibernate configuration files? > > Thoughts? > > Scott > > > > On Fri, Oct 28, 2016 at 9:44 AM, Scott Marlow <smar...@redhat.com> wrote: >>>> Right, Hibernate ORM's module should be the one exposing it, not the >>>> application nor JipiJapa. >>> JipiJapa has zero to do with this, we will create a pr later today to >>> remove the unneeded dependencies, which has nothing to do with this >>> conversation. >> https://github.com/wildfly/wildfly/pull/9305 is for removing the >> unused Javassist dependency from JipiJapa. Also removed a few other >> unused dependencies. _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
