manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Piergiorgio Lucidi (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CONNECTORS-1356) Initial implementation of the CMIS Output Connector
Date Tue, 10 Apr 2018 19:35:00 GMT

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

Piergiorgio Lucidi edited comment on CONNECTORS-1356 at 4/10/18 7:34 PM:
-------------------------------------------------------------------------

I'm working on some bugfixes for the CMIS Output Connector and it seems that now tests are
running fine and I have tested it using on both sides an Alfresco 5.2.2 repo. It works correctly
also for deleted contents :D . So using real CMIS servers both the connectors works correctly.

You can find the last version of the CMIS Output Connector in the latest r1828855.

I also see during the debugging and the cleanup phase of ManifoldCF integration tests that are
removing all the existent contents in the OpenCMIS Target repository (because in the CMIS
Output Connector Integration Test we have two OpenCMIS server instances).

 

If you see the images attached named Integration Tests 1,2 and 3 the build successfully ends
during any debug session.

If I run tests with Maven, both the tests fail on the last step when the crawler is running
for checking the removed content.

If we consider that the Repository Connector integration test is configured without an OpenCMIS
server as a target repo but it is using a standard Null Connection with the TestingOutputConnector.
So in both cases we have an issue on removed contents using the dummy output connector and
using the OpenCMIS In-Memory server... any ideas?

 
{code:java}
public class BaseITHSQLDB extends org.apache.manifoldcf.crawler.tests.BaseITHSQLDB
{
  protected CMISServer cmisServer = null;
  protected String[] getConnectorNames()
  {
    return new String[]{"CMIS"};
  }
  protected String[] getConnectorClasses()
  {
    return new String[]{"org.apache.manifoldcf.crawler.connectors.cmis.CmisRepositoryConnector"};
  }
 
  protected String[] getOutputNames()
  {
    return new String[]{"Null Output"};
  }
 
  protected String[] getOutputClasses()
  {
    return new String[]{"org.apache.manifoldcf.agents.tests.TestingOutputConnector"};
  }
{code}
 

 

 


was (Author: piergiorgiolucidi@gmail.com):
I'm working on some bugfixes for the CMIS Output Connector and it seems that now tests are
running fine and I have tested it using on both sides an Alfresco 5.2.2 repo. It works correctly
also for deleted contents :D . So using real CMIS servers both the connectors works correctly.

I also see during the debugging and the cleanup phase of ManifoldCF integration tests that are
removing all the existent contents in the OpenCMIS Target repository (because in the CMIS
Output Connector Integration Test we have two OpenCMIS server instances).

 

If you see the images attached named Integration Tests 1,2 and 3 the build successfully ends
during any debug session.

If I run tests with Maven, both the tests fail on the last step when the crawler is running
for checking the removed content.

If we consider that the Repository Connector integration test is configured without an OpenCMIS
server as a target repo but it is using a standard Null Connection with the TestingOutputConnector.
So in both cases we have an issue on removed contents using the dummy output connector and
using the OpenCMIS In-Memory server... any ideas?

 
{code:java}
public class BaseITHSQLDB extends org.apache.manifoldcf.crawler.tests.BaseITHSQLDB
{
  protected CMISServer cmisServer = null;
  protected String[] getConnectorNames()
  {
    return new String[]{"CMIS"};
  }
  protected String[] getConnectorClasses()
  {
    return new String[]{"org.apache.manifoldcf.crawler.connectors.cmis.CmisRepositoryConnector"};
  }
 
  protected String[] getOutputNames()
  {
    return new String[]{"Null Output"};
  }
 
  protected String[] getOutputClasses()
  {
    return new String[]{"org.apache.manifoldcf.agents.tests.TestingOutputConnector"};
  }
{code}
 

 

 

> 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
>            Priority: Major
>             Fix For: ManifoldCF 2.10
>
>         Attachments: CMISOutputConnectorSettings.png, Integration Test - 1.png, Integration
Test - 2.png, Integration Test - 3.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
(v7.6.3#76005)

Mime
View raw message