-
1. Re: cmissync
jharrop Aug 27, 2015 6:26 AM (in response to jharrop)In the atom response from modeshape-cmis/atom (pasted in the above cmisSync issue 610 at duplicate repository ids break CmisUtils (happens with ModeShape) · Issue #610 · aegif/CmisSync · GitHub), I see 3 copies of:
<app:workspace>
<atom:title>artifacts</atom:title>
<app:collection href="http://52.18.2.246:32771/modeshape-cmis/atom/artifacts/children?id=%5Broot%5D">
:
<cmisra:repositoryInfo>
<cmis:repositoryId>artifacts</cmis:repositoryId>
<cmis:repositoryName>ModeShape</cmis:repositoryName>
:
Is that expected?
-
2. Re: cmissync
jharrop Aug 27, 2015 7:07 PM (in response to jharrop)As Nicolas observes at duplicate repository ids break CmisUtils (happens with ModeShape) · Issue #610 · aegif/CmisSync · GitHub
The CMIS 1.1 specification says:
The service link relation when provided on a CMIS resource MUST point to an AtomPub service document with only one workspace element.
That AtomPub service document MUST then only contain one workspace element which MUST be the workspace representing the repository containing the Atom Entry or Atom Feed document.
The service document MUST contain only one workspace element.
The rest of the specification always speaks about using singular (never plural) about "the workspace element".
Therefore, I guess it is a CMIS implementation bug in ModeShape. Maybe the XML node is indeed just duplicated?
To replicate what I am seeing, build/run a wildfly with modeshape using the following dockerfile:
FROM jboss/wildfly:8.2.1.Final
ENV MODESHAPE_VERSION 4.3.0.Final
EXPOSE 8080
RUN cd wildfly && curl -o modeshape.zip http://downloads.jboss.org/modeshape/$MODESHAPE_VERSION/modeshape-$MODESHAPE_VERSION-jboss-wf8-dist.zip && unzip -q modeshape.zip && rm modeshape.zip
CMD ["/opt/jboss/wildfly/bin/standalone.sh", "-c", "standalone-modeshape.xml", "-b", "0.0.0.0"]
then add a user, then open modeshape-cmis/atom
-
3. Re: cmissync
hchiorean Aug 28, 2015 1:12 AM (in response to jharrop)Please log a JIRA for this, thanks.