The default bindings for Java = "java.io.Serializable",
that is also why when you register:
serializers.java = "com.romix.akka.serialization.kryo.KryoSerializer"
you are basically covering all standard Java classes.
The only thing you would need to do for your own classes is make them
implement
I am wondering if this would use the same bindings for all the default JDK
types or if that would be another issue.
On Monday, June 13, 2016 at 3:10:01 AM UTC-5, Guido Medina wrote:
>
> Yes, just change the "java.io.Serializable" binding from "java" to "kryo",
> I'm not at home so can't look th
ahh, sorry, yes, you can have a static.conf, say, your static section of
the config and programmatically you can build your config and include a
static file as a resource,
that's kind of way of mixing static conf with config objects, see Merging
config trees: https://github.com/typesafehub/confi
To look for that key in the config open reference.conf of
akka-remote-2.4.7.jar
On Monday, June 13, 2016 at 9:10:01 AM UTC+1, Guido Medina wrote:
>
> Yes, just change the "java.io.Serializable" binding from "java" to "kryo",
> I'm not at home so can't look the exact key nor copy & paste my c
Yes, just change the "java.io.Serializable" binding from "java" to "kryo",
I'm not at home so can't look the exact key nor copy & paste my config
section for that.
That way any object that implements serializable will be serialize with
Kryo, objects that don't implement Serializable you will hav
