EHC ❯ RMISynchronousCacheReplicator should allow non serializable values in replication via. remove

• Type: Bug
• Status: Open
• Priority: 2 Major
• Resolution:
• Component/s: ehcache-core
• Labels:

• Assignee:
• Reporter: mortenno
• Created: April 16, 2010
• Votes: 0
• Watchers: 1
• Updated:

  October 11, 2011
• Resolved:

Description

RMISynchronousCacheReplicator should be fixed to the sourcecode below. This makes the code much more like RMIASynchronousCacheReplicator

______ public void notifyElementPut(final Ehcache cache, final Element element) throws CacheException { if (notAlive()) { return; }

    if (!replicatePuts) {
        return;
    }

    if (replicatePutsViaCopy) {
		if (!element.isSerializable()) \{
            if (LOG.isWarnEnabled()) {
                LOG.warn("Object with key " + element.getObjectKey() + " is not Serializable and cannot be replicated.");
            }
            return;
        }
        replicatePutNotification(cache, element);
    } else {
		if (!element.isKeySerializable()) \{
            if (LOG.isWarnEnabled()) {
                LOG.warn("Object with key " + element.getObjectKey()
                        + " does not have a Serializable key and cannot be replicated via invalidate.");
            }
            return;
        }
        replicateRemovalNotification(cache, (Serializable) element.getObjectKey());
    }
} \_\_\_\_\_\_

Comments

Fiona OShea 2010-09-01

Moving all unresolved “Fix Revision 2.2.1” to fix revision “unknown” as we are releasing Magnum first which is 2.3. Currently not sure which fix version these will actually be in, but they are targeted for Fremantle release

Fiona OShea 2011-02-22

MOving unresolved P2 jiras to Ulloa - to be reviewed by Chris, Fiona, Greg soon