Ensure we never try to register for the object id "NULL"
commit1cfd39e749afc9bb776a441fdbd05e4b4cff34aa
authornyquist@chromium.org <nyquist@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Fri, 9 Aug 2013 05:01:20 +0000 (9 05:01 +0000)
committernyquist@chromium.org <nyquist@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Fri, 9 Aug 2013 05:01:20 +0000 (9 05:01 +0000)
treeffb53278ae9fa2391e613f0601f87a502e395764
parent80288a2a837b677c2b9d4b47ac79f71645c9184b
Ensure we never try to register for the object id "NULL"

Currently if we choose to register for all model types for cache
invalidation, we also register for the ObjectId "NULL", which does not
exist. This causes errors with syncing the registration state between
client and server, since the server does not accept this ObjectId.

BUG=240535

Review URL: https://chromiumcodereview.appspot.com/22642004

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@216591 0039d316-1c4b-4281-b951-d872f2087c98
sync/android/java/src/org/chromium/sync/internal_api/pub/base/ModelType.java
sync/android/java/src/org/chromium/sync/notifier/InvalidationController.java
sync/android/java/src/org/chromium/sync/notifier/InvalidationService.java
sync/android/javatests/src/org/chromium/sync/notifier/InvalidationServiceTest.java