Register Class Order

[caglartolgatetik]

Hi, I register all Serializable classes with reflection and it works good on both serialize and deserialize. If I remove one of that classes or add a new one, it gives exceptions. I know it should have same register order. As much as, I know Kryo has a registration method, so you can give id for each registered class. I couldn't find but do you have such a method or any plan to implement such a mechanism or any suggestion for solution?

Thanks

[RuedigerMoeller]

it would be possible using e.g. annotations, however in order to avoid backward compat issues you would have to track id collisions manually. A simpler solution would be the ability to "reserve" an Id, so instead of removing a class you just put in an incrementIdCount() or so (or just give null as argument). registering via reflection is dangerous reagrding proper order long term ..

[RuedigerMoeller]

wait what: it's already possible FSTConfiguration::getClassRegistry().registerClass( Class c, int code, FSTConfiguration conf). Warning:

• Id's have to be at least > 10.000 to avoid collisions, better choose a base of like 1_000_000 for your id's.
• note registering silently returns in case the class is already registered