I recently upgraded from Rave 0.5 to Rave 0.8. The changes introduced in
RAVE-345 caused major issues during the upgrade process. The problem is that the User and Person class are both in the same package/artifact (rave-core) but in different persistence units (persistence.xml). User is in the persistence unit of rave-core while Person is in the persistence unit of rave-shindig. This caused all kinds of classloading errors on JBoss application server .
RAVE-345 made Person a first-class Rave concept I think it is wise to also move the repository to rave-core. In the process I also moved ApplicationData to rave-core.
With these changes I'm currently able to deploy Rave in JBoss, as was the case when using 0.5. Please see attached patch. Note there's one minor issue with the patch, 2 tests in AbstractJpaRepositoryTest fail.
With OpenJPA as the persistence provider, no Hibernate involved.