[
https://issues.apache.org/jira/browse/IGNITE-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15870003#comment-15870003
]
Vyacheslav Daradur commented on IGNITE-3422:
--------------------------------------------
[~vozerov],
As I understand from dev-list, the user wants to control instantiation of
custom objects. (singleton, specific classes?)
But I suppose I could be wrong.
I like the idea of BinaryReader in constructor, it provides some benefits.
Need to define further actions. I see three ways:
1. Fix current solution with: newInstance(BinaryReader reader)
2. Revert current solution and fix constructor in the BinaryClassDescriptor: to
change rules of determination of the ctor-field (object.hasBinReaderConstr ?
BinReaderConstr : defaultConstr)
3. To invent something else
> 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
(v6.3.15#6346)
