You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chemistry.apache.org by "Florian Müller (JIRA)" <ji...@apache.org> on 2013/01/07 13:08:12 UTC
[jira] [Resolved] (CMIS-208) There is no Capabilities element
within getRepositories response.
[ https://issues.apache.org/jira/browse/CMIS-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Florian Müller resolved CMIS-208.
---------------------------------
Resolution: Won't Fix
> There is no Capabilities element within getRepositories response.
> -----------------------------------------------------------------
>
> Key: CMIS-208
> URL: https://issues.apache.org/jira/browse/CMIS-208
> Project: Chemistry
> Issue Type: Bug
> Components: tck
> Reporter: Alexey Zavizionov
> Fix For: OpenCMIS 1.0.0
>
>
> testQueryURITemplate(org.apache.chemistry.tck.atompub.test.spec.RepositoryServiceTest) Time elapsed: 0.052 sec <<< ERROR!
> java.lang.NullPointerException
> <------>at org.apache.chemistry.tck.atompub.test.spec.RepositoryServiceTest.testQueryURITemplate(RepositoryServiceTest.java:73)
> Because there is no Capabilities element within getRepositories response.
> {code}
> <------>at org.apache.chemistry.tck.atompub.client.CMISClient.getRepository(CMISClient.java:135)
> <------>at org.apache.chemistry.tck.atompub.client.CMISClient.getRepositoryInfo(CMISClient.java:157)
> <------>at org.apache.chemistry.tck.atompub.client.CMISClient.getRepositoryInfo(CMISClient.java:152)
> <------>at org.apache.chemistry.tck.atompub.client.CMISClient.getCapabilities(CMISClient.java:166)
> <------>at org.apache.chemistry.tck.atompub.test.spec.RepositoryServiceTest.testQueryURITemplate(RepositoryServiceTest.java:72)
> {code}
> {code}
> Request req = new GetRequest(serviceUrl); // << Should be there the serviceUrl with cmis repo name, to request getRepositoryInfo
> {code}
> The serviceUrl is for request getRepositories, not for getRepositoryInfo.
> ===============
> {code}
> SPECIFICATION:
> 2.1.1.1 Optional Capabilities
> 58
> 59 Commercial ECM repositories vary in their designs. Moreover, some repositories are designed for a
> 60 specific application domain and may not provide certain capabilities that are not needed for their targeted
> 61 domain. Thus, a repository implementation may not necessarily be able to support all CMIS capabilities.
> A few CMIS capabilities are therefore "optional" for a repository to be compliant. A repository‟s support for
> 62
> 63 each of these optional capabilities is discoverable using the >>> getRepositoryInfo <<< service
> 64
> 2.2.2.1 getRepositories
> 3026
> 2.2.2.1.2 Outputs
> 3030
> 3031 A list of repository information, with (at least) the following information for each entry:
> 3032 ID repositoryId: The identifier for the Repository.
> 3033 String repositoryName: A display name for the Repository.
> 2.2.2.2 getRepositoryInfo
> 3036
> 3037 Description: Returns information about the CMIS repository, the optional capabilities it supports and its
> 3038 Access Control information if applicable. .
> {code}
--
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