Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Java 17 causes "InaccessibleObjectException" for ArraysAsListSerializer #208

Open
tinder-johnbuhanan opened this issue Apr 28, 2023 · 5 comments

Comments

@tinder-johnbuhanan
Copy link

tinder-johnbuhanan commented Apr 28, 2023

Due to PaperDB's use of kryo-serializers, "ArraysAsListSerializer" is not compatible with Java 17.
magro/kryo-serializers#131

Is there anyway we can make "ArraysAsListSerializer" compatible with Java 17?

@tinder-johnbuhanan
Copy link
Author

Seems to me that this part could be solved by this StackOverflow post.
image

https://stackoverflow.com/a/75473860

@tinder-johnbuhanan
Copy link
Author

They say that Kryo5 should work:
magro/kryo-serializers#131 (comment)

Any plans for PaperDB to update to Kryo5?

@pilgr
Copy link
Owner

pilgr commented May 1, 2023

Any plans for PaperDB to update to Kryo5?

I don't have such plans at the moment. I believe you can add your custom serializer as a workaround.

@ruimendesM
Copy link

I don't have such plans at the moment. I believe you can add your custom serializer as a workaround.

Was looking into this topic, as I am currently facing the same problem and adding a custom serializer it is not enough I believe.
The error occurs on the creation of the Kryo Instance here, which calls the constructor of the ArraysAsListSerializer containing the "problematic code".

So even if I add a custom serializer, the code will still fail at the same line.

@aeaa1998
Copy link

Due to PaperDB's use of kryo-serializers, "ArraysAsListSerializer" is not compatible with Java 17. magro/kryo-serializers#131

Is there anyway we can make "ArraysAsListSerializer" compatible with Java 17?

Hello! Did you found a solution for this? I have the same issue but it can only be reproduced when running unit tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants