Let's say I have a running Ignite Service that instantiates instances of an interface via the Class.forName(..) method, where the name of the implementing class is read from a configuration file that exists in a distributed cache. Upon initial deployment of the Ignite Service all implementations of the interface exists in the same jar. Now I have a new implementation of the service in a different jar file. What's the best approach to ensure the next time Class.forName(..) gets called with that new implementing class name, the class gets picked up? Would it require me to start a new Ignite Service node with that new jar copied into the lib folder?
-- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/About-peer-class-loading-tp416p820.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
