[infinispan-dev] Important feedback for transcoding work - Re: Quick fix for ISPN-7710

@Gustavo, some important info for your transcoding work below: -- Galder Zamarreño Infinispan, Red Hat I was able to easily get around the issue of deploying protostream entity marshallers by simply adding a server tasks that did that: https://github.com/infinispan-demos/swiss-transport-datagrid/blob/master/... In fact, that server tasks acts serves as a way to add domain pojos to the system... So when the server starts receiving data, it can deserialize it without problems. However, there's a potential problem here you might want to consider in your work: If I deploy the add protobuf task, write data, then redeploy the add protobuf task, then retrieve some data, the system blows up because the classloader of the domain POJOs has changed. So you'd start seeing ClassCastException errors... That's why I think that even though in the past we'd store objects in deserialized form, this could be problematic because you're committing to domain objects with a given classloader... The more I think about it, the more I think we should keep data only in binary format in the server. IOW, we should never try to keep it in deserialized format. That way, no matter how many times the domain objects are redeployed, assuming no compile-binary changes, the lazy transcoding would work without problems. The relationship between them is explained here: https://github.com/infinispan-demos/swiss-transport-datagrid#infinispan-s... I would strongly recommend that you give that demo repository a try, you might get new ideas on the work you're doing. Cheers,