[
https://issues.apache.org/jira/browse/RAVE-509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13236610#comment-13236610
]
Jasha Joachimsthal commented on RAVE-509:
-----------------------------------------
Hi Richard,
The OpenSocial Person can have a different persistence than the portal User. In
our demo setup we have stored both in the same table. The portal retrieves the
data as User, the OpenSocial container Shindig retrieves the data as Person.
Due to the refactored project setup of RAVE-524 your patch doesn't work
anymore. Failing unit tests are imo not minor issues, but blocking for applying
the patch.
What are the classloading errors in JBoss? Tomcat (6) doesn't seem to have them.
Jasha
> 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
> Fix For: 0.10-INCUBATING
>
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
