entityMap|blocks|key|foq8p|text|JAXB+API被认为是Java+EE+API，因此在Java+SE+9中不再包含在默认类路径中。在Java+11中，它们已从JDK中完全删除。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|fed09|Java9引入了模块的概念，默认情况下，|b3e9m|聚合模块在类路径(或者更确切地说，模块路径)上可用。顾名思义，|deakr|aggregate模块可以做到这一点|d7s7i|注释|b6mio|包括传统上与Java+6/7/8捆绑在一起的Java+EE+API。|8bk3t|幸运的是，JDK+6/7/8中提供的这些Java+EE+API仍然在JDK中，但缺省情况下它们不在类路径中。以下模块提供了额外的Java+EE+API：|ea2ii|java.activation
java.corba
java.transaction
java.xml.bind++<<+This+one+contains+the+JAXB+APIs
java.xml.ws
java.xml.ws.annotation|code-block|syntax|javascript|ff852|快速而粗糙的解决方案：(仅限JDK+9/10+)|79q2m|要使JAXB+API在运行时可用，请指定以下命令行选项：|6s4lf|但我仍然需要它才能与Java+8一起工作！|a9ha7|如果您尝试指定|fmche|对于较旧的JDK，它会爆炸，因为它是一个无法识别的选项。我建议使用以下两个选项之一：|3di82|您可以使用以下命令设置任何仅限9%2B的Java选项|7pv5c|环境变量。此环境变量为|d7ece|自动读取|8ijvl|由|6llgp|用于Java+9%2B的启动器。|aldj2|您可以添加|9gr0n|让JVM静默地忽略无法识别的选项，而不是崩溃。但要当心！JVM将不再验证您使用的任何其他命令行参数。此选项适用于Oracle/OpenJDK以及IBM+JDK+(从JDK+8sr4开始)。|6gp0|备用快速解决方案：(仅限JDK+9/10+)|f099e|注意，您可以在运行时使用上面的所有Java模块，方法是指定|30kl6|选项。The+The+The|9e4l1|模块是一个聚合模块，它包括|4nd5a|以及上面的Java+EE+API模块。请注意，这|8s7h9|在Java+11上不起作用|9vccv|因为|6n3p1|在Java+11中被删除。|7l167|正确的长期解决方案：(JDK+9及更高版本)|fc48q|上面列出的Java+EE+API模块都已标记|euqbs|因为他们是|7uk2s|计划删除|9h7jb|在|36q3f|Java+11|anvqq|..。所以|9gt32|这种方法将不再适用于开箱即用的Java11。|cogrj|在Java+11及更高版本中，您需要做的是在类路径或模块路径中包含您自己的Java副本。例如，您可以将JAX-+APIs作为Maven依赖项添加，如下所示：|1p279|jakarta.xml.bind
++++jakarta.xml.bind-api
++++2.3.2




++++org.glassfish.jaxb
++++jaxb-runtime
++++2.3.2|9crf0|请参阅|9h306|JAXB参考实现页面|11v6p|有关JAXB的更多详细信息。|crsif|有关Java模块性的完整详细信息，请参见|9jq2s|JEP+261:模块系统|6cmkl|对于Gradle或Android+Studio开发人员：(JDK+9及更高版本)|4cmhu|将以下依赖项添加到您的|6bece|文件：|76s4s|dependencies+{
++++//+JAX-B+dependencies+for+JDK+9%2B
++++implementation+"jakarta.xml.bind:jakarta.xml.bind-api:2.3.2"
++++implementation+"org.glassfish.jaxb:jaxb-runtime:2.3.2"
}^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|2Z|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|30|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|31|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|32|9|@]|A|@]|B|$]]|$2|I|4|J|6|7|8|33|9|@]|A|@]|B|$]]|$2|K|4|L|6|7|8|34|9|@]|A|@]|B|$]]|$2|M|4|N|6|7|8|35|9|@]|A|@]|B|$]]|$2|O|4|P|6|Q|8|36|9|@]|A|@]|B|$R|S]]|$2|T|4|U|6|7|8|37|9|@]|A|@]|B|$]]|$2|V|4|W|6|7|8|38|9|@]|A|@]|B|$]]|$2|X|4|Y|6|7|8|39|9|@]|A|@]|B|$]]|$2|Z|4|10|6|7|8|3A|9|@]|A|@]|B|$]]|$2|11|4|12|6|7|8|3B|9|@]|A|@]|B|$]]|$2|13|4|14|6|7|8|3C|9|@]|A|@]|B|$]]|$2|15|4|16|6|7|8|3D|9|@]|A|@]|B|$]]|$2|17|4|18|6|7|8|3E|9|@]|A|@]|B|$]]|$2|19|4|1A|6|7|8|3F|9|@]|A|@]|B|$]]|$2|1B|4|1C|6|7|8|3G|9|@]|A|@]|B|$]]|$2|1D|4|1E|6|7|8|3H|9|@]|A|@]|B|$]]|$2|1F|4|1G|6|7|8|3I|9|@]|A|@]|B|$]]|$2|1H|4|1I|6|7|8|3J|9|@]|A|@]|B|$]]|$2|1J|4|1K|6|7|8|3K|9|@]|A|@]|B|$]]|$2|1L|4|1M|6|7|8|3L|9|@]|A|@]|B|$]]|$2|1N|4|1O|6|7|8|3M|9|@]|A|@]|B|$]]|$2|1P|4|1Q|6|7|8|3N|9|@]|A|@]|B|$]]|$2|1R|4|1S|6|7|8|3O|9|@]|A|@]|B|$]]|$2|1T|4|1U|6|7|8|3P|9|@]|A|@]|B|$]]|$2|1V|4|1W|6|7|8|3Q|9|@]|A|@]|B|$]]|$2|1X|4|1Y|6|7|8|3R|9|@]|A|@]|B|$]]|$2|1Z|4|20|6|7|8|3S|9|@]|A|@]|B|$]]|$2|21|4|22|6|7|8|3T|9|@]|A|@]|B|$]]|$2|23|4|24|6|7|8|3U|9|@]|A|@]|B|$]]|$2|25|4|26|6|7|8|3V|9|@]|A|@]|B|$]]|$2|27|4|28|6|7|8|3W|9|@]|A|@]|B|$]]|$2|29|4|2A|6|7|8|3X|9|@]|A|@]|B|$]]|$2|2B|4|2C|6|7|8|3Y|9|@]|A|@]|B|$]]|$2|2D|4|2E|6|7|8|3Z|9|@]|A|@]|B|$]]|$2|2F|4|2G|6|Q|8|40|9|@]|A|@]|B|$R|S]]|$2|2H|4|2I|6|7|8|41|9|@]|A|@]|B|$]]|$2|2J|4|2K|6|7|8|42|9|@]|A|@]|B|$]]|$2|2L|4|2M|6|7|8|43|9|@]|A|@]|B|$]]|$2|2N|4|2O|6|7|8|44|9|@]|A|@]|B|$]]|$2|2P|4|2Q|6|7|8|45|9|@]|A|@]|B|$]]|$2|2R|4|2S|6|7|8|46|9|@]|A|@]|B|$]]|$2|2T|4|2U|6|7|8|47|9|@]|A|@]|B|$]]|$2|2V|4|2W|6|7|8|48|9|@]|A|@]|B|$]]|$2|2X|4|2Y|6|Q|8|49|9|@]|A|@]|B|$R|S]]]]

The JAXB APIs are considered to be Java EE APIs and therefore are no longer contained on the default classpath in Java SE 9. In Java 11, they are completely removed from the JDK.
Java 9 introduces the concepts of modules, and by default, the <code>java.se</code> aggregate module is available on the classpath (or rather, module-path). As the name implies, the <code>java.se</code> aggregate module does not include the Java EE APIs that have been traditionally bundled with Java 6/7/8.
Fortunately, these Java EE APIs that were provided in JDK 6/7/8 are still in the JDK, but they just aren't on the classpath by default. The extra Java EE APIs are provided in the following modules:
<pre><code>java.activation
java.corba
java.transaction
java.xml.bind &lt;&lt; This one contains the JAXB APIs
java.xml.ws
java.xml.ws.annotation
</code></pre>
Quick and dirty solution: (JDK 9/10 only)
To make the JAXB APIs available at runtime, specify the following command-line option:
<code>--add-modules java.xml.bind</code>
But I still need this to work with Java 8!!!
If you try specifying <code>--add-modules</code> with an older JDK, it will blow up because it's an unrecognized option. I suggest one of two options:
<ol>
<li>You can set any Java 9+ only options using the <code>JDK_JAVA_OPTIONS</code> environment variable. This environment variable is <a href="https://www.oracle.com/technetwork/java/javase/9-new-features-3745613.html#JDK-8170832" rel="noreferrer">automatically read</a> by the <code>java</code> launcher for Java 9+.</li>
<li>You can add the <code>-XX:+IgnoreUnrecognizedVMOptions</code> to make the JVM silently ignore unrecognized options, instead of blowing up. But beware! Any other command-line arguments you use will no longer be validated for you by the JVM. This option works with Oracle/OpenJDK as well as IBM JDK (as of JDK 8sr4).</li>
</ol>
<hr />
Alternate quick solution: (JDK 9/10 only)
Note that you can make all of the above Java EE modules available at run time by specifying the <code>--add-modules java.se.ee</code> option. The <code>java.se.ee</code> module is an aggregate module that includes <code>java.se.ee</code> as well as the above Java EE API modules. Note, this doesn't work on Java 11 because <code>java.se.ee</code> was removed in Java 11.
<hr />
<h2>Proper long-term solution: (JDK 9 and beyond)</h2>
The Java EE API modules listed above are all marked <code>@Deprecated(forRemoval=true)</code> because they are <a href="http://openjdk.java.net/jeps/320" rel="noreferrer">scheduled for removal</a> in <a href="http://openjdk.java.net/projects/jdk/11/" rel="noreferrer">Java 11</a>. So the <code>--add-module</code> approach will no longer work in Java 11 out-of-the-box.
What you will need to do in Java 11 and forward is include your own copy of the Java EE APIs on the classpath or module path. For example, you can add the JAX-B APIs as a Maven dependency like this:
<pre><code>&lt;!-- API, java.xml.bind module --&gt;
&lt;dependency&gt;
 &lt;groupId&gt;jakarta.xml.bind&lt;/groupId&gt;
 &lt;artifactId&gt;jakarta.xml.bind-api&lt;/artifactId&gt;
 &lt;version&gt;2.3.2&lt;/version&gt;
&lt;/dependency&gt;

