See below details about OgmIntegrator not overriding ORM ConnectionProviderInitiator.
On 11/14/2012 11:09 AM, Steve Ebersole wrote: > Integrator is not working why? > >>>>>>>>>>> >>>>>>>>>>> People are still hitting the "Caused by: >>>>>>>>>>> org.hibernate.service.jndi.JndiException: Unable to lookup >>>>>>>>>>> JNDI name >>>>>>>>>>> [---PlaceHolderDSForOGM---]" error. >>>>>>>>>>> >>>>>>>>>>> Since people are still hitting the ---PlaceHolderDSForOGM--- >>>>>>>>>>> induced >>>>>>>>>>> failure (on AS7), we should create a jira for addressing it. >>>>>>>>>>> The >>>>>>>>>>> fix could be to only add ---PlaceHolderDSForOGM--- when >>>>>>>>>>> booting in >>>>>>>>>>> standalone mode but not container. >>>>>>>>>> >>>>>>>>>> The placeholder is there because otherwise, some part of >>>>>>>>>> Hibernate >>>>>>>>>> EntityManager's configuration bootstrap complain. >>>>>>>>>> >>>>>>>>>> But this value should never be used because Hibernate OGM has an >>>>>>>>>> integrator that overrides the ConnectionProviderInitiator with >>>>>>>>>> a Noop >>>>>>>>>> version. >>>>>>>>>> The fact that Sergio's stacktrace shows >>>>>>>>>> >>>>>>>>>> Caused by: org.hibernate.service.jndi.JndiException: Unable to >>>>>>>>>> lookup JNDI name [---PlaceHolderDSForOGM---] >>>>>>>>>> at >>>>>>>>>> org.hibernate.service.jndi.internal.JndiServiceImpl.locate(JndiServiceImpl.java:68) >>>>>>>>>> >>>>>>>>>> at >>>>>>>>>> org.hibernate.service.jdbc.connections.internal.DatasourceConnectionProviderImpl.configure(DatasourceConnectionProviderImpl.java:116) >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> is proof to me that the OgmIntegrator is not taken into >>>>>>>>>> account which >>>>>>>>>> means that the file >>>>>>>>>> META-INF/services/org.hibernate.integrator.spi.Integrator >>>>>>>>>> is not seen by Hibernate ORM when it bootstraps the >>>>>>>>>> application which >>>>>>>>>> means that Hibernate OGM's classpath is not visible where it >>>>>>>>>> should be. >>>>>>>>> >>>>>>>>> I tried adding the Hibernate OGM module to the ORM module >>>>>>>>> classpath and >>>>>>>>> still get the same error (http://pastie.org/5352457). >>>>>>>>> >>>>>>>>>> >>>>>>>>>> That's why I strongly suspects that this is either a JBoss >>>>>>>>>> modules bug >>>>>>>>>> or some misconfiguration of the ogm modules. >>>>>>>>>> >>>>>>>>>> We could try and give a better error report, open an issue for >>>>>>>>>> that but >>>>>>>>>> at the end of the day, something is broken in the ORM-AS >>>>>>>>>> integration wrt >>>>>>>>>> integrator and service discovery. >>>>>>>>>> >>>>>>>>>> Emmanuel >>>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> 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 >>>>> >>>> >> >> _______________________________________________ >> 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
