[ 
https://issues.apache.org/jira/browse/CONNECTORS-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16258247#comment-16258247
 ] 

Karl Wright commented on CONNECTORS-1356:
-----------------------------------------

I updated everything and now indeed the trunk CMIS connector test fails in 
exactly the same way: the deletion doesn't seem to be taking place.

I committed the changes to trunk with that part of the test disabled.  I think 
what we need to do is understand what the chemistry server is doing with that 
deletion -- I suspect it's creating a grave marker and not deleting it.  If so, 
the change we need to make to the connector would be to only queue objects that 
aren't marked as "deleted".  [[email protected]], is there anything 
in the CMIS spec for documents that are marked as "deleted"?


> Initial implementation of the CMIS Output Connector
> ---------------------------------------------------
>
>                 Key: CONNECTORS-1356
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-1356
>             Project: ManifoldCF
>          Issue Type: Task
>          Components: CMIS Output Connector
>            Reporter: Piergiorgio Lucidi
>            Assignee: Piergiorgio Lucidi
>             Fix For: ManifoldCF 2.9
>
>         Attachments: CMISOutputConnectorSettings.png, 
> ResultWithTimestampTreeOnTargetRepo.png, SourceRepoFolder.png
>
>   Original Estimate: 672h
>  Remaining Estimate: 672h
>
> After we have discussed about the possibility to have some output connector 
> dedicated to migrate contents from a specific repo to another one, this is 
> the first implementation for the CMIS protocol.
> The discussion is the following:
> http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201611.mbox/%3CCAEO2op-bjNv4xSTPwGN%3DV2v47Sy8d%2BwKNtd1RpV2PC85y_JAgw%40mail.gmail.com%3E
> The main scenario is migrate contents from any repository type to a 
> CMIS-compliant repo.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to