Entity is not mapped error with seam-gen generated project

[tcmartin24]

I created a seam project with seam-gen and had it generate entities and pages (the works) from database tables (mysql).  The resulting crud app worked just fine - in fact, that original app still works fine.  I've since created the same project again (just added a '2' behind original name) and re-generated artifacts from existing database and now the newly gen'd project doesn't work when I want to see any of the XXXList pages (to show lists of records in database).  I get an error saying {entity} is not mapped.  However, the original war file I created from the first app, pointing at the same database, works just fine.  Unfortunately, I no longer have the original project used to create that war file.  I've all but ruled out the database since that original war does work.

[tcmartin24]

Ok, I know a little more about this issue now.  It's looking like it's related to my app server, JBoss 5.  The app that works is also running on JBoss AS 5 but on another machine.  My guess is that I've inadvertently changed something that's had an adverse effect on Hibernate's functionality maybe.  I hate to skirt the issue, but I'm thinking for now, I'm just gonna reinstall JBoss 5 and see if that fixes it.

[tcmartin24]

I've pinpointed this problem further.  I think it has to do with the fact that I'm deploying locally in 'exploded' format versus a war file.  My guess is that Hibernate with JBoss 5 are having trouble scanning the classpath for annotated entities properly in exploded format.  Guess I'm gonna try out JBoss 4.2 and see if I still get this behavior.

[jharting]

You are facing a known problem related to JBoss AS 5. See this JIRA issue for workaround