WhatsTheCauseOfThisExceptionJavalangClassFormatErrorAbsentCode

最新推荐文章于 2024-11-10 00:10:22 发布

ivanyin111

最新推荐文章于 2024-11-10 00:10:22 发布

阅读量90

点赞数

分类专栏： java 文章标签： maven JavaEE JBoss SUN UP

本文链接：https://blog.csdn.net/ivanyin111/article/details/83943206

版权

java 专栏收录该内容

14 篇文章 0 订阅

订阅专栏

http://community.jboss.org/wiki/WhatsTheCauseOfThisExceptionJavalangClassFormatErrorAbsentCode

Background

When these artifacts were published to the Maven repository, Sun stripped out the code from classes that are classified as "implementations". So all the interfaces are code complete, yet any abstract class or implementation class has no code in it. Any attempt to use that class will likely blow up. That's why Arquillian is failing.

Here's an excerpt from the argument as to why Sun did this:

When one compiles, they want to run as well. By the way, we have been promoting full set of Java EE APIs which can only be used for compilation - they are stripped off method details. That way, user can't take those artifacts and try to use it in runtime.

The workaround is to not use javax.javaee-api but rather use the individual, "real" artifacts that you need. Unfortunately, there is no Maven scope available that will exclude a dependency from the test classpath.

There are two solutions to this problem.