&lt;!-- Runtime, com.sun.xml.bind module --&gt;
&lt;dependency&gt;
 &lt;groupId&gt;org.glassfish.jaxb&lt;/groupId&gt;
 &lt;artifactId&gt;jaxb-runtime&lt;/artifactId&gt;
 &lt;version&gt;2.3.2&lt;/version&gt;
&lt;/dependency&gt;
</code></pre>
See the <a href="https://eclipse-ee4j.github.io/jaxb-ri/" rel="noreferrer">JAXB Reference Implementation page</a> for more details on JAXB.
For full details on Java modularity, see <a href="http://openjdk.java.net/jeps/261" rel="noreferrer">JEP 261: Module System</a>
For Gradle or Android Studio developer: (JDK 9 and beyond)
Add the following dependencies to your <code>build.gradle</code> file:
<pre><code>dependencies {
 // JAX-B dependencies for JDK 9+
 implementation &quot;jakarta.xml.bind:jakarta.xml.bind-api:2.3.2&quot;
 implementation &quot;org.glassfish.jaxb:jaxb-runtime:2.3.2&quot;
}
</code></pre>

entityMap|blocks|key|5tmti|text|在编译时和运行时，添加开关|type|unstyled|depth|inlineStyleRanges|entityRanges|data|8tqpl|javac+--add-modules+java.xml.bind+

java+--add-modules+java.xml.bind|code-block|syntax|javascript|a9dg6|很好地介绍了|fjm0v|还可以在以下位置找到模块：|9ku9f|https://www.youtube.com/watch?v=KZfbRuvv5qc^0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|N|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|O|9|@]|A|@]|B|$F|G]]|$2|H|4|I|6|7|8|P|9|@]|A|@]|B|$]]|$2|J|4|K|6|7|8|Q|9|@]|A|@]|B|$]]|$2|L|4|M|6|7|8|R|9|@]|A|@]|B|$]]]]

At the time of compilation as well as run time, add the switch <code>--add-modules java.xml.bind</code>

<pre><code>javac --add-modules java.xml.bind &lt;java file name&gt;

java --add-modules java.xml.bind &lt;class file&gt;
</code></pre>

A good introduction of the <code>JDK 9</code> modules can also be found at :
<a href="https://www.youtube.com/watch?v=KZfbRuvv5qc" rel="noreferrer">https://www.youtube.com/watch?v=KZfbRuvv5qc</a>

entityMap|blocks|key|4qp01|text|这对我很有效：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|bsqbs|javax.xml.bind
++++jaxb-api
++++2.3.0


++++org.eclipse.persistence
++++eclipselink
++++2.7.0|code-block|syntax|javascript|e2um2|更新|8h4eg|正如@Jasper建议的那样，为了避免依赖于整个EclipseLink库，您也可以只依赖EclipseLink+MOXy：|bfufv|Maven|3r801|org.eclipse.persistence
++++org.eclipse.persistence.moxy
++++2.7.3|58sl9|Gradle|390mf|compile+group:+'org.eclipse.persistence',+name:+'org.eclipse.persistence.moxy',+version:+'2.7.3'|7nlbi|作为我的Java+8应用程序的依赖项，它会生成一个|cjoj1|*|83jf0|.jar，它可以在JRE8或JRE9上运行，不需要额外的参数。|bcmtf|此外，在使用JAXB+API之前，需要在某个位置执行此操作：|1jpnd|System.setProperty("javax.xml.bind.JAXBContextFactory",+"org.eclipse.persistence.jaxb.JAXBContextFactory");|6aub6|到目前为止，作为一种解决办法，它工作得很好。虽然看起来不是一个完美的解决方案..。^0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|15|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|16|9|@]|A|@]|B|$F|G]]|$2|H|4|I|6|7|8|17|9|@]|A|@]|B|$]]|$2|J|4|K|6|7|8|18|9|@]|A|@]|B|$]]|$2|L|4|M|6|7|8|19|9|@]|A|@]|B|$]]|$2|N|4|O|6|E|8|1A|9|@]|A|@]|B|$F|G]]|$2|P|4|Q|6|7|8|1B|9|@]|A|@]|B|$]]|$2|R|4|S|6|E|8|1C|9|@]|A|@]|B|$F|G]]|$2|T|4|U|6|7|8|1D|9|@]|A|@]|B|$]]|$2|V|4|W|6|7|8|1E|9|@]|A|@]|B|$]]|$2|X|4|Y|6|7|8|1F|9|@]|A|@]|B|$]]|$2|Z|4|10|6|7|8|1G|9|@]|A|@]|B|$]]|$2|11|4|12|6|E|8|1H|9|@]|A|@]|B|$F|G]]|$2|13|4|14|6|7|8|1I|9|@]|A|@]|B|$]]]]

This worked for me:

<pre><code>&lt;dependency&gt;
 &lt;groupId&gt;javax.xml.bind&lt;/groupId&gt;
 &lt;artifactId&gt;jaxb-api&lt;/artifactId&gt;
 &lt;version&gt;2.3.0&lt;/version&gt;
&lt;/dependency&gt;
&lt;dependency&gt;
 &lt;groupId&gt;org.eclipse.persistence&lt;/groupId&gt;
 &lt;artifactId&gt;eclipselink&lt;/artifactId&gt;
 &lt;version&gt;2.7.0&lt;/version&gt;
&lt;/dependency&gt;
</code></pre>

<hr>

<h2>Update</h2>

As @Jasper suggested, in order to avoid depending on the entire EclipseLink library, you can also just depend on EclipseLink MOXy:

Maven

<pre><code>&lt;dependency&gt;
 &lt;groupId&gt;org.eclipse.persistence&lt;/groupId&gt;
 &lt;artifactId&gt;org.eclipse.persistence.moxy&lt;/artifactId&gt;
 &lt;version&gt;2.7.3&lt;/version&gt;
&lt;/dependency&gt;
</code></pre>

Gradle

<pre><code>compile group: 'org.eclipse.persistence', name: 'org.eclipse.persistence.moxy', version: '2.7.3'
</code></pre>

<hr>

As dependencies for my Java 8 app, which produces a *.jar which can be run by both JRE 8 or JRE 9 with no additional arguments.

In addition, this needs to be executed somewhere before JAXB API will be used:

<pre><code>System.setProperty("javax.xml.bind.JAXBContextFactory", "org.eclipse.persistence.jaxb.JAXBContextFactory");
</code></pre>

Works great so far, as a workaround. Doesn't look like a perfect solution though...

entityMap|blocks|key|4ab91|text|对于Java+Web+Start执行，我们可以使用Andy+Guibert的建议，如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4udbq|注意--add-modules中额外的"=“。请参见|7vdec|此OpenJDK票证|9a487|的“了解运行时访问警告”中的最后一条说明。|608a9|Java+Platform标准版Oracle+JDK+9迁移指南|66pit|..。^0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|M|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|N|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|O|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|P|9|@]|A|@]|B|$]]|$2|I|4|J|6|7|8|Q|9|@]|A|@]|B|$]]|$2|K|4|L|6|7|8|R|9|@]|A|@]|B|$]]]]

For Java Web Start Execution we can use Andy Guibert's suggestion like this:

<pre><code>&lt;j2se version="1.6+" 
 java-vm-args="-XX:+IgnoreUnrecognizedVMOptions --add-modules=java.se.ee"/&gt;
</code></pre>

Note the extra "=" in the --add-modules. See <a href="https://bugs.openjdk.java.net/browse/JDK-8166438?focusedCommentId=14006763&amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14006763" rel="noreferrer">this OpenJDK Ticket</a> or the last note in "Understanding Runtime Access Warnings" of the <a href="https://docs.oracle.com/javase/9/migrate/" rel="noreferrer">Java Platform, Standard Edition Oracle JDK 9 Migration Guide</a>.

entityMap|blocks|key|e07rv|text|您可以使用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|cgeuq|将xml绑定模块添加到JVM运行时环境的JVM选项。|8le29|例如：^0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|G|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|H|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|I|9|@]|A|@]|B|$]]]]

You can use <code>--add-modules=java.xml.bind</code> JVM option to add xml bind module to JVM run-time environment.

Eg: <code>java --add-modules=java.xml.bind XmlTestClass</code>

entityMap|blocks|key|fo9s9|text|在我的示例中(spring+boot+fat+jar)，我只需将以下代码添加到pom.xml中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|6r6t8|javax.xml.bind
++++jaxb-api
++++2.3.1|code-block|syntax|javascript^0|0^^$0|$]|1|@$2|3|4|5|6|7|8|H|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|I|9|@]|A|@]|B|$F|G]]]]

In my case (spring boot fat jar) I just add the following to pom.xml.

<pre><code>&lt;dependency&gt;
 &lt;groupId&gt;javax.xml.bind&lt;/groupId&gt;
 &lt;artifactId&gt;jaxb-api&lt;/artifactId&gt;
 &lt;version&gt;2.3.1&lt;/version&gt;
&lt;/dependency&gt;
</code></pre>

entityMap|blocks|key|4mce3|text|这对我很有效。仅仅添加jaxb-api是不够的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|fnd02|javax.xml.bind
++++++++++++jaxb-api
++++++++++++${jaxb-api.version}
++++++++
++++++++
++++++++++++com.sun.xml.bind
++++++++++++jaxb-impl
++++++++++++${jaxb-api.version}
++++++++
++++++++
++++++++++++com.sun.xml.bind
++++++++++++jaxb-core
++++++++++++${jaxb-api.version}|code-block|syntax|javascript^0|0^^$0|$]|1|@$2|3|4|5|6|7|8|H|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|I|9|@]|A|@]|B|$F|G]]]]

This worked for me. Adding only jaxb-api wasn't enough.

<pre><code> &lt;dependency&gt;
 &lt;groupId&gt;javax.xml.bind&lt;/groupId&gt;
 &lt;artifactId&gt;jaxb-api&lt;/artifactId&gt;
 &lt;version&gt;${jaxb-api.version}&lt;/version&gt;
 &lt;/dependency&gt;
 &lt;dependency&gt;
 &lt;groupId&gt;com.sun.xml.bind&lt;/groupId&gt;
 &lt;artifactId&gt;jaxb-impl&lt;/artifactId&gt;
 &lt;version&gt;${jaxb-api.version}&lt;/version&gt;
 &lt;/dependency&gt;
 &lt;dependency&gt;
 &lt;groupId&gt;com.sun.xml.bind&lt;/groupId&gt;
 &lt;artifactId&gt;jaxb-core&lt;/artifactId&gt;
 &lt;version&gt;${jaxb-api.version}&lt;/version&gt;
 &lt;/dependency&gt;
