hibernate-c3p0 and hibernate-proxool have internal packages defined as Private-Package in the MANIFEST. Rather than export them so that Core can get to the providers, or define them as bundle fragments of core, register the providers as services.
Brett, specifically what I mean is that the intention was that a call would be made from classes within the hibernate-c3p0 and hibernate-proxool artifacts which registered org.hibernate.service.jdbc.connections.internal.C3P0ConnectionProvider.class and org.hibernate.service.jdbc.connections.internal.ProxoolConnectionProvider.class with the StrategySelectorService.
My understanding is that that should work. hibernate-c3p0 and hibernate-proxool obviously have access to their own class loaders.
Brett, if you can get to this for Beta1 great. If not, we'll just push it to Beta2.
, with respect to OSGi, there will be a collision since both c3p0 and proxool export the org.hibernate.service.jdbc.connections.internal package. Any issues with refactoring that in master?
, following up with – good catch.
Reopening to add support for ehcache and infinispan