[ https://issues.apache.org/jira/browse/IGNITE-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874436#comment-15874436 ]
Vladimir Ozerov commented on IGNITE-2422: ----------------------------------------- [~dreamx], I am not sure if the fix is correct. Passing either {{BinaryObject[]}} or {{BinaryObjectBuilder[]}} to builder should be semantically equal to passing {{Object[]}} to normal object. As you set component type ID to {{BInaryObject}} I suspect we will not be able to deserialize root object correctly. Let's add more tests ensuring that object can be deserialized into it's original form after setting {{BinaryObjectBuilder[]}} to one of it's fields. > Unable to deserialize BinaryObjectBuilder > ----------------------------------------- > > Key: IGNITE-2422 > URL: https://issues.apache.org/jira/browse/IGNITE-2422 > Project: Ignite > Issue Type: Bug > Components: binary > 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}} file. > 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 reason. -- This message was sent by Atlassian JIRA (v6.3.15#6346)