Hi, Not sure why but many others say "Kyro" instead of "Kryo", just like you. Not a big deal :-)
WicketStuff project provides ISerializer impl based on Kryo - http://repo1.maven.org/maven2/org/wicketstuff/wicketstuff-serializer-kryo2/7.0.0-M3/ You can change the effective version of Kryo by adding a dependency for it in your application pom.xml. Kryo supports custom serializers per class. If there is no explicit serializer for some class then it uses a generic one. The generic one uses https://github.com/EsotericSoftware/reflectasm to do its magic. On Mon, Sep 22, 2014 at 6:28 PM, Garret Wilson <[email protected]> wrote: > I found the KyroSerializer project <https://github.com/ > EsotericSoftware/kryo>, but I suppose that there needs to be certain > adapter implementations (e.g. ISerializer), which maybe comes from > WicketStuff? But the WicketStuff page on Kyro <https://github.com/ > wicketstuff/core/wiki/Kryo-Serializer> seems out of date (mentioning > Wicket 1.5!), and it also mentions that it is only "based on Kyro and > kyro-serializers". > > * Do I have to bring in a WicketStuff dependency just to get Kyro, or > can I just bring in the Kyro dependency from Maven directly? > add dependency to org.wicketstuff.wicketstuff-serializer-kryo2:7.0.0-M3 and to com.esotericsoftware.kryo:kryo:LATEST_VERSION > * Is the WicketStuff version even maintained anymore? > There are no reported bugs against it. I guess it works fine for the developer who contributed it. > * Will the WicketStuff dependency force me to use an old, stale > version of Kyro, or does it allow me to pull in the latest build > from the KyroSerializer project? > See above. > * Does KyroSerializer allow deserialization of a class without a > default constructor (similar to XStream)? I'm already running into > the dreaded "no valid constructor" deserialization issue with > default Java serialization. > Yes. It supports several different instantiation strategies. Check Kryo's docu for more details. > > > Thanks for any clarification, > > Garret > > > > On 9/7/2014 7:13 AM, Andrea Del Bene wrote: > >> You can start from here: http://wicket.apache.org/ >> guide/guide/versioningCaching.html , paragraph "Pluggable >> serialization". This should save you some time :) >> >>> >>> On 9/6/2014 4:25 PM, Martin Grigorov wrote: >>> >>>> Use another ISerializer! >>>> >>> >>> Ah, so I can plug different serializers into Wicket? Nice. I'll go do >>> some research... another day, unfortunately, as I'm working at breakneck >>> speed toward a deadline. For the moment I'll throw in a custom >>> read/writeObject(). (Ugh, custom Java serialization is so old and unwieldy. >>> There go my final fields...) But I'll keep that in mind to look >>> into---thanks for the tip! >>> >>> For example KryoSerializer from WicketStuff. >>>> Side effect: it will be faster >>>> >>> >>> >>> Can't argue with faster, I guess. :) >>> >>> Cheers, >>> >>> Garret >>> >> >> >
