theigl commented on issue #2066:
URL: https://github.com/apache/fury/issues/2066#issuecomment-2663572910
> If you force Fury to use the default JIT/Codegen serializer, the
writeObject/readObject method in SimplePrincipalCollection won't be invoked,
which may be unexpected if users did some special action in those methods.
That makes sense. In this case I reviewed the custom JDK serialization and
it is perfectly fine to use JIT instead.
Unfortunately, your suggested solution does not work for me. The first
argument to `loadCodegenSerializer` is a `Fury` instance, but I only have
access to a `ThreadSafeFury`.
```java
fury.registerSerializer(SimplePrincipalCollection.class,
CodegenSerializer.loadCodegenSerializer(fury,
SimplePrincipalCollection.class));
```
Is there another way?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
