Re: [eclipselink-users] M9 osgi problems
Thanks Tom, that worked, though you still need the String constructor
for PersistenceProvider since there is no default constructor anymore,
I passed in my initializer's classname and that worked.
On Wed, Jun 25, 2008 at 8:45 AM, Tom Ware <tom.ware@xxxxxxxxxx> wrote:
> Hi Tim,
> Try using the createEntityManagerFactoryMethod(String, Map) method.
> Something like:
> HashMap properties = new HashMap();
> properties.put(PersistenceUnitProperties.CLASSLOADER, <classlaoder>);
> emf = new PersistenceProvider().createEntityManagerFactory(PU_NAME,
> Starting with M10, the 3 arg createEMF method will no longer be public.
> Tim Hollosy wrote:
>> I upgraded to 3.4 (yay!) and M9 today, and am having problems with the
>> PersistenceProvider changes, the constructor now takes a String
>> I'm creating my EMF like this (This is in a seperate bundle from my
>> persistence unit):
>> EntityManagerFactory emf = new
>> However when it starts I get this exception:
>> Exception Description: An attempt has been made to use PersistenceUnit
>> [com.redacted.plugin.dataeng.ipdata.persist], but no bundle is
>> available that defines that persistence unit.
>> I've tried passing Activator.getClass().getName(), plugin_id of the
>> bundle, and the pu name as initialilzerClassName and I get the same
>> Any ideas? Like I said this method worked great up until M9.
>> As an aside, is there a reason the M9 incubation jar's don't have any
>> source or javadoc in them anymore? Makes it tricky to debug :)
>> eclipselink-users mailing list
> eclipselink-users mailing list