Update: I grabbed the hibernate code, extracted parts, and here's the
interesting bit:
PersistenceProviderResolver ppr =
PersistenceProviderResolverHolder.getPersistenceProviderResolver();
List<PersistenceProvider> list = ppr.getPersistenceProviders();
On the good machine, the list has the hibernate provider.
On the bad machines, the list is empty.
Ugh.
I even have the provider listed specifically in the persistence unit.
ARGH!
On Thursday, 18 April 2013 16:04:35 UTC-4, Jamie wrote:
>
> This is driving me crazy.
>
> My (large) project uses Hibernate and Postgres.
> On one machine it works perfectly.
>
> On two machines:
> - All works fine when running externally (from the web server)
> - Other (non gwt) programs work fine, using the same eclipse project, same
> classpath, same config (persistence.xml) etc.
> - If I launch my project in GWT debug mode, the following code fails
> immediately:
> emf = Persistence.createEntityManagerFactory("dpu", connectionProperties);
>
> I have confirmed that all the connection properties are the same when
> connecting.
> There are two things that I am considering:
> - The classpath is incorrect
> - GWT is including hibernate code that is interfering with my EMF.
>
> Has anyone ever seen anything like this? I really want to use the
> debugger!!!
> Thanks for your time!
>
> -- Jamie
>
>
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
