Re: [ecf-dev] Issue adding custom serialization to ecf provider

[Peter Hermsdorf <peter.hermsdorf@xxxxxxxxx>]

Hi, again,

Am 02.05.2017 um 09:12 schrieb Peter Hermsdorf:

Hmm.   Would adding a no-arg constructor to RemoteServiceRegistrationImpl.Properties help?   That could be done pretty easily, but I'm not sure if that will work with Kryo's deserialization behavior.

i.e. something like:

protected Properties() {
    super();
}

with that change it is now possible to use kryo as serialization framework.  the other problem i had was about serializing/deserializing Throwable's (for reference: problem and workaround described here: https://groups.google.com/forum/#!topic/kryo-users/9xOngIaZdO4/discussion)
If that change would be acceptable to you and the others i would really appreciate it in the release!

Thx, bye Peter