|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
Steve Ebersole, decision to make here...
If an app tries to create a SF using the ServiceRegistryBuilder, BootstrapServiceRegistryImpl (and therefore ClassLoaderServiceImpl) do not know about the OsgiClassLoader.
1.) Have hibernate-osgi register an OSGi Service w/ a contract allowing SF and EMF creation using the OSGiClassLoader.
2.) Have hibernate-osgi provide a BootstrapServiceRegistry (or higher up – the ServiceRegistryBuilder itself), giving OsgiClassLoader to the ClassLoaderService, and require that apps use that during SF creation.
3.) As previously discussed, we had to set a static var to get the OSGiClassLoader into the ReflectHelper. A static bandaid would need to be used in the bootstrap as well, until re-worked in Hibernate 5.