[
https://issues.apache.org/jira/browse/RAVE-509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485857#comment-13485857
]
Chris Geer commented on RAVE-509:
---------------------------------
Is this still an issue?
> Move Person repository from rave-shindig to rave-core
> ------------------------------------------------------
>
> Key: RAVE-509
> URL: https://issues.apache.org/jira/browse/RAVE-509
> Project: Rave
> Issue Type: Improvement
> Components: rave-core, rave-shindig
> Affects Versions: 0.8-INCUBATING
> Reporter: Richard Kettelerij
> Priority: Critical
> Attachments: rave_jpa_refactoring_trunk.patch
>
>
> 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 (*).
> Since 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
