Hi Christian,
About the itests, and your proposal, I think it's a good thing to split
API, model and impl for persistence.
For the dependency cycle, I gonna take a look as I'm working on some
modular enhancement (related to OSGi support).
The only point is (for SYNCOPE-242) to wait the changes in progress
(started by Francesco).
Regards
JB
On 12/06/2012 09:35 AM, Christian Schneider wrote:
Hi Syncope team,
my name is Christian Schneider and I am working together with Jan
Bernhard on the CXF migration of Syncope.
We sometimes have problems running the rest itests in the core project
from eclipse. When looking into the reasons we found that eclipse
sometimes seems to overwrite the enhanced jpa classes with plain ones.
I thought about how to solve this and found that it may be a good idea
to split the persistence model and persistence impl out of core and into
two separate modules.
See: https://issues.apache.org/jira/browse/SYNCOPE-241
So what do you think about this idea? Does it make sense or are there
some good reasons to keep these packages in the core?
While analysing how to do this split I found that there are a lot of
dependency cycles in core. Especially the ones between persistence and
impl impede moving out these packages. So if we agree to move the
persistence we first have to solve the dependency cycles. I have added
another issue to track this:
https://issues.apache.org/jira/browse/SYNCOPE-242
The good thing is that it looks worse than it is. I experimented with
some ways to eliminate the cycles and am pretty sure I can do it. Jan
told me that Francesco is working on a refactoring of the role code. So
I would in any case wait till he has finished his work.
Best regards
Christian
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
