ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-2422) Unable to deserialize BinaryObjectBuilder
Date Fri, 20 Jan 2017 20:06:27 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15832334#comment-15832334

Vladimir Ozerov commented on IGNITE-2422:

It has nothing common with serialization. It is used to build everything in one hop, and to
handle situations when two objects (builders) refer to each other.

> Unable to deserialize BinaryObjectBuilder
> -----------------------------------------
>                 Key: IGNITE-2422
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2422
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 1.5.0.final
>            Reporter: Denis Magda
>            Assignee: Maksim Kozlov
>              Labels: important
>             Fix For: 2.0
>         Attachments: ExampleNodeStartup.java
> Presently it's possible to serialize {{BinaryObjectBuilder}} but it will lead to the
errors at deserialization stage.
> After a brief investigation I see that this happens because neither {{org.apache.ignite.binary.BinaryObjectBuilder}}
nor {{org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl}} presents in {{META-INF/classnames.properties}}
> If you try to update {{ignite/modules/core/src/main/resources/META-INF/classnames.properties}}
by building the project from scratch and copying-pasting generated content from built {{classnames.properties}},
then you will still see that there are still no entries for  {{org.apache.ignite.binary.BinaryObjectBuilder}}
nor {org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl}}.
> Looks like that {{ClassesGenerator}} misses these and other possible classes by some

This message was sent by Atlassian JIRA

View raw message