The ticket is on the radar, but not in immediate plans. The problem might sounds simple at first glance, but we already spent considerable time on implementation and review, because we heavily rely on classes caching, and a lot of internal BinaryMarshaller infrastructure should be reworked to allow for this change. Hopefully, we will have it in Apache Ignite 2.5.
On Thu, Jan 4, 2018 at 2:28 AM, Valentin Kulichenko < [email protected]> wrote: > Ticket is still open. Vladimir, looks like it's assigned to you. Do you > have any plans to work on it? > > https://issues.apache.org/jira/browse/IGNITE-5038 > > -Val > > On Wed, Jan 3, 2018 at 1:26 PM, Abeneazer Chafamo < > [email protected]> wrote: > >> Is there any update on the suggested functionality to resolve cache entry >> classes based on the caller's context first instead of relying on Ignite's >> classloader? >> >> >> >> -- >> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >> > >
