Alexey, one more question. In which cases, classLoader won't find Class by class-name?
2017-03-24 10:00 GMT+03:00 Alexey Goncharuk <[email protected]>: > Vyacheslav, > > As for the real scenarios for a class name not be registered, this can > happen when Ignite attempts to register a mapping on a locked topology (for > example, inside a started user transaction) and the primary node for the > corresponding mapping key has left. In this case, the mapping attempt would > throw a topology exception, and marshaller has to write the full class > name. > > --AG > > 2017-03-23 22:20 GMT+03:00 Alexander Paschenko < > [email protected]>: > > > Hi Vyacheslav, > > > > 1: Yes, exactly. > > > > 2: Hash code is written for all BinaryObjects. Starting with Ignite > > 1.9, hashCode implementations of original classes are never used to > > compute hash codes for corresponding binary objects. > > > > - Alex > > > > 2017-03-23 12:58 GMT+03:00 Vyacheslav Daradur <[email protected]>: > > > Following second question. > > > > > > In which cases it needs to write postWriteHashCode? > > > > > > 2017-03-23 12:27 GMT+03:00 Vyacheslav Daradur <[email protected]>: > > > > > >> Hello everyone. > > >> > > >> Please, explain me, in which cases at marshalling after object header > > (24 > > >> bytes) it needs to write Class.getName? > > >> > > >> I understand that it means that this class isn't registered in > > >> BinaryContext, and at deserializing we use it for loading Class with > > >> ClassLoader. > > >> > > >> Please explain real scenarios. > > >> > > >> -- > > >> Best Regards, Vyacheslav > > >> > > > > > > > > > > > > -- > > > Best Regards, Vyacheslav > > > -- Best Regards, Vyacheslav
