Initial changes on the sharepoint are not tracked if the connector is restarted before the first traversal completes

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start the connector to crawl a document library which contains more than
(2*batchhint) no. of documents.
2. Stop the connector before all the documents from the document library
gets crawled.
3. Make some changes in the documents (from the same document library) that
connector has sent to gsa. Or, delete some of them, expecting delete feeds
will be sent when the connector is restarted.
4. Start the connector.

What is the expected output?
All the changes that has happened when the connector was stopped should be
tracked and reflected in the feeds.

What do you see instead?
Connector proceeds crawling the next set of documents but never tracks the
changes.

Initial Analysis:
Handling of the current scenario is already there in the implementation.
But, there is a miss. While checking for the value of ChangeToken in
ListsWS.getListItemChangeSinceToken() before updating the next change token
value, Change token should also be checked for a blank value and not only
for null. Ref: Line no. 1085.

Original issue reported on code.google.com by th.nitendra on 30 Nov 2009 at 1:11

[GoogleCodeExporter]

This was occurring because the change token value was changed to a blank string 
from
null, when the connector state was getting loaded. The implemenation was 
relying only
on null checks and there was no check for blank value.

Resolved in revision: 
http://code.google.com/p/google-enterprise-connector-sharepoint/source/detail?r=
479
http://code.google.com/p/google-enterprise-connector-sharepoint/source/detail?r=
478

Original comment by th.nitendra on 1 Dec 2009 at 3:22

• Changed state: Fixed

[GoogleCodeExporter]

Verified in 2.4 Release

Original comment by ashwinip...@gmail.com on 14 Dec 2009 at 6:40

• Changed state: Verified