[
https://issues.apache.org/jira/browse/CMIS-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Florian Müller resolved CMIS-609.
---------------------------------
Resolution: Fixed
Fix Version/s: DotCMIS 0.5
Thanks for reporting!
> Crash when at the end of iterating through GetChildren() in DotCMIS
> -------------------------------------------------------------------
>
> Key: CMIS-609
> URL: https://issues.apache.org/jira/browse/CMIS-609
> Project: Chemistry
> Issue Type: Bug
> Components: dotcmis
> Affects Versions: DotCMIS 0.5
> Environment: Visual Studio 9.0 (2008)
> Reporter: Matthew Rutledge-Taylor
> Assignee: Florian Müller
> Priority: Blocker
> Fix For: DotCMIS 0.5
>
>
> I'm trying to build a client for connecting to SharePoint via CMIS using
> DotCMIS.
> in my code
> IFolder rootFolder = session.GetRootFolder();
> IEnumerable<ICmisObject> children = rootFolder.GetChildren();
> List<ICmisObject> childrenList = children.ToList();
> an internal server error is thrown when creating the list of ICmisObjects.
> Each of the objects in the library is retrieved successfully. However, in
> the call to CollectionEnumerator.MoveNext() after the last object is
> retrieved, SkipOffset == items.Count, which causes IncrementPage() to be
> called. Ultimately, the HttpWebResponse response =
> (HttpWebResponse)conn.GetResponse() call in Client.Impl.HttpUtils fails,
> throwing an error, presumably because there is no subsequent page of items.
> Here is the request url that is built
> {http://<site>/_vti_bin/cmis/rest/b8520585-9fbe-49fc-a523-2da2ab4e16ab?getChildren&folderID=-1&includeAllowableActions=true&includeRelationships=none&includePathSegment=true&maxItems=100&skipCount=1}
> I tested the same code using the Groovy connector in the workbench:
> Folder rootFolder = session.getRootFolder();
> ItemIterable<CmisObject> children = rootFolder.getChildren();
> List<CmisObject> childrenList = children.toList();
> and it works fine.
--
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
