Question: Why use of latest jakarta dependencies (icw use jaxb xsd processing and java 11)

[mvhaasteren]

Hi Greta,

We use the jvnet jaxb2 maven plugin (org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.15.1) to generate the SqlRules java objects from the customRules.xsd (the jvnet has an extension to initialise fields with the default values). So we removed the hardcoded SqlRules classes. Hence the addhocprovider uses unmarshalling with a jaxbcontext.
Problem with the maven-jaxb2-plugin plugin is that even the latest version is still using the javax.xml.bind classes, through transitive dependencies. There is a clash with the jakarta xml dependencies (versions 4.0.#) versus this plugin ... javax versus jakarta. If I choose versions 2.3.3 of both jakarta xml dependencies, then all is well. The result is that the old style javax classes are used.
Even the other jaxb plugin (jaxb2-maven-plugin) deals with the same issue, but also lacks the support of default values in the xsd.

Question 2: Is there a specific reason that the latest versions of the jakarta xml implementation dependencies are used?
Can we downgrade to 2.3.3?

Best regards,
Maarten.

[gretard]

Hi, there are no specific reasons for using those versions. However, I would like to keep the default values.

[mvhaasteren]

OK ... got it