[
https://issues.apache.org/jira/browse/IGNITE-28200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov resolved IGNITE-28200.
---------------------------------------
Resolution: Duplicate
This ticket is already done, except for one message, so I close it as a
duplicate of IGNITE-28901.
The ticket listed five messages that used prepareMarshal() / finishUnmarshal().
Four of them no longer do:
* GridDeploymentRequest - IGNITE-28220, then IGNITE-27824;
* GridIoMessage - IGNITE-28286, then IGNITE-28520;
* DataStreamerResponse - IGNITE-28523;
* GridJobExecuteRequest - IGNITE-28520, then IGNITE-28356 (it is a
DeferredUnmarshalMessage now).
The only one left is GridEventStorageMessage, which still implements
MarshallableMessage and still unmarshals its filter by hand. That is exactly
the scope of IGNITE-28901, so the remaining work lives there.
> Use MarshalableMessage for Communication messages
> -------------------------------------------------
>
> Key: IGNITE-28200
> URL: https://issues.apache.org/jira/browse/IGNITE-28200
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladimir Steshin
> Priority: Minor
> Labels: IEP-132, ise
> Fix For: 2.19
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> We should use _MarshallableMessage_ brought in #IGNITE-27414 for the messages
> already using _prepareMarshall()_ / {_}finishUnmarshall(){_}.
> At first look, the message list to revise is:
> * _GridDeploymentRequest_
> * _GridJobExecuteRequest_
> * _GridIoMessage_
> * _GridEventStorageMessage_
> * _DataStreamerResponse_
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
