[
https://issues.apache.org/jira/browse/RAVE-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14096915#comment-14096915
]
Stanton Sievers commented on RAVE-1281:
---------------------------------------
Inspecting the classes involved I found that the error is pretty accurate and
UserImpl defines a private String "id" while it's super class PersonImpl
defines a protected String "id". There is thus confusion when deserializing
the data.
If I remove the "id" field from UserImpl, the issue goes away without any
noticeable adverse behavior.
> Data import for MongoDB fails for people
> ----------------------------------------
>
> Key: RAVE-1281
> URL: https://issues.apache.org/jira/browse/RAVE-1281
> Project: Rave
> Issue Type: Bug
> Components: rave-core, rave-mongodb
> Affects Versions: 0.24
> Reporter: Stanton Sievers
>
> When using the the dataImporter bean to initialize the database from a static
> file during integration tests, I'm seeing a failure with the following cause:
> {code}
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name 'dataImporter': Invocation of init method failed; nested exception
> is org.springframework.data.mapping.model.MappingException: Attempt to add id
> property protected java.lang.String
> org.apache.rave.portal.model.impl.PersonImpl.id but already have property
> private java.lang.String org.apache.rave.portal.model.impl.UserImpl.id
> registered as id. Check your mapping configuration!
> {code}
> This appears to only be an issue when using MongoDB and only with certain
> versions of org.springframework.data.mongodb.
--
This message was sent by Atlassian JIRA
(v6.2#6252)