Re: OptimizedClassDescriptor verifyChecksum object set as optional

2015-11-12 Thread 姜 为
Hi Denis, This is not what I want ,but it works for my service. Thank you! Jiang > 在 2015年11月11日,下午9:00,Denis Magda 写道: > > Hi Jiang, > > I'm a bit confused why you can't give different names to the services located > in different modules. If each service has a different name

Re: OptimizedClassDescriptor verifyChecksum object set as optional

2015-11-11 Thread Denis Magda
Hi Jiang, I'm a bit confused why you can't give different names to the services located in different modules. If each service has a different name then my approach will work for you, doesn't it? But if my service is by ModuleA.ExampleServiceImpl call ModuleB.ExampleServiceImpl,

Re: OptimizedClassDescriptor verifyChecksum object set as optional

2015-11-10 Thread 姜 为
Hi Denis: I tried compute.call(new ExampleServiceImplA()); But if my service is by ModuleA.ExampleServiceImpl call ModuleB.ExampleServiceImpl, and ModuleB.ExampleServiceImpl call other complicated service. The ModuleA only has ExampleServiceImpl there is

Re: OptimizedClassDescriptor verifyChecksum object set as optional

2015-11-09 Thread Denis Magda
Hi, +1 to Val. Actually if you have different class names on different machines (DataEntity, ServiceEntity) I don't realize how you can get to the checksum validation stage. In my understanding you should have caught ClassNotFoundException. Provide me with a full runnable example, I'll run a

Re: OptimizedClassDescriptor verifyChecksum object set as optional

2015-11-09 Thread Valentin Kulichenko
Hi, I'm against optional checksum verification. It's not safe, adds one more configuration property and I don't see any use case that can require this. I also don't completely understand what you're trying to achieve. Can you please describe the sequence of serialization/deserialization events th

Re: OptimizedClassDescriptor verifyChecksum object set as optional

2015-11-09 Thread 姜 为
Hi: The implementations name maybe not same. Like my example: class DataEntity { Integer id; string name; Integer age; ….. and other Externalizable.read(in){ if(in.re

Re: OptimizedClassDescriptor verifyChecksum object set as optional

2015-11-09 Thread Denis Magda
Hi, As I understand both servers have different implementations but the names of those implementations are the same, correct? Because otherwise I don't see how your code could get to the point of checksum validation if one implementation's name is ServiceEntity while the other's is DataEntity.

OptimizedClassDescriptor verifyChecksum object set as optional

2015-11-08 Thread 姜 为
Hi guys: I’m using ignite 1.4. In IgniteCompute.call will transfer of an object to the cluster. The object should implement Serializable or Externalizable interface. OptimizedClassDescriptor.read method will check whether the object is in the same class. In my use cas

[jira] [Created] (IGNITE-1854) OptimizedClassDescriptor verifyChecksum object set as optional

2015-11-04 Thread wmz7year (JIRA)
wmz7year created IGNITE-1854: Summary: OptimizedClassDescriptor verifyChecksum object set as optional Key: IGNITE-1854 URL: https://issues.apache.org/jira/browse/IGNITE-1854 Project: Ignite