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-3422) No way to control object initialization during deserialization/unmarshalling
Date Thu, 16 Feb 2017 10:25:41 GMT

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

Vladimir Ozerov commented on IGNITE-3422:

[~dmagda], [~daradurvs], 
Could you please explain which problem is addressed in this ticket? Current fix allows users
to define custom factory which will instantiate object without any parameters. I do not think
it is useful for users in any way, neither do Java SE has something similar (except of {{readObject}}
and {{readResolve}} methods, which are called after object is already instantiated.

> No way to control object initialization during deserialization/unmarshalling 
> -----------------------------------------------------------------------------
>                 Key: IGNITE-3422
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3422
>             Project: Ignite
>          Issue Type: Improvement
>          Components: binary, general
>    Affects Versions: 1.6
>            Reporter: Denis Magda
>            Assignee: Vyacheslav Daradur
> Presently there is no way to control instantiation of a {{BinaryObject}} that is being
deserialized. The object is created using {{BinaryClassDescriptor#newInstance}} all the time.
> It makes sense to add {{BinaryConfiguration.setInitializationFactory()}} method that
will provide with such support.
> Use case and details are provided in this discussion
> http://apache-ignite-users.70518.x6.nabble.com/Properly-Immutable-Keys-values-with-Binary-objects-tp6082.html

This message was sent by Atlassian JIRA

View raw message