Using the BinaryObject API, which is used out-of-the-box by Ignite, we get
this exception that I am trying to solve.
We just want a simple in-memory cache, so I am not sure why I would use a
heavy Ignite implementation as an inmem DB with SQL. That is overkill.
And... why would that solve the prob
Kind regards,
Roger Janssen
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
not care about the structure/content of our
model.
I can't give a quick reproducer. I can post our spring configuration class
content, but then you won't have our application and our domain model, so I
don't know if that would be of any help.
Kind regards,
Roger Janssen
--
rrect stating this?
kind regards,
Roger Janssen
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
d?
If Ignite somehow persists information about your classes, how do you then
deploy new versions of your application with model changes and prevent these
kind of problems from happening?
Kind regards,
Roger Janssen
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
