Mailing-List: contact dev-help@chemistry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@chemistry.apache.org
Date: Wed, 30 Nov 2011 23:49:39 +0000 (UTC)
From: "Jeff Potts (Resolved) (JIRA)" <jira@apache.org>
To: dev@chemistry.apache.org
Message-ID: 
 <1009811719.28613.1322696979985.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (CMIS-232) RepositoryTest.testGetObjectByPath
 should use 'pathSegment'
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CMIS-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Potts resolved CMIS-232.
-----------------------------

    Resolution: Fixed

Fixed and checked in to head. Also added a getPaths() method to facilitate the refactor of this test.
                
> RepositoryTest.testGetObjectByPath should use 'pathSegment'
> -----------------------------------------------------------
>
>                 Key: CMIS-232
>                 URL: https://issues.apache.org/jira/browse/CMIS-232
>             Project: Chemistry
>          Issue Type: Bug
>          Components: python-cmislib
>            Reporter: Jeff Potts
>            Assignee: Jeff Potts
>            Priority: Minor
>
> Migrated from GC issue #11, Reported by niyue.com, Mar 29, 2010
> RepositoryTest.testGetObjectByPath concatenates an object path by using
> several folder names and document name together, this is incorrect
> sometimes. According to CMIS spec 1.0cd07:
>     Folder and object path segments are specified by pathSegment tokens
> which can be retrieved by all services that take an includePathSegments
> parameter.
>         A pathSegment token MUST not include a '/' character.
>         It is repository specific how a repository chooses the value for
> pathSegment.
>     Repositories might choose to use cmis:name or content stream filename for
> pathSegment token.
>     The pathSegment token for each item MUST uniquely identify the item in
> the folder.

--
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