ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anton Vinogradov <avinogra...@gridgain.com>
Subject Re: putting to cache as generic object
Date Wed, 13 Jan 2016 13:18:56 GMT
Hello Ambha,

Seem you need to use BinaryMarshaller (
In this case you can create objects using binary builder and read field's
values using BinaryObject (Reflection like mechanism)

On Wed, Jan 13, 2016 at 7:58 AM, Ambha <ambha.ungrapalli@wipro.com> wrote:

> In our project, we plan to deploy ignite caching as a shared service
> available for other modules. The caching module is visible to all the
> modules but any module's classes are not visible to caching.
> The objects of different components are put into cache, but it requires
> classes of different modules to be on Ignite's classpath.I plan to use
> Reflection like mechanism at ignite server to fetch the property of the
> cached object. But before this Ignite OptmizedMarshaller expects class to
> be
> present in classpath while serializing.  For some security reason I can't
> put other modules classes into Ignite classpath and also can't use
> peerClassLoading. I want a solution which can make ignite to treat objects
> to be cached as generic 'java.lang.Object's and don't expect cached
> object's
> class to be present in Ignite's classpath
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/putting-to-cache-as-generic-object-tp2525.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message