You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2017/07/10 07:08:05 UTC
[jira] [Updated] (IGNITE-3422) No way to control object
initialization during deserialization/unmarshalling
[ https://issues.apache.org/jira/browse/IGNITE-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov updated IGNITE-3422:
------------------------------------
Fix Version/s: (was: 2.1)
2.2
> 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
> Fix For: 2.2
>
>
> 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
(v6.4.14#64029)