Comments (7)
From [email protected] on April 05, 2010 14:15:39
The value of a final field can be inlined in method bodies. Changing the value of a
final field is possible through reflection, but should never be done because the
changes may not be seen by all code accessing the field.
Status: WontFix
from kryo.
From martin.grotzke on April 05, 2010 14:19:54
Ok, that's true. But in my case the final field is only set when an object is deserialized in another jvm, therefore there has not
been any code that has seen this value.
from kryo.
From martin.grotzke on April 05, 2010 14:21:33
In either case, it would be good to have the possibility to enforce this behavior. Do you see any problems with this?
from kryo.
From [email protected] on April 05, 2010 14:39:42
It appears JLS 17.5.3 details when it is OK to modify final fields and the associated
problems:
http://java.sun.com/docs/books/jls/third_edition/html/memory.html#17.5.3
Based on this, I now think Kryo should serialize final fields. I don't think a
setting is necessary.
Status: Accepted
from kryo.
From martin.grotzke on April 05, 2010 14:49:23
Great!
Though, I just noticed that inner classes are not deserialized correctly with this setting. E.g. for a class
public static class Container {
private final Body _body;
public Container() {
_body = new Body();
}
class Body {
}
}
the enclosing Container instance is not set on the Body instance after deserialization.
The test and serialization/deserialization looks like this:
public void testInnerClass() throws Exception {
final Container container = new Container();
final Container deserialized = deserialize( serialize( container ), Container.class );
assertDeepEquals( deserialized, container );
}
protected byte[] serialize( final Object o ) {
return new ObjectBuffer(_kryo).writeObject( o );
}
protected <T> T deserialize( final byte[] in, final Class<T> clazz ) {
return new ObjectBuffer( _kryo ).readObject( in, clazz );
}
from kryo.
From [email protected] on April 06, 2010 01:12:00
Final field support is checked in, r96.
Being unable to instantiate a non-static member class is separate from final field
support. To do this, Kryo would need to pass the reference to the enclosing instance
to Constructor#newInstance(). There is currently no mechanism to obtain the enclosing
instance, and it doesn't appear easy to add.
Status: Fixed
from kryo.
From [email protected] on April 06, 2010 19:47:17
Issue 6 has been merged into this issue.
from kryo.
Related Issues (20)
- General approach to Java collections? -> UnmodifiableCollections do not seem to be de/serializable using Kryo HOT 1
- Redisson 3.24.3 java.lang.NoClassDefFoundError: com/esotericsoftware/kryo/serializers/DefaultSerializers$UUIDSerializer HOT 2
- Spring microservice encounters infinite loop when calling readLongs method resulting in denied access. HOT 3
- Could not serialize Lambda. If anyone knows this, then please response. HOT 6
- Compatibility issue between 5.5.0 and 5.6.0 HOT 2
- failed to lazily initialize a collection, no session or session was closed while trying to deserialize SPRING_SECURITY_CONTEXT HOT 3
- Add GregorianCalendar default serializer HOT 1
- Maven artifact not found HOT 4
- Encountered ArrayIndexOutOfBoundsException when running in Apache Spark 3.3.1 HOT 3
- Allow Kryo instances to be compared using .equals() & .hashcode() HOT 3
- deserialize failure in JDK 21 HOT 5
- When an anonymous inner class is used to initialize a collection, the elements are doubled. HOT 1
- Kryo5 deserialization lost Locale script field HOT 1
- The Input class changes its buffer when deserialize a string HOT 3
- About how to build serializer by custom self-reference class HOT 4
- Cannot run benchmarks HOT 4
- Urgent: Data Corruption Issue Identified During DTO Deserialization (Instance Variable Renamed/Type Changed) HOT 10
- schema validation failed while deserialize data serialized by Encoder.Bean Serializer using Kryo. HOT 2
- Comparison with ObjectInputStream and ObjectOutputStream HOT 2
- How to configure CompatibleFieldSerializer in Kryo3 ? HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from kryo.