Re: [OpenCmis] About behaviour of getContentChanges with null token parameter

2015-03-06 Thread Sascha Homeier
Hi Florian, thx for quick response. This makes much more sense now. According to 2): I simply forgot to set the value of the Holder with the latest token on server side. Now all my unit tests shine green ;) Thx for the hint. Cheers Sascha > Am 06.03.2015 um 17:17 schrieb Florian Müller : > >

Re: [OpenCmis] About behaviour of getContentChanges with null token parameter

2015-03-06 Thread Florian Müller
Hi Sascha, The maxItems parameter defines how many entries should be returned (at most). If the client does not specify the maxItems parameter, the server can decide. I agree the spec wording could be better. It should be: "If not specified, then the repository MUST return the first change ev

Re: [OpenCmis] About behaviour of getContentChanges with null token parameter

2015-03-06 Thread Sascha Homeier
2) I am a bit irritated about client library behaviour when getting latestChangeLogToken from ChangeEvent: It seems to always return the token which is passed as argument of method ‚getContentChanges‘. A look inside SessionImpl class confirmed that the token parameter is passed through to creat

[OpenCmis] About behaviour of getContentChanges with null token parameter

2015-03-06 Thread Sascha Homeier
Hello together, I am currently implementing the ChangeLog functionality on server side and have a question concerning the spec conformant behavior of Discovery Service „getContentChanges“: Due to get the very first change event the CMIS spec 1.1 says I need to pass a null changeLogToken parame