JPQL inconsitency between hibernate and eclipselink?

Looks like EclipseLink is not scanning the portion of your JAR files/classes that contain the Organisation class. Declare it explicitly in persistence. Xml and see what happens.

Looks like EclipseLink is not scanning the portion of your JAR files/classes that contain the Organisation class. Declare it explicitly in persistence. Xml and see what happens: org.eclipse.persistence.jpa.

PersistenceProvider foo.bar.Organisation.

We have multiple jar files with different sets of persistable objects. It turns out hibernate handles this situation differently than eclipse, the easiest way out was to turn on false – James Brown Nov 22 '10 at 1:08 I believe bernate adds annotated @Entity classes that are in the classpath by default unless you tell it not to. That's probably why it worked before.

Ninja's answer is right, but an alternative might be to find an equivalent property for EclipseLink that tells it to find all @Entity classes at runtime. I'm assuming that there is one. – Jim Tough Nov 22 '10 at 1:11 1 Note that exclude-unlisted-classes is not intended for use in J2SE environments (as per the spec), although some implementations do make use of it there ... likely why you see different behaviour that is not covered by the spec.

You don't mention which env you're using – DataNucleus Nov 22 '10 at 8:04.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.