-
Bug
-
Resolution: Done
-
Critical
-
7.0.3.Final, 7.1.0.CR2
When compatibility is enabled, storing a java serialized object with REST, and then retrieving it with Hot Rod results in byte[] being returned instead of the deserilialized object:
java.lang.AssertionError: Expected :org.infinispan.it.compatibility.EmbeddedRestHotRodTest$Person@22cd6f Actual :[B@2ff9eb2a at org.testng.AssertJUnit.fail(AssertJUnit.java:59) at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364) at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80) at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:88) at org.infinispan.it.compatibility.EmbeddedRestHotRodTest.testCustomObjectRestPutHotRodEmbeddedGet(EmbeddedRestHotRodTest.java:217)
This is because when the entry is retrieved by Hot Rod and it's going to marshall it for sending it back to the client, it should check if the entry is already a byte[], in which case it should not touch it.
- causes
-
ISPN-5758 HotRod client try to unmarhall an object on get() no matter whether the put() use a byte[] or not
- Closed