[jira] [Created] (CONNECTORS-777) SharePoint 2010 does not always qualify FileRef fields with proper relative paths

["Karl Wright (JIRA)" <ji...@apache.org>]

Karl Wright created CONNECTORS-777:
--------------------------------------

             Summary: SharePoint 2010 does not always qualify FileRef fields with proper relative paths
                 Key: CONNECTORS-777
                 URL: https://issues.apache.org/jira/browse/CONNECTORS-777
             Project: ManifoldCF
          Issue Type: Bug
          Components: SharePoint connector
    Affects Versions: ManifoldCF 1.3
            Reporter: Karl Wright
            Assignee: Karl Wright
             Fix For: ManifoldCF 1.4


We're seeing instances where SharePoint 2010 (on AWS) does not qualify file references with the expected base-relative URL.  For example:

{code}
DEBUG 2013-09-16 13:02:31,590 (Worker thread '23') - SharePoint: getListItems xml response: '<GetListItems xmlns="http://schemas.microsoft.com/sharepoint/soap/directory/"><GetListItemsResponse xmlns=""><GetListItemsResult FileRef="SitePages/Home.aspx"/></GetListItemsResponse></GetListItems>'
DEBUG 2013-09-16 13:02:31,590 (Worker thread '23') - SharePoint: Checking whether to include document '/SitePages/Home.aspx'
DEBUG 2013-09-16 13:02:31,590 (Worker thread '23') - SharePoint: File '/SitePages/Home.aspx' exactly matched rule path '/*'
DEBUG 2013-09-16 13:02:31,590 (Worker thread '23') - SharePoint: Including file '/SitePages/Home.aspx'
 WARN 2013-09-16 13:02:31,590 (Worker thread '23') - Sharepoint: Unexpected relPath structure; path is '/SitePages/Home.aspx', but expected <list/library> length of 26
{code}

Here, the fact that the FileRef does not start with a "/" may indicate that it should be treated as being relative to the current library URL.  But without more data (and multiple installations) it will be hard to fully test this assumption.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira