[
https://issues.apache.org/jira/browse/OAK-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14189803#comment-14189803
]
angela edited comment on OAK-2245 at 10/30/14 10:55 AM:
--------------------------------------------------------
hmm... but the import would then fail (irrespective on whether or not we add
the rep:authorizableId property during the import)... and you have to add more
magic to the fvault that knows about the implementation details of jr/oak...
wouldn't it be preferable to keep it simple and document instead that this will
not work? shall i add a verification to the importer instead?
was (Author: anchela):
hmm... but the import would then fail... and you have to add more magic to the
fvault that knows about the implementation details of jr/oak... wouldn't it be
preferable to keep it simple and document instead that this will not work?
shall i add a verification to the importer instead?
> UserImporter should always set the rep:authorizableID
> -----------------------------------------------------
>
> Key: OAK-2245
> URL: https://issues.apache.org/jira/browse/OAK-2245
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Reporter: angela
> Assignee: angela
> Attachments: OAK-2245.patch, oak-2245-additional-tests.patch
>
>
> upon XML import of user/group nodes the UserImporter currently doesn't
> enforce the creation of rep:authorizableID which has been introduced with Oak
> 1.0.
> while this allows to import JR 2.x content packages as they are, it will
> cause the import to fail in case of uuid-conflicts with existing
> authorizables at a different location.
> for this reason and in order to make sure that imported user/group content
> always has the authorizableID set, we should change the user importer to
> verify that an authorizable id property has been imported.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
