-
Notifications
You must be signed in to change notification settings - Fork 76
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
Usage of JBoss Marshalling incompatible with native compilation with GraalVM #127
Comments
Options:
|
Hey @stuartwdouglas what would be your suggestion for this please? I suppose we would need to get rid of JBoss Marshalling if we indeed wanted to integrate JBeret into Quarkus? |
What exactly is this used for? The correct solution will likely depend on the use case. |
@stuartwdouglas see https://github.com/jberet/jsr352/blob/master/jberet-core/src/main/java/org/jberet/util/BatchUtil.java#L124 |
Here is a proposal to remove JBoss Marshalling: This is using MapStruct to generate the clone / copy code for the Job model. |
MapStruct, if used, will be a new dependency for both JBeret and WildFly. Is it already used in any other of our projects? If so how is the experience? |
@gunnarmorling is one of the creators of the project, so he can probably give additional feedback :) I don't think it is a major problem, since MapStruct is set as |
related to #133 |
BatchUtil
class currently uses aorg.jboss.marshalling.cloner.ObjectCloner
. Native compilation yields this (the actual log is much longer and less readable, showing just the most important piece here)We might need to get rid of JBoss Marshalling, or hack around it somehow, but I'm not yet sure if it's possible.
The text was updated successfully, but these errors were encountered: