-
Notifications
You must be signed in to change notification settings - Fork 115
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
systemId resolution regression introduced in 2.3.4+ #1732
Comments
lukasj
added a commit
to lukasj/jaxb-ri
that referenced
this issue
Oct 9, 2023
Signed-off-by: Lukas Jungmann <[email protected]>
lukasj
added a commit
that referenced
this issue
Oct 12, 2023
Signed-off-by: Lukas Jungmann <[email protected]>
lukasj
added a commit
to lukasj/jaxb-ri
that referenced
this issue
Oct 13, 2023
Signed-off-by: Lukas Jungmann <[email protected]> (cherry picked from commit 20c8ed3)
lukasj
added a commit
that referenced
this issue
Oct 13, 2023
Signed-off-by: Lukas Jungmann <[email protected]> (cherry picked from commit 20c8ed3)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While modernizing the jaxb-tools (formerly the Highsource jaxb2-basics, maven-jaxb2-plugin, etc), we came across a use case that results in the need for us to work around systemId detection and handling.
We are looking for a better long-term solution for being able to wire into the xjc lifecycle, or send a config option to change the new default behavior.
@laurentschoelens has coded up a work-around and a demo project highlighting the issue.
This is the identified change in jaxb-ri:
b3a2c63
jaxb-tools PR with work-around: highsource/jaxb-tools#329
JAXB Tools project: https://github.com/highsource/jaxb-tools
The text was updated successfully, but these errors were encountered: