[ https://issues.apache.org/jira/browse/CMIS-722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13768167#comment-13768167
]
Florian Müller commented on CMIS-722:
-------------------------------------
The AtomPub binding doesn't provide a generic way to retrieve the change log token.
See section 3.10.2:
"The ChangeLog Token is specified in the URI specified by the paging link notations. Through
this binding it is not possible to retrieve the ChangeLog Token from the URIs."
And section 3.10.2.1:
"first, next, previous, last Paging link relations as appropriate. ChangeLogToken is incorporated
into the URI specified by the next link relation."
The change log token is somehow encoded in the next link, but a client cannot decode it. Therefore,
OpenCMIS cannot provide this token.
> getContentChanges doesn't renew Holder<String>changeLogToken in AtomPub Client
> ------------------------------------------------------------------------------
>
> Key: CMIS-722
> URL: https://issues.apache.org/jira/browse/CMIS-722
> Project: Chemistry
> Issue Type: Bug
> Components: opencmis-client-bindings
> Affects Versions: OpenCMIS 0.10.0
> Reporter: linzhixing
>
> org.apache.chemistry.opencmis.client.bindings.spi.atompub.DiscoveryServiceImpl#getContentChanges,
which is called from SessionImpl(Line:326), seems not to return a new Holder<String>changeLogToken
argument. When I execute getContentChange from OpenCMIS client, changeLogToken remains the
same as its input value.
> I confirmed that my CMIS server updates Holder<String>changeLogToken to the latest
token in the returned list both in debugging and Atom feed <atom:link rel="next">.
> To see org.apache.chemistry.opencmis.client.bindings.spi.webservices.DiscoveryServiceImpl#getContentChanges(Line:66),
one can find
> setHolderValue(portChangeLokToken, changeLogToken);
> but I can't find any such code in atompub DiscoveryServiceImpl.
> So I suppose some codes should be added that sets a renewed changeLogToken reading from
an atom feed page link.
--
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