</code></pre>

entityMap|blocks|key|8nboi|text|不是一个答案，而是一个附录:我得到的是因为跑步|type|unstyled|depth|inlineStyleRanges|entityRanges|data|fd0u5|(Groovy+2.4.13)如果JAVA|5t6ib|_|ci0em|HOME指向Java+9安装(|7969q|准确地说)严重失败：|9p1cr|java.lang.reflect.InvocationTargetException
++++++++at+java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native+Method)
++++++++at+java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
++++++++at+java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
++++++++at+java.base/java.lang.reflect.Method.invoke(Method.java:564)
++++++++at+org.codehaus.groovy.tools.GroovyStarter.rootLoader(GroovyStarter.java:107)
++++++++at+org.codehaus.groovy.tools.GroovyStarter.main(GroovyStarter.java:129)
Caused+by:+java.lang.NoClassDefFoundError:+Unable+to+load+class+groovy.xml.jaxb.JaxbGroovyMethods+due+to+missing+dependency+javax/xml/bind/JAXBContext
++++++++at+org.codehaus.groovy.vmplugin.v5.Java5.configureClassNode(Java5.java:400)
++++++++at+org.codehaus.groovy.ast.ClassNode.lazyClassInit(ClassNode.java:277)
++++++++at+org.codehaus.groovy.ast.ClassNode.getMethods(ClassNode.java:397)
++++++++...
++++++++..
++++++++.
++++++++..
++++++++...
++++++++at+org.codehaus.groovy.tools.shell.Groovysh.(Groovysh.groovy:135)
++++++++at+org.codehaus.groovy.vmplugin.v7.IndyInterface.selectMethod(IndyInterface.java:232)
++++++++at+org.codehaus.groovy.tools.shell.Main.(Main.groovy:66)
++++++++at+org.codehaus.groovy.vmplugin.v7.IndyInterface.selectMethod(IndyInterface.java:232)
++++++++at+org.codehaus.groovy.tools.shell.Main.main(Main.groovy:163)
...+6+more|code-block|syntax|javascript|32ih5|解决方案是：|ckj4e|转到|76sf8|JAXB项目|ahpdu|在github.io+(|ahimo|"JAXB在双重许可下获得许可-+CDDL+1.1和GPL+2.0，但类路径例外“|d1rb5|)|8ua6r|下载|5n35|将java基础结构文件解压到任何位置(在我的例子中，|10tng|)。可能存在其他解决方案(可能通过SDKMAN，我不知道)|8vdiu|确保lib子目录中的jar位于|a9nlt|..。我是通过一个在bash启动时启动的脚本来实现的，该脚本名为|5gqnf|，我在其中添加了(在许多其他行中)以下循环：|bj1v9|打包成一个函数...|4bnbh|function+extend_qzminynshg+{
+++local+BASE="/usr/local/java"
+++for+LIB+in+jaxb-api.jar++jaxb-core.jar++jaxb-impl.jar++jaxb-jxc.jar++jaxb-xjc.jar;+do
++++++local+FQLIB="$BASE/jaxb-ri/lib/$LIB"
++++++if+[[+-f+$FQLIB+]];+then
+++++++++export+CLASSPATH=$FQLIB:$CLASSPATH
++++++fi
++++done
}

extend_qzminynshg;+unset+extend_qzminynshg|bj6kg|它起作用了！^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|1J|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|1K|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|1L|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|1M|9|@]|A|@]|B|$]]|$2|I|4|J|6|7|8|1N|9|@]|A|@]|B|$]]|$2|K|4|L|6|M|8|1O|9|@]|A|@]|B|$N|O]]|$2|P|4|Q|6|7|8|1P|9|@]|A|@]|B|$]]|$2|R|4|S|6|7|8|1Q|9|@]|A|@]|B|$]]|$2|T|4|U|6|7|8|1R|9|@]|A|@]|B|$]]|$2|V|4|W|6|7|8|1S|9|@]|A|@]|B|$]]|$2|X|4|Y|6|7|8|1T|9|@]|A|@]|B|$]]|$2|Z|4|10|6|7|8|1U|9|@]|A|@]|B|$]]|$2|11|4|12|6|7|8|1V|9|@]|A|@]|B|$]]|$2|13|4|14|6|7|8|1W|9|@]|A|@]|B|$]]|$2|15|4|16|6|7|8|1X|9|@]|A|@]|B|$]]|$2|17|4|18|6|7|8|1Y|9|@]|A|@]|B|$]]|$2|19|4|1A|6|7|8|1Z|9|@]|A|@]|B|$]]|$2|1B|4|1C|6|7|8|20|9|@]|A|@]|B|$]]|$2|1D|4|1E|6|7|8|21|9|@]|A|@]|B|$]]|$2|1F|4|1G|6|M|8|22|9|@]|A|@]|B|$N|O]]|$2|1H|4|1I|6|7|8|23|9|@]|A|@]|B|$]]]]

Not an answer, but an addendum: I got because running <code>groovysh</code> (Groovy 2.4.13) if JAVA_HOME points to a Java 9 installation (<code>java version "9.0.1"</code> to be precise) fails abysmally:

<pre><code>java.lang.reflect.InvocationTargetException
 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.base/java.lang.reflect.Method.invoke(Method.java:564)
 at org.codehaus.groovy.tools.GroovyStarter.rootLoader(GroovyStarter.java:107)
 at org.codehaus.groovy.tools.GroovyStarter.main(GroovyStarter.java:129)
Caused by: java.lang.NoClassDefFoundError: Unable to load class groovy.xml.jaxb.JaxbGroovyMethods due to missing dependency javax/xml/bind/JAXBContext
 at org.codehaus.groovy.vmplugin.v5.Java5.configureClassNode(Java5.java:400)
 at org.codehaus.groovy.ast.ClassNode.lazyClassInit(ClassNode.java:277)
 at org.codehaus.groovy.ast.ClassNode.getMethods(ClassNode.java:397)
 ...
 ..
 .
 ..
 ...
 at org.codehaus.groovy.tools.shell.Groovysh.&lt;init&gt;(Groovysh.groovy:135)
 at org.codehaus.groovy.vmplugin.v7.IndyInterface.selectMethod(IndyInterface.java:232)
 at org.codehaus.groovy.tools.shell.Main.&lt;init&gt;(Main.groovy:66)
 at org.codehaus.groovy.vmplugin.v7.IndyInterface.selectMethod(IndyInterface.java:232)
 at org.codehaus.groovy.tools.shell.Main.main(Main.groovy:163)
... 6 more
</code></pre>

The solution was to:

<ul>
<li>Go to the <a href="https://javaee.github.io/jaxb-v2/" rel="nofollow noreferrer">JAXB Project</a> at github.io ("JAXB is licensed under a dual license - CDDL 1.1 and GPL 2.0 with Class-path Exception")</li>
<li>Download <code>jaxb-ri-2.3.0.zip</code></li>
<li>Unzip wherever you put your java infrastructure files (in my case, <code>/usr/local/java/jaxb-ri/</code>). Other solution may exist (maybe via SDKMAN, I dunno)</li>
<li>Make sure the jars in the lib subdirectory are on the <code>CLASSPATH</code>. I do it via a script started on bash startup, called <code>/etc/profile.d/java.sh</code>, where I added (among many other lines) the following loop:</li>
</ul>

Packed into a function...

<pre><code>function extend_qzminynshg {
 local BASE="/usr/local/java"
 for LIB in jaxb-api.jar jaxb-core.jar jaxb-impl.jar jaxb-jxc.jar jaxb-xjc.jar; do
 local FQLIB="$BASE/jaxb-ri/lib/$LIB"
 if [[ -f $FQLIB ]]; then
 export CLASSPATH=$FQLIB:$CLASSPATH
 fi
 done
}

extend_qzminynshg; unset extend_qzminynshg
</code></pre>

And it works!

entityMap|blocks|key|8qqp2|text|在最近的JDK+9.0.1中，这些解决方案都不适合我。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5u3el|我发现这个依赖列表足以保证正常运行，所以您|6ghb4|不需要|abd8a|显式指定|4r924|(尽管它是在这些依赖项的pom中指定的)。您唯一需要做的就是指定以下依赖项列表：|8upbn|javax.xml.bind
++++++++jaxb-api
++++++++2.3.0
++++
++++
++++++++com.sun.xml.bind
++++++++jaxb-impl
++++++++2.3.0
++++
++++
++++++++org.glassfish.jaxb
++++++++jaxb-runtime
++++++++2.3.0
++++
++++
++++++++javax.activation
++++++++activation
++++++++1.1.1|code-block|syntax|javascript^0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|P|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|Q|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|R|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|S|9|@]|A|@]|B|$]]|$2|I|4|J|6|7|8|T|9|@]|A|@]|B|$]]|$2|K|4|L|6|M|8|U|9|@]|A|@]|B|$N|O]]]]

None of these solutions worked fine for me in the recent JDK 9.0.1.

I found that this list of dependencies is enough for a proper functioning, so you don't need to explicitly specify <code>--add-module</code> (though it is specified within these dependencies's pom's). The only you need is to specify this list of dependencies:

<pre><code>&lt;dependencies&gt;
 &lt;dependency&gt;
 &lt;groupId&gt;javax.xml.bind&lt;/groupId&gt;
 &lt;artifactId&gt;jaxb-api&lt;/artifactId&gt;
 &lt;version&gt;2.3.0&lt;/version&gt;
 &lt;/dependency&gt;
 &lt;dependency&gt;
 &lt;groupId&gt;com.sun.xml.bind&lt;/groupId&gt;
 &lt;artifactId&gt;jaxb-impl&lt;/artifactId&gt;
 &lt;version&gt;2.3.0&lt;/version&gt;
 &lt;/dependency&gt;
 &lt;dependency&gt;
 &lt;groupId&gt;org.glassfish.jaxb&lt;/groupId&gt;
 &lt;artifactId&gt;jaxb-runtime&lt;/artifactId&gt;
 &lt;version&gt;2.3.0&lt;/version&gt;
 &lt;/dependency&gt;
 &lt;dependency&gt;
 &lt;groupId&gt;javax.activation&lt;/groupId&gt;
 &lt;artifactId&gt;activation&lt;/artifactId&gt;
 &lt;version&gt;1.1.1&lt;/version&gt;
 &lt;/dependency&gt;
&lt;/dependencies&gt;
</code></pre>

