You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "MihkelJ (JIRA)" <ji...@apache.org> on 2018/04/17 09:53:00 UTC
[jira] [Commented] (IGNITE-8293)
BinaryUtils#isCustomJavaSerialization fails when only readObject is
declared in a class
[ https://issues.apache.org/jira/browse/IGNITE-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440681#comment-16440681 ]
MihkelJ commented on IGNITE-8293:
---------------------------------
Patch: [^IGNITE-8293.patch]
> BinaryUtils#isCustomJavaSerialization fails when only readObject is declared in a class
> ---------------------------------------------------------------------------------------
>
> Key: IGNITE-8293
> URL: https://issues.apache.org/jira/browse/IGNITE-8293
> Project: Ignite
> Issue Type: Bug
> Components: binary
> Affects Versions: 2.4
> Reporter: MihkelJ
> Priority: Minor
> Attachments: IGNITE-8293.patch
>
>
> Consider this class:
>
> {code:java}
> public class Test implements Serializable {
> private transient AtomicBoolean dirty = new AtomicBoolean(false);
> private void readObject(java.io.ObjectInputStream in) throws IOException, ClassNotFoundException {
> dirty = new AtomicBoolean(false);
> }
> //methods to check and mark class as dirty
> }{code}
> {{isCustomJavaSerialization}} will get a {{NoSuchMethodException}} when trying to grab the {{writeObject}} method and falsely conclude that Test doesn't use custom serialization.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)