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

Support additional Serialization mechanisms #134

Closed
radcortez opened this issue Aug 14, 2020 · 0 comments · Fixed by #137
Closed

Support additional Serialization mechanisms #134

radcortez opened this issue Aug 14, 2020 · 0 comments · Fixed by #137

Comments

@radcortez
Copy link
Contributor

For SVM native image, Java Serialization is not supported yet.

We can workaround this, by use SVM Substitute with a supported Serialization mechanism (Jsonb for instance).

Unfortunately, this still raises an issue of different behaviours between the JVM and SVM executions, plus if using a persistent repository the data serialization is incompatible.

Ideally, we could support different Serialization mechanisms in JBeret and pick which one to use with a configuration. You won't be able to change Serialization after the first execution with a persistent store, but at least it would allow you to keep consistency between the JVM and SVM.

radcortez added a commit to radcortez/jsr352 that referenced this issue Nov 10, 2020
radcortez added a commit to radcortez/jsr352 that referenced this issue Mar 18, 2021
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

Successfully merging a pull request may close this issue.

1 participant