entityMap|blocks|key|1s0bt|text|为了解决这个问题，我在项目中导入了一些JAR文件：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|bk4db|javax.activation-1.2.0.jar|a0pqv|http://search.maven.org/remotecontent?filepath=com/sun/activation/javax.activation/1.2.0/javax.activation-1.2.0.jar|43c9e|jaxb-api-2.3.0.jar|4lced|http://search.maven.org/remotecontent?filepath=javax/xml/bind/jaxb-api/2.3.0/jaxb-api-2.3.0.jar|fcsn2|jaxb-core-2.3.0.jar|fbjiv|http://search.maven.org/remotecontent?filepath=com/sun/xml/bind/jaxb-core/2.3.0/jaxb-core-2.3.0.jar|eh885|jaxb-impl-2.3.0.jar|a21ql|http://search.maven.org/remotecontent?filepath=com/sun/xml/bind/jaxb-impl/2.3.0/jaxb-impl-2.3.0.jar|2581r|下载上述文件并将其复制到项目的libs文件夹中|edto3|将导入的JAR文件添加到Java构建路径中^0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|W|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|X|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|Y|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|Z|9|@]|A|@]|B|$]]|$2|I|4|J|6|7|8|10|9|@]|A|@]|B|$]]|$2|K|4|L|6|7|8|11|9|@]|A|@]|B|$]]|$2|M|4|N|6|7|8|12|9|@]|A|@]|B|$]]|$2|O|4|P|6|7|8|13|9|@]|A|@]|B|$]]|$2|Q|4|R|6|7|8|14|9|@]|A|@]|B|$]]|$2|S|4|T|6|7|8|15|9|@]|A|@]|B|$]]|$2|U|4|V|6|7|8|16|9|@]|A|@]|B|$]]]]

To solve this, I have imported some JAR files in my project:

<ul>
<li>javax.activation-1.2.0.jar</li>
</ul>

<a href="http://search.maven.org/remotecontent?filepath=com/sun/activation/javax.activation/1.2.0/javax.activation-1.2.0.jar" rel="noreferrer">http://search.maven.org/remotecontent?filepath=com/sun/activation/javax.activation/1.2.0/javax.activation-1.2.0.jar</a>

<ul>
<li>jaxb-api-2.3.0.jar</li>
</ul>

<a href="http://search.maven.org/remotecontent?filepath=javax/xml/bind/jaxb-api/2.3.0/jaxb-api-2.3.0.jar" rel="noreferrer">http://search.maven.org/remotecontent?filepath=javax/xml/bind/jaxb-api/2.3.0/jaxb-api-2.3.0.jar</a>

<ul>
<li>jaxb-core-2.3.0.jar</li>
</ul>

<a href="http://search.maven.org/remotecontent?filepath=com/sun/xml/bind/jaxb-core/2.3.0/jaxb-core-2.3.0.jar" rel="noreferrer">http://search.maven.org/remotecontent?filepath=com/sun/xml/bind/jaxb-core/2.3.0/jaxb-core-2.3.0.jar</a>

<ul>
<li>jaxb-impl-2.3.0.jar</li>
</ul>

<a href="http://search.maven.org/remotecontent?filepath=com/sun/xml/bind/jaxb-impl/2.3.0/jaxb-impl-2.3.0.jar" rel="noreferrer">http://search.maven.org/remotecontent?filepath=com/sun/xml/bind/jaxb-impl/2.3.0/jaxb-impl-2.3.0.jar</a>

<ol>
<li>Download above files and copy them into libs folder in the project</li>
<li>Add the imported JAR files in Java Build Path</li>
</ol>

entityMap|blocks|key|7bg56|text|好吧，我一直有同样的问题，但我使用的是Java+8，并不断收到这个错误，我尝试了大多数解决方案。但事实证明，我的maven仍然指向java9-尽管我将全局java版本设置为8，只要我修复了所有问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|7em85|对于任何可能有这种问题的人，请查看|46gcd|如何修复Maven以使用默认Java^0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|G|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|H|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|I|9|@]|A|@]|B|$]]]]

OK, I have been having the same kind of issue, but I was using Java 8, and kept getting this error, I tried most of the solutions. but it turns out that my maven was still pointing to java 9 even-though I set the global Java version to 8, as soon as I fixed that it all worked. 

For anybody who might have this kind of problem, check out <a href="https://blog.tompawlak.org/maven-default-java-version-mac-osx" rel="nofollow noreferrer">How to fix Maven to use default Java</a>

entityMap|blocks|key|72vlh|text|更新2019年4月|type|unstyled|depth|inlineStyleRanges|entityRanges|data|d5dnh|JAXB版本的Changelong在|3m5lm|https://javaee.github.io/jaxb-v2/doc/user-guide/ch02.html|ca3bq|摘录：|1atcd|4.1.+Changes+between+2.3.0.1+and+2.4.0

+++++++++JAXB+RI+is+now+JPMS+modularized:

++++++++++++All+modules+have+native+module+descriptor.

++++++++++++Removed+jaxb-core+module,+which+caused+split+package+issue+on+JPMS.

++++++++++++RI+binary+bundle+now+has+single+jar+per+dependency+instead+of+shaded+fat+jars.

++++++++++++Removed+runtime+class+weaving+optimization.

++++4.2.+Changes+between+2.3.0+and+2.3.0.1

++++++++++Removed+legacy+technology+dependencies:

++++++++++++com.sun.xml.bind:jaxb1-impl

++++++++++++net.java.dev.msv:msv-core

++++++++++++net.java.dev.msv:xsdlib

++++++++++++com.sun.xml.bind.jaxb:isorelax

++++4.3.+Changes+between+2.2.11+and+2.3.0

++++++++++Adopt+Java+SE+9:

++++++++++++JAXB+api+can+now+be+loaded+as+a+module.

++++++++++++JAXB+RI+is+able+to+run+on+Java+SE+9+from+the+classpath.

++++++++++++Addes+support+for+java.util.ServiceLoader+mechanism.

++++++++++++Security+fixes|code-block|syntax|javascript|dvn0|权威链接位于|5e2ov|https://github.com/eclipse-ee4j/jaxb-ri#maven-artifacts|8qq3m|JAXB工件的Maven坐标|b9rin|JAXB+:jakarta.xml.bind-+API+:JAXB的API类。需要针对JAXB进行编译。|c8f1v|JAXB+:JAXB-+xml+:JAXB的实现，用于将java对象序列化和反序列化到xml或从xml反序列化的运行时。|7otsb|JAXB+fat-jar包：|ej1q3|JAXB+:JAXB-impl:JAXB运行时fat+jar。|9vrp7|与org.glassfish.jaxb工件不同的是，这些jars中包含了所有依赖类。这些工件不包含JPMS模块描述符。在Maven项目中，应该使用org.glassfish.jaxb工件。|dq4qm|f1bqs|jaxb:jaxb-jar:jar:2.3.2拉入：|6122b|[INFO]+%2B-+org.glassfish.jaxb:jaxb-runtime:jar:2.3.2:compile
[INFO]+%7C++%2B-+jakarta.xml.bind:jakarta.xml.bind-api:jar:2.3.2:compile
[INFO]+%7C++%2B-+org.glassfish.jaxb:txw2:jar:2.3.2:compile
[INFO]+%7C++%2B-+com.sun.istack:istack-commons-runtime:jar:3.0.8:compile
[INFO]+%7C++%2B-+org.jvnet.staxex:stax-ex:jar:1.8.1:compile
[INFO]+%7C++%2B-+com.sun.xml.fastinfoset:FastInfoset:jar:1.2.16:compile
[INFO]+%7C++\-+jakarta.activation:jakarta.activation-api:jar:1.2.1:compile|876nm|原始答案|bmpso|下面|ekbq6|我应该为我的Maven项目中的JAXB+RI使用哪些构件？|dak81|在Maven中，您可以使用如下配置文件：|8oed7|java-9
++++
++++++++9
++++
++++
++++++++
++++++++++++org.glassfish.jaxb
++++++++++++jaxb-runtime
++++++++++++2.3.0
++++++++
++++++++
++++++++++++javax.activation
++++++++++++activation
++++++++++++1.1.1|bv7mg|依赖关系树显示：|4psr6|[INFO]+%2B-+org.glassfish.jaxb:jaxb-runtime:jar:2.3.0:compile
[INFO]+%7C++%2B-+org.glassfish.jaxb:jaxb-core:jar:2.3.0:compile
[INFO]+%7C++%7C++%2B-+javax.xml.bind:jaxb-api:jar:2.3.0:compile
[INFO]+%7C++%7C++%2B-+org.glassfish.jaxb:txw2:jar:2.3.0:compile
[INFO]+%7C++%7C++\-+com.sun.istack:istack-commons-runtime:jar:3.0.5:compile
[INFO]+%7C++%2B-+org.jvnet.staxex:stax-ex:jar:1.7.8:compile
[INFO]+%7C++\-+com.sun.xml.fastinfoset:FastInfoset:jar:1.2.13:compile
[INFO]+\-+javax.activation:activation:jar:1.1.1:compile|8a23s|要在Eclipse中使用此功能，请使用Oxygen.3a+Release+(4.7.3a)或更高版本，按Ctrl-Alt-P组合键，或者右键单击项目Maven，然后选择概要文件。^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|1O|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|1P|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|1Q|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|1R|9|@]|A|@]|B|$]]|$2|I|4|J|6|K|8|1S|9|@]|A|@]|B|$L|M]]|$2|N|4|O|6|7|8|1T|9|@]|A|@]|B|$]]|$2|P|4|Q|6|7|8|1U|9|@]|A|@]|B|$]]|$2|R|4|S|6|7|8|1V|9|@]|A|@]|B|$]]|$2|T|4|U|6|7|8|1W|9|@]|A|@]|B|$]]|$2|V|4|W|6|7|8|1X|9|@]|A|@]|B|$]]|$2|X|4|Y|6|7|8|1Y|9|@]|A|@]|B|$]]|$2|Z|4|10|6|7|8|1Z|9|@]|A|@]|B|$]]|$2|11|4|12|6|7|8|20|9|@]|A|@]|B|$]]|$2|13|4|-4|6|7|8|21|9|@]|A|@]|B|$]]|$2|14|4|15|6|7|8|22|9|@]|A|@]|B|$]]|$2|16|4|17|6|K|8|23|9|@]|A|@]|B|$L|M]]|$2|18|4|19|6|7|8|24|9|@]|A|@]|B|$]]|$2|1A|4|1B|6|7|8|25|9|@]|A|@]|B|$]]|$2|1C|4|1D|6|7|8|26|9|@]|A|@]|B|$]]|$2|1E|4|1F|6|7|8|27|9|@]|A|@]|B|$]]|$2|1G|4|1H|6|K|8|28|9|@]|A|@]|B|$L|M]]|$2|1I|4|1J|6|7|8|29|9|@]|A|@]|B|$]]|$2|1K|4|1L|6|K|8|2A|9|@]|A|@]|B|$L|M]]|$2|1M|4|1N|6|7|8|2B|9|@]|A|@]|B|$]]]]

