Re: [eclipselink-users] ProviderResolver?

[Shaun Smith <shaun.smith@xxxxxxxxxx>]

Bryan Hunt wrote:

Also, the default ProviderResolver looks for a resource file  "META-INF/services/javax.persistence.spi.PersistenceProvider" which exists in the bundle org.eclipse.persistence.jpa, but since the default ProviderResolver is using the context class loader, it's not found.  How is this all supposed to tie together?  Is this mechanism strictly for the non-OSGi environment?

Yes, the default ProviderResolver is for Java SE, not OSGi.  The OSGi resolver is installed by the Activator when the bundle is started.

Assuming this is the case, how are the bundles supposed to get started in an RCP environment so that the Activator can register the necessary components?

See my previous email on this subject: for a discussion of bundle starting.
   
    Shaun

On Nov 3, 2008, at 6:22 PM, Bryan Hunt wrote:

The Activator in javax.persistence sets the provider resolver to the Activator, but the manifest is set to not automatically activate the bundle.  Is the default provider resolver supposed to be used, or do I manually have to start the bundle?

Bryan
_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users

_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users
  

--



Shaun Smith | Principal Product Manager, TopLink | +1.905.502.3094
Oracle Fusion Middleware
110 Matheson Boulevard West, Suite 100
Mississauga, Ontario, Canada L5R 3P4