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?
* Is the WicketStuff version even maintained anymore?
* 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?
* 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.
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
