[
https://issues.apache.org/jira/browse/CMIS-722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13776180#comment-13776180
]
linzhixing commented on CMIS-722:
---------------------------------
I tested the method, but how can I get the latest change token from the
result(ItemIterable<ChangeEvent>)?
Indeed, I was able to find that "ExtendedHolder<String> changeLogTokenHolder"
or "nextlink" is defined in AbstractPageFetcher<ChangeEvent>, in
SessionImpl.java.
But I don't figure out how to access AbstracgPageFetcher<ChangeEvent> itself...
Iterating ItemIterable<ChangeEvent> object only resulted in ennumerating change
events as much as I specified as maxNumItems.
> 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