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 Steshin (Jira)" <ji...@apache.org> on 2026/05/01 14:16:00 UTC

[jira] [Updated] (IGNITE-28637) Revise using the origin message class loader and serializer.

     [ https://issues.apache.org/jira/browse/IGNITE-28637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Steshin updated IGNITE-28637:
--------------------------------------
    Epic Link: IGNITE-25881

> Revise using the origin message class loader and serializer.
> ------------------------------------------------------------
>
>                 Key: IGNITE-28637
>                 URL: https://issues.apache.org/jira/browse/IGNITE-28637
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Vladimir Steshin
>            Priority: Major
>              Labels: IEP-132, ise
>
> In {_}CoreMessagesProvider{_}, we use resolved class loader for {_}DynamicCacheChangeBatch{_}:
> {code:java}
> withNoSchemaResolvedClassLoader(DynamicCacheChangeRequest.class); {code}
> Actually, this message is quite simple and doesn't require specific class loader. We have to use it because the message holds user-data-customized _DynamicCacheChangeRequest_ which depends on resolved class loader.
> The problem is that we take marshaller and class loader for inner messages from original message being serialized. Instead, we should get serializaer and class loader from current message config/registration in the factory.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)