Update April 2019

Changelong for JAXB releases is at <a href="https://javaee.github.io/jaxb-v2/doc/user-guide/ch02.html" rel="noreferrer">https://javaee.github.io/jaxb-v2/doc/user-guide/ch02.html</a>

excerpts:

<pre><code> 4.1. Changes between 2.3.0.1 and 2.4.0

 JAXB RI is now JPMS modularized:

 All modules have native module descriptor.

 Removed jaxb-core module, which caused split package issue on JPMS.

 RI binary bundle now has single jar per dependency instead of shaded fat jars.

 Removed runtime class weaving optimization.

 4.2. Changes between 2.3.0 and 2.3.0.1

 Removed legacy technology dependencies:

 com.sun.xml.bind:jaxb1-impl

 net.java.dev.msv:msv-core

 net.java.dev.msv:xsdlib

 com.sun.xml.bind.jaxb:isorelax

 4.3. Changes between 2.2.11 and 2.3.0

 Adopt Java SE 9:

 JAXB api can now be loaded as a module.

 JAXB RI is able to run on Java SE 9 from the classpath.

 Addes support for java.util.ServiceLoader mechanism.

 Security fixes
</code></pre>

Authoritative link is at <a href="https://github.com/eclipse-ee4j/jaxb-ri#maven-artifacts" rel="noreferrer">https://github.com/eclipse-ee4j/jaxb-ri#maven-artifacts</a>

<blockquote>
 Maven coordinates for JAXB artifacts
 
 jakarta.xml.bind:jakarta.xml.bind-api: API classes for JAXB. Required
 to compile against JAXB.
 
 org.glassfish.jaxb:jaxb-runtime: Implementation of JAXB, runtime used
 for serialization and deserialization java objects to/from xml.
 
 JAXB fat-jar bundles: 
 
 com.sun.xml.bind:jaxb-impl: JAXB runtime fat
 jar.
 
 In contrast
 to org.glassfish.jaxb artifacts, these jars have all dependency
 classes included inside. These artifacts does not contain JPMS module
 descriptors. 
 In Maven projects org.glassfish.jaxb artifacts are
 supposed to be used instead.
</blockquote>

org.glassfish.jaxb:jaxb-runtime:jar:2.3.2 pulls in:

<pre><code>[INFO] +- org.glassfish.jaxb:jaxb-runtime:jar:2.3.2:compile
[INFO] | +- jakarta.xml.bind:jakarta.xml.bind-api:jar:2.3.2:compile
[INFO] | +- org.glassfish.jaxb:txw2:jar:2.3.2:compile
[INFO] | +- com.sun.istack:istack-commons-runtime:jar:3.0.8:compile
[INFO] | +- org.jvnet.staxex:stax-ex:jar:1.8.1:compile
[INFO] | +- com.sun.xml.fastinfoset:FastInfoset:jar:1.2.16:compile
[INFO] | \- jakarta.activation:jakarta.activation-api:jar:1.2.1:compile
</code></pre>

Original Answer

Following <a href="https://stackoverflow.com/questions/26413431/which-artifacts-should-i-use-for-jaxb-ri-in-my-maven-project">Which artifacts should I use for JAXB RI in my Maven project?</a> in Maven, you can use a profile like:

<pre><code>&lt;profile&gt;
 &lt;id&gt;java-9&lt;/id&gt;
 &lt;activation&gt;
 &lt;jdk&gt;9&lt;/jdk&gt;
 &lt;/activation&gt;
 &lt;dependencies&gt;
 &lt;dependency&gt;
 &lt;groupId&gt;org.glassfish.jaxb&lt;/groupId&gt;
 &lt;artifactId&gt;jaxb-runtime&lt;/artifactId&gt;
 &lt;version&gt;2.3.0&lt;/version&gt;
 &lt;/dependency&gt;
 &lt;dependency&gt;
 &lt;groupId&gt;javax.activation&lt;/groupId&gt;
 &lt;artifactId&gt;activation&lt;/artifactId&gt;
 &lt;version&gt;1.1.1&lt;/version&gt;
 &lt;/dependency&gt;
 &lt;/dependencies&gt;
&lt;/profile&gt; 
</code></pre>

Dependency tree shows:

<pre><code>[INFO] +- org.glassfish.jaxb:jaxb-runtime:jar:2.3.0:compile
[INFO] | +- org.glassfish.jaxb:jaxb-core:jar:2.3.0:compile
[INFO] | | +- javax.xml.bind:jaxb-api:jar:2.3.0:compile
[INFO] | | +- org.glassfish.jaxb:txw2:jar:2.3.0:compile
[INFO] | | \- com.sun.istack:istack-commons-runtime:jar:3.0.5:compile
[INFO] | +- org.jvnet.staxex:stax-ex:jar:1.7.8:compile
[INFO] | \- com.sun.xml.fastinfoset:FastInfoset:jar:1.2.13:compile
[INFO] \- javax.activation:activation:jar:1.1.1:compile
</code></pre>

To use this in Eclipse, say Oxygen.3a Release (4.7.3a) or later, Ctrl-Alt-P, or right-click on the project, Maven, then select the profile.

entityMap|blocks|key|aid9c|text|转到您的Build.gradle并为Java9或Java10添加以下依赖项。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|c9sda|sourceCompatibility+=+10+//+You+can+also+decrease+your+souce+compatibility+to+1.8+

//java+9%2B+does+not+have+Jax+B+Dependents

++++compile+group:+'javax.xml.bind',+name:+'jaxb-api',+version:+'2.3.0'
++++compile+group:+'com.sun.xml.bind',+name:+'jaxb-core',+version:+'2.3.0'
++++compile+group:+'com.sun.xml.bind',+name:+'jaxb-impl',+version:+'2.3.0'
++++compile+group:+'javax.activation',+name:+'activation',+version:+'1.1.1'|code-block|syntax|javascript^0|0^^$0|$]|1|@$2|3|4|5|6|7|8|H|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|I|9|@]|A|@]|B|$F|G]]]]

Go to Your Build.gradle and add below dependencies for both Java 9 or Java 10.

<pre><code>sourceCompatibility = 10 // You can also decrease your souce compatibility to 1.8 

//java 9+ does not have Jax B Dependents

 compile group: 'javax.xml.bind', name: 'jaxb-api', version: '2.3.0'
 compile group: 'com.sun.xml.bind', name: 'jaxb-core', version: '2.3.0'
 compile group: 'com.sun.xml.bind', name: 'jaxb-impl', version: '2.3.0'
 compile group: 'javax.activation', name: 'activation', version: '1.1.1'
</code></pre>

entityMap|blocks|key|250o1|text|我遵循了这个URL，下面的设置对我真的很有帮助。我在Macbook+Pro中使用带有STS+IDE的Java+10。它就像一个护身符。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|ff4aq|javax.xml.bind
++++jaxb-api
++++2.3.0


++++org.glassfish.jaxb
++++jaxb-runtime
++++2.3.0
++++runtime


++++javax.activation
++++javax.activation-api
++++1.2.0|code-block|syntax|javascript^0|0^^$0|$]|1|@$2|3|4|5|6|7|8|H|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|I|9|@]|A|@]|B|$F|G]]]]

I followed this URL and the below settings had really helped me. I use Java 10 with STS IDE in Macbook Pro. It works like a charm.

<pre><code> &lt;dependency&gt;
 &lt;groupId&gt;javax.xml.bind&lt;/groupId&gt;
 &lt;artifactId&gt;jaxb-api&lt;/artifactId&gt;
 &lt;version&gt;2.3.0&lt;/version&gt;
&lt;/dependency&gt;
&lt;dependency&gt;
 &lt;groupId&gt;org.glassfish.jaxb&lt;/groupId&gt;
 &lt;artifactId&gt;jaxb-runtime&lt;/artifactId&gt;
 &lt;version&gt;2.3.0&lt;/version&gt;
 &lt;scope&gt;runtime&lt;/scope&gt;
&lt;/dependency&gt;
&lt;dependency&gt;
 &lt;groupId&gt;javax.activation&lt;/groupId&gt;
 &lt;artifactId&gt;javax.activation-api&lt;/artifactId&gt;
 &lt;version&gt;1.2.0&lt;/version&gt;
&lt;/dependency&gt;
</code></pre>

entityMap|blocks|key|8j57h|text|我在使用Spring+Boot时遇到了同样的问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|8otvq|在Java+11上。|4bflc|添加|p5bs|单独解决不了这个问题。我还必须将Spring+Boot更新到最新的里程碑|6dj9k|，所以我假设这个问题会在下一个正式版本中得到解决。^0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|K|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|L|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|M|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|N|9|@]|A|@]|B|$]]|$2|I|4|J|6|7|8|O|9|@]|A|@]|B|$]]]]

I encountered the same issue using Spring Boot <code>2.0.5.RELEASE</code> on Java 11.

Adding <code>javax.xml.bind:jaxb-api:2.3.0</code> alone did not fix the problem. I also had to update Spring Boot to the latest Milestone <code>2.1.0.M2</code>, so I assume this will be fixed in the next official release.

entityMap|blocks|key|d0mdj|text|在pom.xml中添加javax.xml.bind依赖|type|unstyled|depth|inlineStyleRanges|entityRanges|data|cmq0f|javax.xml.bind
++++++++jaxb-api
++++++++2.3.0|code-block|syntax|javascript^0|0^^$0|$]|1|@$2|3|4|5|6|7|8|H|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|I|9|@]|A|@]|B|$F|G]]]]

add javax.xml.bind dependency in pom.xml

<pre><code> &lt;dependency&gt;
 &lt;groupId&gt;javax.xml.bind&lt;/groupId&gt;
 &lt;artifactId&gt;jaxb-api&lt;/artifactId&gt;
 &lt;version&gt;2.3.0&lt;/version&gt;
 &lt;/dependency&gt;
</code></pre>

entityMap|blocks|key|5tmqf|text|适用于所有JDK+>=+9的干净解决方案|type|unstyled|depth|inlineStyleRanges|entityRanges|data|677ng|您需要向构建中添加两个依赖项|3lpp8|jaxb-api|blqt5|一个jaxb实现|ck2h4|作为一个实现，我选择使用glassfish的参考实现来摆脱旧的com.sun类/库。因此，我在maven构建中添加了|ba6sl|javax.xml.bind
++jaxb-api
++2.3.1



