[
https://issues.apache.org/jira/browse/CMIS-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12888148#action_12888148
]
Yue Ni edited comment on CMIS-232 at 7/13/10 9:41 PM:
------------------------------------------------------
No, the problem is about the value of pathSegment token.
In this test case, folder f1, folder f2, document d1 are created. And their
cmis:name are used as pathSegment token when constructing path for the
document. But this might be incorrect according to the spec.
{quote}
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.
{quote}
Repository might use cmis:name for pathSegment token, however, if repository
doesn't use cmis:name as pathSegment token, this case will fail obviously.
There're some possible scenarios that cmis:name is not used as pathSegment
token:
1) Content stream file name is used rather than cmis:name as it is described in
the spec.
2) Repository supports to create document with same cmis:name in a folder,
which means it is inevitable to use other value rather than cmis:name as its
pathSegment since "The pathSegment token for each item MUST uniquely identify
the item in the folder" according to the spec.
was (Author: niyue):
No, the problem is about the value of pathSegment token.
In this test case, folder f1, folder f2, document d1 are created. And their
cmis:name are used as pathSegment token when constructing path for the
document. But this might be incorrect according to the spec.
{quote}
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.
{quote}
Repository might use cmis:name for pathSegment token, however, if repository
doesn't use cmis:name as pathSegment token, this case will fail obviously.
There're some possible scenarios that cmis:name is not used as pathSegment
token:
1) Content stream file name, object id or other property is used rather than
cmis:name.
2) Repository supports to create document with same cmis:name in a folder,
which means it is inevitable to use other value rather than cmis:name as its
pathSegment since "The pathSegment token for each item MUST uniquely identify
the item in the folder" according to the spec.
> RepositoryTest.testGetObjectByPath should use 'pathSegment'
> -----------------------------------------------------------
>
> Key: CMIS-232
> URL: https://issues.apache.org/jira/browse/CMIS-232
> Project: Chemistry
> Issue Type: Bug
> Components: 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.
-
You can reply to this email to add a comment to the issue online.
