We are currently migrating from Jboss EAP 6.4 to Jboss EAP 6.4.12 with Overlays deployment enabled. Now our application is not deploying properly.
We are using customized hiberate for our application purpose, in 6.4 the deployment was working fine when we replace the provided hibernate modules with our own jar's. We are using hibernate 4.2.18.
In 6.4.12, we did the same but Jboss is always referring the hibernate module in the .overlays location. We tried the following approaches but nothing seems to be working.
1) Tried shipping the customized hibernate jar's as part of our ear and excluded the hibernate module by updating the jboss-deployment-structure.xml, but Jboss is still picking the hibernate jar;s from the overlays location.
2) Tried creating our own module for hibernate and specified the same in the persistence.xml using "jboss.as.jpa.providerModule" property but Jboss is still picking the hibernate jar;s from the overlays location.
3) At last we tried repalcing the hibernate jars in the .overlays module and now the deployment is working fine.
Our intention here is to either using the hibernate jar's provided as part of the EAR or to use our custom hibernate module instead of disturbing the default hibernate module.
Can someone guide us on how to achieve this expected behavior.