The Hot Rod and Rest endpoints have different expectations on how data is stored and read back, it's not possible (out-of-the box) to fully read data written by rest from Hot Rod and vice-versa.
At the moment there is no way of asking for an specific format via Hot Rod (this is work in progress), so the only way to make both endpoints work together is to enable compatibility mode, e.g.:
<compatibility enabled="true" />
Thanks for the quick reply, Gustavo.
As recommended I switched on the compatibility mode, but now the output looks like this:
Does this meant some kind of serializer/deserializer is required?
Many thanks for your response.
What kind of objects are you writing to the cache? If you are writing strings or primitives, it should work without extra serializers/deserializers.
I am writing strings (XML); Content type="application/xml" -- see my original post.
Hello arcanemage, the bug should not affect version 9.0.0.Final, but is present on 9.1.x pre-release version.
You should be able to support your use case by following the instructions on [ISPN-7991] Improve Compatibility between Rest and HotRod for text content - JBoss Issue Tracker
The extra step of creating a custom marshaller and deploying it will not be necessary in the version 9.1.0.Final, to be released this Friday.