++org.glassfish.jaxb
++jaxb-runtime
++2.3.1|code-block|syntax|javascript|2sjd5|请注意，从2.3.1版开始，您不再需要添加javax.activation。(请参阅|1ik4q|https://github.com/eclipse-ee4j/jaxb-ri/issues/1222|b8c7t|)^0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|V|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|W|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|X|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|Y|9|@]|A|@]|B|$]]|$2|I|4|J|6|7|8|Z|9|@]|A|@]|B|$]]|$2|K|4|L|6|M|8|10|9|@]|A|@]|B|$N|O]]|$2|P|4|Q|6|7|8|11|9|@]|A|@]|B|$]]|$2|R|4|S|6|7|8|12|9|@]|A|@]|B|$]]|$2|T|4|U|6|7|8|13|9|@]|A|@]|B|$]]]]

<h2>Clean solution for all JDKs &gt;= 9</h2>
You need to add two dependencies to your build
<ul>
<li>the jaxb-api</li>
<li>a jaxb implementation</li>
</ul>
As an implementation I chose to use the reference implementation by glassfish to get rid of old com.sun classes / libraries.
So as a result I added in my maven build
<pre><code>&lt;dependency&gt;
 &lt;groupId&gt;javax.xml.bind&lt;/groupId&gt;
 &lt;artifactId&gt;jaxb-api&lt;/artifactId&gt;
 &lt;version&gt;2.3.1&lt;/version&gt;
&lt;/dependency&gt;

&lt;dependency&gt;
 &lt;groupId&gt;org.glassfish.jaxb&lt;/groupId&gt;
 &lt;artifactId&gt;jaxb-runtime&lt;/artifactId&gt;
 &lt;version&gt;2.3.1&lt;/version&gt;
&lt;/dependency&gt;
</code></pre>
Note that from version 2.3.1 you don't need to add the javax.activation any longer. (see <a href="https://github.com/eclipse-ee4j/jaxb-ri/issues/1222" rel="noreferrer">https://github.com/eclipse-ee4j/jaxb-ri/issues/1222</a>)

entityMap|blocks|key|3qlso|text|我知道我来晚了，但我的错误最终需要一个不同的解决方案...超级简单|type|unstyled|depth|inlineStyleRanges|entityRanges|data|gcrj|我最初对Tomcat9进行了改进，并意识到我需要7。我忘记在build.xml中将类路径映射回7版本|tmfb|希望这将在未来修复某人的错误，谁能像我一样忽略这个简单的问题！^0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|G|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|H|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|I|9|@]|A|@]|B|$]]]]

I know I'm late to the party, but my error ended up needing a diffrent solution... super simple too

I originally depoloyed to Tomcat 9 and realised I needed 7... I forgot to map my class path back to the 7 version in build.xml

Hopefully this will fix someone elses error in the future, who manages to overlook this simple issue as I did!

entityMap|blocks|key|6c5u8|text|这是因为java版本如果您使用的是jdk+9或更高版本，只需将此代码添加到您的pom中即可。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|eung9|javax.xml.bind
++jaxb-api
++2.3.0|code-block|syntax|javascript^0|0^^$0|$]|1|@$2|3|4|5|6|7|8|H|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|I|9|@]|A|@]|B|$F|G]]]]

it´s because java version if you are using jdk 9 or a later version just add this to your pom

<pre><code>&lt;dependency&gt;
 &lt;groupId&gt;javax.xml.bind&lt;/groupId&gt;
 &lt;artifactId&gt;jaxb-api&lt;/artifactId&gt;
 &lt;version&gt;2.3.0&lt;/version&gt;
&lt;/dependency&gt;
</code></pre>

entityMap|blocks|key|7bgrq|text|由于JavaEE现在由|type|unstyled|depth|inlineStyleRanges|entityRanges|data|9q0a8|https://jakarta.ee/|6bd5q|，2.3.2版本的新Maven坐标为：|chke3|https://eclipse-ee4j.github.io/jaxb-ri/#maven-artifacts|eq79l|第一个发布的jaxb.version是2.3.2。|f9tes|2.3.2



++jakarta.xml.bind
++jakarta.xml.bind-api
++${jaxb.version}


++++org.glassfish.jaxb
++++jaxb-runtime
++++${jaxb.version}|code-block|syntax|javascript^0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|P|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|Q|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|R|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|S|9|@]|A|@]|B|$]]|$2|I|4|J|6|7|8|T|9|@]|A|@]|B|$]]|$2|K|4|L|6|M|8|U|9|@]|A|@]|B|$N|O]]]]

Since JavaEE is now governed by <a href="https://jakarta.ee/" rel="noreferrer">https://jakarta.ee/</a>, the new Maven coordinates as of 2.3.2 are:

<a href="https://eclipse-ee4j.github.io/jaxb-ri/#maven-artifacts" rel="noreferrer">https://eclipse-ee4j.github.io/jaxb-ri/#maven-artifacts</a>

The first released jaxb.version is 2.3.2.

<pre><code>&lt;properties&gt;
 &lt;jaxb.version&gt;2.3.2&lt;/jaxb.version&gt;
&lt;/properties&gt;

&lt;dependency&gt;
 &lt;groupId&gt;jakarta.xml.bind&lt;/groupId&gt;
 &lt;artifactId&gt;jakarta.xml.bind-api&lt;/artifactId&gt;
 &lt;version&gt;${jaxb.version}&lt;/version&gt;
&lt;/dependency&gt;
&lt;dependency&gt;
 &lt;groupId&gt;org.glassfish.jaxb&lt;/groupId&gt;
 &lt;artifactId&gt;jaxb-runtime&lt;/artifactId&gt;
 &lt;version&gt;${jaxb.version}&lt;/version&gt;
&lt;/dependency&gt;
</code></pre>

entityMap|blocks|key|a1kmg|text|旧答案“切换到amazoncorretto解决了问题”新闻答案:我使用corretto最新版本，但与jdk+1.8相似。所以不管怎样，我们需要手动添加依赖项|type|unstyled|depth|inlineStyleRanges|entityRanges|data^0^^$0|$]|1|@$2|3|4|5|6|7|8|C|9|@]|A|@]|B|$]]]]

Old answer "Problem resolved by switching to amazoncorretto"
News answer: I used corretto latest , but is similar jdk 1.8. so anyway we need add dependencies manually

entityMap|blocks|key|edans|text|编译Java+8目标时需要使用的依赖项版本。在Java+8、11和12+JRE中测试的应用程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|en9dm|javax.xml.bind
++++++++++++jaxb-api
++++++++++++2.2.8
++++++++
++++++++
++++++++++++com.sun.xml.bind
++++++++++++jaxb-core
++++++++++++2.2.8-b01
++++++++
++++++++
++++++++++++com.sun.xml.bind
++++++++++++jaxb-impl
++++++++++++2.2.8-b01|code-block|syntax|javascript^0|0^^$0|$]|1|@$2|3|4|5|6|7|8|H|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|I|9|@]|A|@]|B|$F|G]]]]

The dependency versions that I needed to use when compiling for Java 8 target. Tested application in Java 8, 11, and 12 JREs.

<pre><code> &lt;!-- replace dependencies that have been removed from JRE's starting with Java v11 --&gt;
 &lt;dependency&gt;
 &lt;groupId&gt;javax.xml.bind&lt;/groupId&gt;
 &lt;artifactId&gt;jaxb-api&lt;/artifactId&gt;
 &lt;version&gt;2.2.8&lt;/version&gt;
 &lt;/dependency&gt;
 &lt;dependency&gt;
 &lt;groupId&gt;com.sun.xml.bind&lt;/groupId&gt;
 &lt;artifactId&gt;jaxb-core&lt;/artifactId&gt;
 &lt;version&gt;2.2.8-b01&lt;/version&gt;
 &lt;/dependency&gt;
 &lt;dependency&gt;
 &lt;groupId&gt;com.sun.xml.bind&lt;/groupId&gt;
 &lt;artifactId&gt;jaxb-impl&lt;/artifactId&gt;
 &lt;version&gt;2.2.8-b01&lt;/version&gt;
 &lt;/dependency&gt;
 &lt;!-- end replace dependencies that have been removed from JRE's starting with Java v11 --&gt;
</code></pre>

entityMap|blocks|key|a031v|text|对我来说，在Java+11和gradle中是这样的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|cv7us|plugins+{
++++++id+'java'
}

dependencies+{
++++++runtimeOnly+'javax.xml.bind:jaxb-api:2.3.1'
}|code-block|syntax|javascript^0|0^^$0|$]|1|@$2|3|4|5|6|7|8|H|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|I|9|@]|A|@]|B|$F|G]]]]

For me in Java 11 and gradle this is what worked out:

<pre><code>plugins {
 id 'java'
}

dependencies {
 runtimeOnly 'javax.xml.bind:jaxb-api:2.3.1'
}
</code></pre>

entityMap|blocks|key|btoiq|text|您需要将jaxb依赖项添加到maven。glassfish实现版本2.3.2与新的jakarta+EE+jaxb+api版本2.3.2完全兼容。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1rtt|jakarta.xml.bind
++++jakarta.xml.bind-api
++++2.3.2




++++org.glassfish.jaxb
++++jaxb-runtime
++++2.3.2|code-block|syntax|javascript^0|0^^$0|$]|1|@$2|3|4|5|6|7|8|H|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|I|9|@]|A|@]|B|$F|G]]]]

You need to add jaxb dependancies to maven. The glassfish implementation version 2.3.2 is perfectly compatible with new jakarta EE jaxb api version 2.3.2.

<pre><code>&lt;!-- API --&gt;
&lt;dependency&gt;
 &lt;groupId&gt;jakarta.xml.bind&lt;/groupId&gt;
 &lt;artifactId&gt;jakarta.xml.bind-api&lt;/artifactId&gt;
 &lt;version&gt;2.3.2&lt;/version&gt;
&lt;/dependency&gt;

&lt;!-- Runtime --&gt;
&lt;dependency&gt;
 &lt;groupId&gt;org.glassfish.jaxb&lt;/groupId&gt;
 &lt;artifactId&gt;jaxb-runtime&lt;/artifactId&gt;
 &lt;version&gt;2.3.2&lt;/version&gt;
&lt;/dependency&gt;
</code></pre>

entityMap|blocks|key|elpa4|text|这解决了我在Java+12上运行Apache+Camel+2.24.1依赖项的问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|7bo9p|javax.activation
++++++++activation
++++++++1.1.1
++++

