Mailing-List: contact dev-help@chemistry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@chemistry.apache.org
Date: Mon, 7 Jan 2013 12:08:12 +0000 (UTC)
From: =?utf-8?Q?Florian_M=C3=BCller_=28JIRA=29?= <jira@apache.org>
To: dev@chemistry.apache.org
Message-ID: <JIRA.12464514.1273826783184.90035.1357560492644@arcas>
In-Reply-To: <JIRA.12464514.1273826783184@arcas>
References: <JIRA.12464514.1273826783184@arcas>
Subject: [jira] [Resolved] (CMIS-208) There is no Capabilities element
 within getRepositories response.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


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

Florian M=C3=BCller resolved CMIS-208.
---------------------------------

    Resolution: Won't Fix
   =20
> 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.Repositor=
yServiceTest)  Time elapsed: 0.052 sec  <<< ERROR!
> java.lang.NullPointerException
> <------>at org.apache.chemistry.tck.atompub.test.spec.RepositoryServiceTe=
st.testQueryURITemplate(RepositoryServiceTest.java:73)
> Because there is no Capabilities element within getRepositories response.
> {code}
> <------>at org.apache.chemistry.tck.atompub.client.CMISClient.getReposito=
ry(CMISClient.java:135)
> <------>at org.apache.chemistry.tck.atompub.client.CMISClient.getReposito=
ryInfo(CMISClient.java:157)
> <------>at org.apache.chemistry.tck.atompub.client.CMISClient.getReposito=
ryInfo(CMISClient.java:152)
> <------>at org.apache.chemistry.tck.atompub.client.CMISClient.getCapabili=
ties(CMISClient.java:166)
> <------>at org.apache.chemistry.tck.atompub.test.spec.RepositoryServiceTe=
st.testQueryURITemplate(RepositoryServiceTest.java:72)
> {code}
> {code}
> Request req =3D new GetRequest(serviceUrl); // << Should be there the ser=
viceUrl with cmis repo name, to request getRepositoryInfo
> {code}
> The serviceUrl is for request getRepositories, not for getRepositoryInfo.
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> {code}
> SPECIFICATION:
>    2.1.1.1 Optional Capabilities
> 58
> 59 Commercial ECM repositories vary in their designs. Moreover, some repo=
sitories are designed for a
> 60 specific application domain and may not provide certain capabilities t=
hat 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 b=
e compliant. A repository=E2=80=9Fs support for
> 62
> 63 each of these optional capabilities is discoverable using the >>> getR=
epositoryInfo <<< 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 info=
rmation 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 opti=
onal 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 administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira