CacheWriterTest.shouldWriteThroughUsingInvoke_setValue_CreateEntryThenRemove asserts writer delete not called

[cruftex]

The test sets and removes a value via the EntryProcessor, that is not yet existing in the cache and asserts:

    assertEquals(0, cacheWriter.getWriteCount());
    assertEquals(0, cacheWriter.getDeleteCount());

The Spec says that a Cache.remove() should always call writer.delete() if write trough is enabled, and the MutableEntry.remove() should behave identical. However, in this case the TCK asserts that the remove had no effect.

Probably the TCK interprets that the "net effect" of the operation is none, but that is only correct regarding the cache state.

[cruftex]

Probably it is better to change and clarify the Spec and not change all existing implementations. Reviewed the EntryProcessor JavaDoc carefully and opened an issue against the Spec.

[gregrluck]

Looks like Jens is correct on this. How does Coherence work on this point?

[cruftex]

Decided to updated the Spec and close this.