++++
++++++++javax.xml.bind
++++++++jaxb-api
++++++++2.3.1
++++

++++
++++++++com.sun.xml.bind
++++++++jaxb-core
++++++++2.3.0.1
++++

++++
++++++++com.sun.xml.bind
++++++++jaxb-impl
++++++++2.3.0.1|code-block|syntax|javascript^0|0^^$0|$]|1|@$2|3|4|5|6|7|8|H|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|I|9|@]|A|@]|B|$F|G]]]]

This solved my problems with dependencies running Apache Camel 2.24.1 on Java 12:

<pre><code> &lt;dependency&gt;
 &lt;groupId&gt;javax.activation&lt;/groupId&gt;
 &lt;artifactId&gt;activation&lt;/artifactId&gt;
 &lt;version&gt;1.1.1&lt;/version&gt;
 &lt;/dependency&gt;

 &lt;dependency&gt;
 &lt;groupId&gt;javax.xml.bind&lt;/groupId&gt;
 &lt;artifactId&gt;jaxb-api&lt;/artifactId&gt;
 &lt;version&gt;2.3.1&lt;/version&gt;
 &lt;/dependency&gt;

 &lt;dependency&gt;
 &lt;groupId&gt;com.sun.xml.bind&lt;/groupId&gt;
 &lt;artifactId&gt;jaxb-core&lt;/artifactId&gt;
 &lt;version&gt;2.3.0.1&lt;/version&gt;
 &lt;/dependency&gt;

 &lt;dependency&gt;
 &lt;groupId&gt;com.sun.xml.bind&lt;/groupId&gt;
 &lt;artifactId&gt;jaxb-impl&lt;/artifactId&gt;
 &lt;version&gt;2.3.0.1&lt;/version&gt;
 &lt;/dependency&gt;
</code></pre>

entityMap|blocks|key|ddvnk|text|在使用JDK+9%2B时，您需要添加JAX-B依赖项。对于Android+Studio用户，您需要将此代码添加到您的|type|unstyled|depth|inlineStyleRanges|entityRanges|data|8v4on|%25s|28lrf|数据块：|3o1ee|//+Add+missing+dependencies+for+JDK+9%2B
if+(JavaVersion.current().ordinal()+>=+JavaVersion.VERSION_1_9.ordinal())+{
++++//+If+you're+using+@AutoValue+or+any+libs+that+requires+javax.annotation+(like+Dagger)
++++compileOnly+'com.github.pengrad:jdk9-deps:1.0'
++++compileOnly+'javax.annotation:javax.annotation-api:1.3.2'

++++//+If+you're+using+Kotlin
++++kapt+"com.sun.xml.bind:jaxb-core:2.3.0.1"
++++kapt+"javax.xml.bind:jaxb-api:2.3.1"
++++kapt+"com.sun.xml.bind:jaxb-impl:2.3.2"

++++//+If+you're+using+Java
++++annotationProcessor+"com.sun.xml.bind:jaxb-core:2.3.0.1"
++++annotationProcessor+"javax.xml.bind:jaxb-api:2.3.1"

++++testAnnotationProcessor+"com.sun.xml.bind:jaxb-core:2.3.0.1"
++++testAnnotationProcessor+"javax.xml.bind:jaxb-api:2.3.1"
}|code-block|syntax|javascript^0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|L|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|M|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|N|9|@]|A|@]|B|$]]|$2|G|4|H|6|I|8|O|9|@]|A|@]|B|$J|K]]]]

You need to add JAX-B dependencies when using JDK 9+. For Android Studio user, you'll need to add this to your <code>build.gradle</code>'s <code>dependencies {}</code> block:

<pre><code>// Add missing dependencies for JDK 9+
if (JavaVersion.current().ordinal() &gt;= JavaVersion.VERSION_1_9.ordinal()) {
 // If you're using @AutoValue or any libs that requires javax.annotation (like Dagger)
 compileOnly 'com.github.pengrad:jdk9-deps:1.0'
 compileOnly 'javax.annotation:javax.annotation-api:1.3.2'

 // If you're using Kotlin
 kapt "com.sun.xml.bind:jaxb-core:2.3.0.1"
 kapt "javax.xml.bind:jaxb-api:2.3.1"
 kapt "com.sun.xml.bind:jaxb-impl:2.3.2"

 // If you're using Java
 annotationProcessor "com.sun.xml.bind:jaxb-core:2.3.0.1"
 annotationProcessor "javax.xml.bind:jaxb-api:2.3.1"

 testAnnotationProcessor "com.sun.xml.bind:jaxb-core:2.3.0.1"
 testAnnotationProcessor "javax.xml.bind:jaxb-api:2.3.1"
}
</code></pre>

entityMap|blocks|key|coi2l|text|您只需要一个依赖项：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|boq4g|dependencies+{
++++implementation+("jakarta.xml.bind:jakarta.xml.bind-api:2.3.2")|code-block|syntax|javascript^0|0^^$0|$]|1|@$2|3|4|5|6|7|8|H|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|I|9|@]|A|@]|B|$F|G]]]]

You only need 1 dependency:

