Reason/avoidance/future of necessary JVM args

[SebastianDietrich]

To run eclipsestore I need to start the JVM with --add-exports java.base/jdk.internal.misc=ALL-UNNAMED
I suppose that is necessary for the eclipse-serializer to serialize/deserialize objects of classes that are not serializable and not accessible by reflection. Correct?
Is there a way to avoid this?
Is it planned or even possible to change that, so that future versions of eclipse-store / serializer don't have to do that? If not that might be a show-stopper in future java versions and is currently a show-stopper for using eclipse-store in google app-engine standard environment.

[hg-ms]

Hi,
we need access to the internal vm methods defined in misc.Unsafe to implement (de-)serialization (e.g accessing nonpublic properties) and fast off-heap memory access. The java module system unfortunately denies access to those long existing methods by default now.
We are working on an alternative because future java version will remove those low-level methods, but this will still take some time.

[SebastianDietrich]

Thanks for the update!
In the meantime, I've scanned the code of the eclipse-serializer and found that exception only for java records. So I've refactored my records into classes (annotated with Lombok @value) and voila: no necessity to use that JVM parameter anymore.

If I am correct (that the parameter is only necessay when using records), then that should imho be documented somewhere.

And of course thumbs up for the future alternative!