I'm trying to upgrade my spring + jpa(hibernate) application to JBoss 5 and am noticing that hibernate is not finding any of my entities. It works fine when I run it outside of the container inside a unit test, but once inside the container it doesn't find my entities. Has anyone experienced anything like this? I'm using the built in hibernate jars and not including any in my war. I'm wondering if it has something to do with those classes being loaded outside of the webapp classloader?

Daniel

I can work around this issue by listing the classes in my peristence.xml file. Any suggestions on why the annotation scanning might work in my unit tests but not within JBoss 5 would be greatly appreciated though.

Daniel

I am having a similar problem when upgrading from Jboss 4.2.3. Works with JBoss 4.2.3, but fails with JBoss 5.X. I am not using Spring.

I fixed my problem by converting my war to a ear and putting my entities in a ejb jar file.

Putting them in an ejb jar file is definitely going to work because they are now being managed by the container and are first class ejb3 beans. In my case, I don't want the container to manage the life cycle of my JPA entities. I have aspects of my code base that needs to be self-contained and run with and without an ejb3 container and I don't want to have different configurations for each deployment environment. My configuration works just fine under JBoss 4 without having to list all of the classes in my persistence xml file.