<pre><code>dependencies {
 implementation ("jakarta.xml.bind:jakarta.xml.bind-api:2.3.2")
</code></pre>

entityMap|blocks|key|bjbbj|text|我还在使用ClassNotFoundException:javax.xml.bind.DatatypeConverter时遇到了问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|fdvd1|Java+11|coeke|和|dolqb|io.jsonwebtoken
++++jjwt
++++0.9.1|code-block|syntax|javascript|4bj5d|我尝试了添加javax.xml.bind:jaxb-api或spring+boot+jakarta.xml.bind-api。我在jjwt版本0.10.0中找到了修复的提示。但最重要的是，jjwt包现在被拆分了！|5du3|因此，请检查此引用：|1ivmp|https://github.com/jwtk/jjwt/issues/510|2r4lq|简单地说，如果您使用|d5il5|Java11和jjwt0.9.x，而你面对的是ClassNotFoundException:javax.xml.bind.DatatypeConverter问题，|6n62f|1mbk6|去找|aduop|jjwt版本0.11.x，但使用拆分的包：|aulv2|https://github.com/jwtk/jjwt#install|e6efh|你可能找不到更高版本的jjwt依赖，因为他们拆分了包。|4ak7d|干杯。^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|16|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|17|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|18|9|@]|A|@]|B|$]]|$2|G|4|H|6|I|8|19|9|@]|A|@]|B|$J|K]]|$2|L|4|M|6|7|8|1A|9|@]|A|@]|B|$]]|$2|N|4|O|6|7|8|1B|9|@]|A|@]|B|$]]|$2|P|4|Q|6|7|8|1C|9|@]|A|@]|B|$]]|$2|R|4|S|6|7|8|1D|9|@]|A|@]|B|$]]|$2|T|4|U|6|7|8|1E|9|@]|A|@]|B|$]]|$2|V|4|-4|6|7|8|1F|9|@]|A|@]|B|$]]|$2|W|4|X|6|7|8|1G|9|@]|A|@]|B|$]]|$2|Y|4|Z|6|7|8|1H|9|@]|A|@]|B|$]]|$2|10|4|11|6|7|8|1I|9|@]|A|@]|B|$]]|$2|12|4|13|6|7|8|1J|9|@]|A|@]|B|$]]|$2|14|4|15|6|7|8|1K|9|@]|A|@]|B|$]]]]

I also stumpled accross the ClassNotFoundException:javax.xml.bind.DatatypeConverter using Java 11 and
<pre><code>&lt;dependency&gt;
 &lt;groupId&gt;io.jsonwebtoken&lt;/groupId&gt;
 &lt;artifactId&gt;jjwt&lt;/artifactId&gt;
 &lt;version&gt;0.9.1&lt;/version&gt;
&lt;/dependency&gt;
</code></pre>
I tried all this stuff around adding javax.xml.bind:jaxb-api or spring boot jakarta.xml.bind-api .. I found a hint for fixes in jjwt version 0.10.0 .. but most importantly, the jjwt package is now split !
Thus, check this reference: <a href="https://github.com/jwtk/jjwt/issues/510" rel="noreferrer">https://github.com/jwtk/jjwt/issues/510</a>
Simply, if you use
<blockquote>
Java11 and
jjwt 0.9.x and
you face the ClassNotFoundException:javax.xml.bind.DatatypeConverter issue,
</blockquote>
go for
jjwt version 0.11.x, but use the splitted packages: <a href="https://github.com/jwtk/jjwt#install" rel="noreferrer">https://github.com/jwtk/jjwt#install</a>
You maven wont find a higher version for jjwt dependency, since they split the packages.
Cheers.

entityMap|blocks|key|e138r|text|作为|type|unstyled|depth|inlineStyleRanges|entityRanges|data|30mv2|官方文档|cqcvs|状态：|59qnt|升级时，您可能会遇到以下问题：|6ds8m|ft5ea|a9dev|Hibernate通常需要不再默认提供的JAXB。您可以使用Java9或Java10添加java.xml.bind模块来恢复此功能(即使该模块已被弃用)。|5kknu|从Java11开始，该模块不可用，因此您唯一的选择是添加JAXB+(从Java9开始，您可以这样做，而不是添加java.xml.bind模块：|dg2r9|6drpp|Maven|36npu|org.glassfish.jaxb
++++jaxb-runtime|code-block|syntax|javascript|b4f3f|Gradle+(build.gradle.kts)：|c607g|implementation("org.glassfish.jaxb:jaxb-runtime")|6fhlc|Gradle+(build.gradle)|5fakb|implementation+'org.glassfish.jaxb:jaxb-runtime'|7e42t|如果你更愿意指定一个特定的版本，看看这里：|9pdph|https://mvnrepository.com/artifact/org.glassfish.jaxb/jaxb-runtime^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|18|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|19|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|1A|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|1B|9|@]|A|@]|B|$]]|$2|I|4|-4|6|7|8|1C|9|@]|A|@]|B|$]]|$2|J|4|-4|6|7|8|1D|9|@]|A|@]|B|$]]|$2|K|4|L|6|7|8|1E|9|@]|A|@]|B|$]]|$2|M|4|N|6|7|8|1F|9|@]|A|@]|B|$]]|$2|O|4|-4|6|7|8|1G|9|@]|A|@]|B|$]]|$2|P|4|Q|6|7|8|1H|9|@]|A|@]|B|$]]|$2|R|4|S|6|T|8|1I|9|@]|A|@]|B|$U|V]]|$2|W|4|X|6|7|8|1J|9|@]|A|@]|B|$]]|$2|Y|4|Z|6|T|8|1K|9|@]|A|@]|B|$U|V]]|$2|10|4|11|6|7|8|1L|9|@]|A|@]|B|$]]|$2|12|4|13|6|T|8|1M|9|@]|A|@]|B|$U|V]]|$2|14|4|15|6|7|8|1N|9|@]|A|@]|B|$]]|$2|16|4|17|6|7|8|1O|9|@]|A|@]|B|$]]]]

As the <a href="https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-with-Java-9-and-above#jaxb" rel="nofollow noreferrer">official documentation</a> states:
<blockquote>
When upgrading you may face the following:
<code>java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException</code>
Hibernate typically requires JAXB that’s no longer provided by default. You can
add the java.xml.bind module to restore this functionality with Java9
or Java10 (even if the module is deprecated).
As of Java11, the module is not available so your only option is to
add the JAXB RI (you can do that as of Java9 in place of adding the
java.xml.bind module:
</blockquote>
<hr />
Maven
<pre><code>&lt;dependency&gt;
 &lt;groupId&gt;org.glassfish.jaxb&lt;/groupId&gt;
 &lt;artifactId&gt;jaxb-runtime&lt;/artifactId&gt;
&lt;/dependency&gt;
</code></pre>
Gradle (build.gradle.kts):
<pre><code>implementation(&quot;org.glassfish.jaxb:jaxb-runtime&quot;)
</code></pre>
Gradle (build.gradle)
<pre><code>implementation 'org.glassfish.jaxb:jaxb-runtime'
</code></pre>
If you rather specify a specific version, take a look here:
<a href="https://mvnrepository.com/artifact/org.glassfish.jaxb/jaxb-runtime" rel="nofollow noreferrer">https://mvnrepository.com/artifact/org.glassfish.jaxb/jaxb-runtime</a>

entityMap|blocks|key|drfgq|text|我在工作时遇到了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|a2co|Java项目|468uv|在|8um9h|Debian+10|502ke|..。|2h87s|每次启动应用程序时，它都会在日志文件中抛出错误：|cf60|java.lang.NoClassDefFoundError:+javax/xml/bind/JAXBException|2ac0j|d0vct|下面是我是如何解决这个问题的|c69bb|问题通常是在以下情况下引起的|cpj7r|JAXB|4pisc|类路径中缺少库(用于XML绑定的Java体系结构)。JAXB包含在JavaSE10或更早的版本中，但是从Java11或更新版本的-moved到Jakarta+EE项目下的Java中删除了JAXB。|fi5cv|因此，我使用以下命令检查了我的Java版本：|221ud|java+--version|code-block|syntax|javascript|2dutj|它给了我这个输出|caobt|openjdk+11.0.8+2020-07-14
OpenJDK+Runtime+Environment+(build+11.0.8%2B10-post-Debian-1deb10u1)
OpenJDK+64-Bit+Server+VM+(build+11.0.8%2B10-post-Debian-1deb10u1,+mixed+mode,+sharing)|39ta3|所以我遇到了|7mimb|JAXBException|2u0ha|错误，因为我正在使用|6goae|Java+11|clr3t|类路径中缺少JAXB库(用于XML绑定的Java体系结构)。JAXB包含在其中。|f2ia9|为了解决这个问题，我必须添加|eq56e|JAXB+API|dgsjv|库添加到|53r5e|库|fv9r9|(|1c349|)我的tomcat安装目录：|6i85s|sudo+wget+https://repo1.maven.org/maven2/javax/xml/bind/jaxb-api/2.4.0-b180830.0359/jaxb-api-2.4.0-b180830.0359.jar|ee4g2|然后我把它的名字从|7j6c7|至|8p0jo|sudo+mv+jaxb-api-2.4.0-b180830.0359.jar+jaxb-api.jar|8tpkv|注意|5l0bg|：确保将权限更改为允许tomcat访问文件，并将所有权更改为|9hptt|sudo+chown+-R+tomcat:tomcat+/opt/tomcat
sudo+chmod+-R+777+/opt/tomcat/|1gjkv|然后我重新启动了tomcat服务器：|buok|sudo+systemctl+restart+tomcat|7b8h2|资源|vq8o|：|1gg2v|[已解决]+java.lang.NoClassDefFoundError:+javax/xml/bind/JAXBException|f1us7|仅此而已。|fv7b9|我希望这能有所帮助^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|2M|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|2N|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|2O|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|2P|9|@]|A|@]|B|$]]|$2|I|4|J|6|7|8|2Q|9|@]|A|@]|B|$]]|$2|K|4|L|6|7|8|2R|9|@]|A|@]|B|$]]|$2|M|4|N|6|7|8|2S|9|@]|A|@]|B|$]]|$2|O|4|-4|6|7|8|2T|9|@]|A|@]|B|$]]|$2|P|4|Q|6|7|8|2U|9|@]|A|@]|B|$]]|$2|R|4|S|6|7|8|2V|9|@]|A|@]|B|$]]|$2|T|4|U|6|7|8|2W|9|@]|A|@]|B|$]]|$2|V|4|W|6|7|8|2X|9|@]|A|@]|B|$]]|$2|X|4|Y|6|7|8|2Y|9|@]|A|@]|B|$]]|$2|Z|4|10|6|11|8|2Z|9|@]|A|@]|B|$12|13]]|$2|14|4|15|6|7|8|30|9|@]|A|@]|B|$]]|$2|16|4|17|6|11|8|31|9|@]|A|@]|B|$12|13]]|$2|18|4|19|6|7|8|32|9|@]|A|@]|B|$]]|$2|1A|4|1B|6|7|8|33|9|@]|A|@]|B|$]]|$2|1C|4|1D|6|7|8|34|9|@]|A|@]|B|$]]|$2|1E|4|1F|6|7|8|35|9|@]|A|@]|B|$]]|$2|1G|4|1H|6|7|8|36|9|@]|A|@]|B|$]]|$2|1I|4|1J|6|7|8|37|9|@]|A|@]|B|$]]|$2|1K|4|1L|6|7|8|38|9|@]|A|@]|B|$]]|$2|1M|4|1N|6|7|8|39|9|@]|A|@]|B|$]]|$2|1O|4|1P|6|7|8|3A|9|@]|A|@]|B|$]]|$2|1Q|4|1R|6|7|8|3B|9|@]|A|@]|B|$]]|$2|1S|4|1T|6|7|8|3C|9|@]|A|@]|B|$]]|$2|1U|4|1V|6|11|8|3D|9|@]|A|@]|B|$12|13]]|$2|1W|4|1X|6|7|8|3E|9|@]|A|@]|B|$]]|$2|1Y|4|1Z|6|7|8|3F|9|@]|A|@]|B|$]]|$2|20|4|21|6|11|8|3G|9|@]|A|@]|B|$12|13]]|$2|22|4|23|6|7|8|3H|9|@]|A|@]|B|$]]|$2|24|4|25|6|7|8|3I|9|@]|A|@]|B|$]]|$2|26|4|27|6|11|8|3J|9|@]|A|@]|B|$12|13]]|$2|28|4|29|6|7|8|3K|9|@]|A|@]|B|$]]|$2|2A|4|2B|6|11|8|3L|9|@]|A|@]|B|$12|13]]|$2|2C|4|2D|6|7|8|3M|9|@]|A|@]|B|$]]|$2|2E|4|2F|6|7|8|3N|9|@]|A|@]|B|$]]|$2|2G|4|2H|6|7|8|3O|9|@]|A|@]|B|$]]|$2|2I|4|2J|6|7|8|3P|9|@]|A|@]|B|$]]|$2|2K|4|2L|6|7|8|3Q|9|@]|A|@]|B|$]]]]

I encountered this issue when working on a Java Project in Debian 10.
Each time I start the appliction it throws the error in the log file:
<blockquote>
java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
</blockquote>
Here's how I solved it:
The issue is often caused when JAXB library (Java Architecture for XML Binding) is missing in the classpath. JAXB is included in Java SE 10 or older, but it is removed from Java SE from Java 11 or newer –moved to Java EE under Jakarta EE project.
So, I checked my Java version using:
<pre><code>java --version
</code></pre>
And it gave me this output
<pre><code>openjdk 11.0.8 2020-07-14
OpenJDK Runtime Environment (build 11.0.8+10-post-Debian-1deb10u1)
OpenJDK 64-Bit Server VM (build 11.0.8+10-post-Debian-1deb10u1, mixed mode, sharing)
</code></pre>
So I was encountering the JAXBException error because I was using Java 11, which does not have the JAXB library (Java Architecture for XML Binding) is missing in the classpath. JAXB is included in it.
To fix the issue I had to add the <a href="https://mvnrepository.com/artifact/javax.xml.bind/jaxb-api" rel="noreferrer">JAXB API</a> library to the lib (<code>/opt/tomcat/lib</code>) directory of my tomcat installation:
<pre><code>sudo wget https://repo1.maven.org/maven2/javax/xml/bind/jaxb-api/2.4.0-b180830.0359/jaxb-api-2.4.0-b180830.0359.jar
</code></pre>
Then I renamed it from <code>jaxb-api-2.4.0-b180830.0359.jar</code> to <code>jaxb-api.jar</code>:
<pre><code>sudo mv jaxb-api-2.4.0-b180830.0359.jar jaxb-api.jar
</code></pre>
Note: Ensure that you change the permission allow tomcat access the file and also change the ownership to <code>tomcat</code>:
<pre><code>sudo chown -R tomcat:tomcat /opt/tomcat
sudo chmod -R 777 /opt/tomcat/
</code></pre>
And then I restarted the tomcat server:
<pre><code>sudo systemctl restart tomcat
</code></pre>
Resources: <a href="https://mail.codejava.net/coding/solved-java-lang-noclassdeffounderror-javax-xml-bind-jaxbexception" rel="noreferrer">[Solved] java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException</a>
That's all.
I hope this helps

I have some code that uses JAXB API classes which have been provided as a part of the JDK in Java 6/7/8. When I run the same code with Java 9, at runtime I get errors indicating that JAXB classes can not be found.

The JAXB classes have been provided as a part of the JDK since Java 6, so why can Java 9 no longer find these classes?

How to resolve java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

 我有一些使用JAXB API类的代码，这些类已作为Java 6/7/8中JDK的一部分提供。当我使用Java 9运行相同的代码时，在运行时收到错误，指示找不到JAXB类。 JAXB类是从Java 6开始作为JDK的一部分提供的，那么为什么Java 9不能再找到这些类呢？

问如何解析java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何解析java.lang.NoClassDefFoundError: javax/xml/bind/JAXBExceptionEN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何解析java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
EN