RE: Warning about java.time.Ser

2016-01-27 Thread vkulichenko
Andrey, I think this warning is just not needed any more because of binary format. I completely removed it and also fixed the documentation. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Warning-about-java-time-Ser-tp2693p2750.html Sent from the Apache

RE: Warning about java.time.Ser

2016-01-26 Thread Andrey Kornev
25 Jan 2016 03:09:50 -0800 > From: d.lope...@gmail.com > To: user@ignite.apache.org > Subject: Warning about java.time.Ser > > Hi, > > We are using Java 8 and when we define a cache that uses some of the new > classes in the java.time package, so you get the warning: Class >

Re: Warning about java.time.Ser

2016-01-25 Thread Alexey Goncharuk
I think it makes sense to add a native binary marshaller support for such types (at least for platform interoperability standpoint). I will create a ticket. 2016-01-26 3:31 GMT+03:00 vkulichenko : > Agree. I made a fix in master to ignore JDK classes when printing

Warning about java.time.Ser

2016-01-25 Thread DLopez
Hi, We are using Java 8 and when we define a cache that uses some of the new classes in the java.time package, so you get the warning: Class "java.time.Ser" cannot be written in binary format because it either implements Externalizable interface or have writeObject/readObject methods. Please...