From dev-return-17887-archive-asf-public=cust-asf.ponee.io@manifoldcf.apache.org Tue Apr 10 21:35:05 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 7276B180718 for ; Tue, 10 Apr 2018 21:35:04 +0200 (CEST) Received: (qmail 63813 invoked by uid 500); 10 Apr 2018 19:35:03 -0000 Mailing-List: contact dev-help@manifoldcf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@manifoldcf.apache.org Delivered-To: mailing list dev@manifoldcf.apache.org Received: (qmail 63796 invoked by uid 99); 10 Apr 2018 19:35:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Apr 2018 19:35:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 1F986C036E for ; Tue, 10 Apr 2018 19:35:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id f4OXwqA9-6aU for ; Tue, 10 Apr 2018 19:35:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 43B635F1E7 for ; Tue, 10 Apr 2018 19:35:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id A07BBE0110 for ; Tue, 10 Apr 2018 19:35:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 5F36C241C6 for ; Tue, 10 Apr 2018 19:35:00 +0000 (UTC) Date: Tue, 10 Apr 2018 19:35:00 +0000 (UTC) From: "Piergiorgio Lucidi (JIRA)" To: dev@manifoldcf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (CONNECTORS-1356) Initial implementation of the CMIS Output Connector MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CONNECTORS-1356?page=3Dcom.atla= ssian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId= =3D16432816#comment-16432816 ]=20 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 tha= t now tests are running fine and I have tested it using on both sides an Al= fresco 5.2.2 repo.=C2=A0It works correctly also for deleted contents=C2=A0:= D=C2=A0. So using real CMIS servers both the connectors works correctly. You can find the last version of the CMIS Output Connector in the latest=C2= =A0r1828855. I also see during the debugging and the cleanup phase of ManifoldCF integra= tion tests that=C2=A0are removing all the existent contents in the OpenCMIS= Target repository (because in the CMIS Output Connector Integration Test w= e have two OpenCMIS server instances). =C2=A0 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 cr= awler is running for checking the removed content. If we consider that the Repository Connector=C2=A0integration test is confi= gured without an OpenCMIS server as a target repo but it is using a standar= d Null Connection with the=C2=A0TestingOutputConnector. So in both cases we= have an issue on removed contents using the dummy output connector and usi= ng the OpenCMIS In-Memory server... any ideas? =C2=A0 {code:java} public class BaseITHSQLDB extends org.apache.manifoldcf.crawler.tests.BaseI= THSQLDB { =C2=A0 protected CMISServer cmisServer =3D null; =C2=A0 protected String[] getConnectorNames() =C2=A0 { =C2=A0 =C2=A0 return new String[]{"CMIS"}; =C2=A0 } =C2=A0 protected String[] getConnectorClasses() =C2=A0 { =C2=A0 =C2=A0 return new String[]{"org.apache.manifoldcf.crawler.connectors= .cmis.CmisRepositoryConnector"}; =C2=A0 } =C2=A0 =C2=A0 protected String[] getOutputNames() =C2=A0 { =C2=A0 =C2=A0 return new String[]{"Null Output"}; =C2=A0 } =C2=A0 =C2=A0 protected String[] getOutputClasses() =C2=A0 { =C2=A0 =C2=A0 return new String[]{"org.apache.manifoldcf.agents.tests.Testi= ngOutputConnector"}; =C2=A0 } {code} =C2=A0 =C2=A0 =C2=A0 was (Author: piergiorgiolucidi@gmail.com): I'm working on some bugfixes for the CMIS Output Connector and it seems tha= t now tests are running fine and I have tested it using on both sides an Al= fresco 5.2.2 repo.=C2=A0It works correctly also for deleted contents=C2=A0:= D=C2=A0. So using real CMIS servers both the connectors works correctly. I also see during the debugging and the cleanup phase of ManifoldCF integra= tion tests that=C2=A0are removing all the existent contents in the OpenCMIS= Target repository (because in the CMIS Output Connector Integration Test w= e have two OpenCMIS server instances). =C2=A0 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 cr= awler is running for checking the removed content. If we consider that the Repository Connector=C2=A0integration test is confi= gured without an OpenCMIS server as a target repo but it is using a standar= d Null Connection with the=C2=A0TestingOutputConnector. So in both cases we= have an issue on removed contents using the dummy output connector and usi= ng the OpenCMIS In-Memory server... any ideas? =C2=A0 {code:java} public class BaseITHSQLDB extends org.apache.manifoldcf.crawler.tests.BaseI= THSQLDB { =C2=A0 protected CMISServer cmisServer =3D null; =C2=A0 protected String[] getConnectorNames() =C2=A0 { =C2=A0 =C2=A0 return new String[]{"CMIS"}; =C2=A0 } =C2=A0 protected String[] getConnectorClasses() =C2=A0 { =C2=A0 =C2=A0 return new String[]{"org.apache.manifoldcf.crawler.connectors= .cmis.CmisRepositoryConnector"}; =C2=A0 } =C2=A0 =C2=A0 protected String[] getOutputNames() =C2=A0 { =C2=A0 =C2=A0 return new String[]{"Null Output"}; =C2=A0 } =C2=A0 =C2=A0 protected String[] getOutputClasses() =C2=A0 { =C2=A0 =C2=A0 return new String[]{"org.apache.manifoldcf.agents.tests.Testi= ngOutputConnector"}; =C2=A0 } {code} =C2=A0 =C2=A0 =C2=A0 > Initial implementation of the CMIS Output Connector > --------------------------------------------------- > > Key: CONNECTORS-1356 > URL: https://issues.apache.org/jira/browse/CONNECTORS-135= 6 > 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, ResultWithTimest= ampTreeOnTargetRepo.png, SourceRepoFolder.png > > Original Estimate: 672h > Remaining Estimate: 672h > > After we have discussed about the possibility to have some output connect= or 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/%3CCA= EO2op-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)