chemistry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Potts (Commented) (JIRA)" <>
Subject [jira] [Commented] (CMIS-479) wrong url parse in the case __main__.RepositoryTest.testGetObjectByPath
Date Tue, 06 Dec 2011 21:21:41 GMT


Jeff Potts commented on CMIS-479:

Not sure if this is the back-end the reporter saw this problem with but I am seeing the issue
when running against FileNet. All other back-ends seem to be fine.

Against FileNet, if you create a folder with a space in it, and then ask that object for its
paths, it will return the space. If you then attempt to use getObjectByPath() and pass in
the path, the repo chokes on the space as shown below:

>>> subFolder.getPaths()
[u'/cmislib/test space']
>>> someOtherFolder = repo.getObjectByPath(subFolder.getPaths()[0])
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/opt/src/chemistry/cmislib/src/cmislib/", line 967, in getObjectByPath
    result = self._cmisClient.get(byObjectPathUrl.encode('utf-8'), **addOptions)
  File "/opt/src/chemistry/cmislib/src/cmislib/", line 208, in get
  File "/opt/src/chemistry/cmislib/src/cmislib/", line 312, in _processCommonErrors
    raise ObjectNotFoundException(error.status, error.url)
cmislib.exceptions.ObjectNotFoundException: Error 404 at
> wrong url parse in the case __main__.RepositoryTest.testGetObjectByPath
> -----------------------------------------------------------------------
>                 Key: CMIS-479
>                 URL:
>             Project: Chemistry
>          Issue Type: Bug
>          Components: python-cmislib
>    Affects Versions: OpenCMIS 1.0.0
>            Reporter: shaoyuliang
>            Assignee: Jeff Potts
>             Fix For: OpenCMIS 1.0.0
> The folder name in the server is separated by the ' ',such as "cmislib RepositoryTest
> The client request parameter is p=/Temp/cmislib+RepositoryTest+1322638268.0 , so get
404 response.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message