Return-Path: X-Original-To: apmail-manifoldcf-dev-archive@www.apache.org Delivered-To: apmail-manifoldcf-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 205A1D610 for ; Wed, 11 Jul 2012 14:38:37 +0000 (UTC) Received: (qmail 17169 invoked by uid 500); 11 Jul 2012 14:38:36 -0000 Delivered-To: apmail-manifoldcf-dev-archive@manifoldcf.apache.org Received: (qmail 17123 invoked by uid 500); 11 Jul 2012 14:38:36 -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 17087 invoked by uid 99); 11 Jul 2012 14:38:35 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Jul 2012 14:38:35 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 57F58142850 for ; Wed, 11 Jul 2012 14:38:35 +0000 (UTC) Date: Wed, 11 Jul 2012 14:38:35 +0000 (UTC) From: "Karl Wright (JIRA)" To: dev@manifoldcf.apache.org Message-ID: <296118141.35668.1342017515363.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (CONNECTORS-470) SharePoint 2010 support MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CONNECTORS-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411576#comment-13411576 ] Karl Wright commented on CONNECTORS-470: ---------------------------------------- bq. I also get "org.apache.axis.ConfigurationException: No service named .... is available" exceptions during crawling too. That's expected if you get them during configuration. bq. Not sure if crawling is fully working I am using Null output and null authority at the moment. Can you look in the Simple History report to see whether any "ingesting" has been done? The null output connector will log all ingestion attempts. bq. Probably not related to this but I saw the following Exception during crawl phase. I wish I knew which service this was coming from. Is there a stack trace? > SharePoint 2010 support > ----------------------- > > Key: CONNECTORS-470 > URL: https://issues.apache.org/jira/browse/CONNECTORS-470 > Project: ManifoldCF > Issue Type: Improvement > Components: SharePoint connector > Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 > Reporter: Karl Wright > Assignee: Karl Wright > Fix For: ManifoldCF 0.7 > > Attachments: CONNECTORS-470.patch, CONNECTORS-470.patch, CONNECTORS-470.patch, Screen Shot 2012-05-31 at 11.21.12 AM.png, pagination.zip, pom.patch, pom.patch > > > See here for list of the SharePoint web services for SharePoint 2010: > http://msdn.microsoft.com/en-us/library/ee705814.aspx -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira