Rebase on current Kryo trunk #1
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…. 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.
…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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.