[
https://issues.apache.org/jira/browse/SYNCOPE-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538130#comment-13538130
]
Christian Schneider commented on SYNCOPE-241:
---------------------------------------------
I found that I did not have the most current trunk when I created the patch.
Currently I am testing if I can somehow avoid to have a complete db connection
when enhancing the classes.But I get errors like below in the tests.
Any idea what that means? In the logs I see that ExternalResource was enhanced.
Do you know what the openjpa maven plugin does and why it needs the db
connection?
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
Caused by: org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'springContextInitializer' defined in file
[/home/cschneider/checkout/syncope/core/target/classes/org/apache/syncope/core/init/SpringContextInitializer.class]:
Invocation of init method failed; nested exception is
<openjpa-2.2.1-r422266:1396819 nonfatal user error>
org.apache.openjpa.persistence.ArgumentException: An error occurred while
parsing the query filter "SELECT e FROM ExternalResource e". Error message:
The name "ExternalResource" is not a recognized entity or identifier. Perhaps
you meant ExternalResource, which is a close match. Known entity names:
[AbstractSchema, ExternalResource, RAttrUniqueValue, AbstractVirAttr,
Membership, TaskExec, SyncopeConf, Report, RAttr, AbstractExec, SyncopeLogger,
USchema, MAttr, PasswordPolicy, RSchema, MSchema, AbstractMappingItem,
MAttrValue, MAttrUniqueValue, AbstractAttr, AbstractDerSchema,
AbstractVirSchema, UAttr, AccountPolicy, RAttrValue, UAttrValue, ReportExec,
SyncopeUser, ConnInstance, AbstractDerAttr, AbstractAttrValue, SyncopeRole,
UMappingItem, AbstractMapping, SyncPolicy, RMapping, Policy,
ReportletConfInstance, Task, RMappingItem, UAttrUniqueValue, Entitlement,
UMapping]
> Move persistence and persistence impl into separate modules
> -----------------------------------------------------------
>
> Key: SYNCOPE-241
> URL: https://issues.apache.org/jira/browse/SYNCOPE-241
> Project: Syncope
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.0.3-incubating
> Reporter: Christian Schneider
> Fix For: 1.1.0
>
> Attachments: SYNCOPE-241.patch
>
>
> The core module currently contains many parts of syncope. This makes it
> bigger and more complex than necessary.
> A possible modularization is to move the internal model
> (org.apache.syncope.core.persistence*) and the persistence impl
> (org.apache.syncope.core.persistence.impl) out of core and into separate
> modules.
> One big advantage would be that the jpa code enhancements would then run in
> the model module only. Currently we run into some problems in the cxf
> migration when running the rest itests in core that may be caused by eclipse
> overwriting the enhanced classes with plain classes. If the model
> (peristence) classes are in a separate module we could leave it out of
> eclipse and so this would be no issue anymore.
> Another advantage would be that the persistence tests could run in the
> persistence impl module so when working on the core they would not have to
> run each time.
--
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
