…. It is called sun.misc.Unsafe and not java.misc.Unsafe ;-)

…work in the same way as AsmCacheField and UnsafeCacheField. All of them optimize for speed and ignore any custom registered serializers for primitive types for now.

…set of fields by means of rebuildCachedFields, remove all fields that were removed before.

…aultInstantiatorStrategy implements the usual Kryo behavior, where it tries to invoke a no-arg constructor when it needs to create a new instance.

But when org.objenesis.strategy.StdInstantiatorStrategy is used, then new instances are created without invoking a no-arg constructor, even if such a constructor is available. This improves Kryo's performance on fast-serialization tests (see issue #138)

- DateSerializer now properly handles Date subclasses.
- Added a new default serialzer por java.util.Locale.

Update to DateSerializer and new LocaleSerializer

…them package private

This shall support (de)serialization of cglib proxies.
A cglib proxy is typically serialized with a class name like e.g.
  FOO_org.example.MyClass$$EnhancerByCGLIB$$580cffdd
which, during deserialization, is the input to DefaultClassResolver.readName.

Because readName invokes Class.forName such proxies could not be
deserialized (Class.forName obviously would fail), this change shall
make it possible to resolve a valid type for such class names (a valid
type is a type for that a Registration exists).

For a real use case see CGLibProxySerializer (and Test) in kryo-serializers.

…Factory

…umber of classes.

Kryo can't be used since it thinks the object has already been serialized, Kryo would write a reference ID instead of the object.