Tika解析器在Wildfly上的部署问题 [英] Tika-Parsers deployment issue on Wildfly

问题描述

作为Web应用程序的一部分，我需要解析不同传入文件的文本内容。
这应该使用 tika-解析器非常简单，但是一旦我尝试在 Wildfly 部署我的webapp
（测试V.8.2）。 1和V.10.0.0.RC4）我遇到问题。

As part of a web application i need to parse textual content of different incoming files. This should be quite simple using tika-parsers, but as soon as i try to deploy my webapp on Wildfly (tested V.8.2.1 and V.10.0.0.RC4) i run into problems.

这是一个非常基本的webapp的我的maven依赖：

This is my maven dependency in a very basic webapp:

<groupId>org.apache.tika</groupId>
<artifactId>tika-parsers</artifactId>
<version>1.11</version>

这是我在部署过程中遇到的错误（手动部署或使用arquillian进行测试）：

This is the error i get during deployment (manual deployment or using arquillian for testing):

Caused by: java.lang.Exception: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"backend-test.war\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"backend-test.war\".WeldStartService: Failed to start service
    Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000071: Managed bean with a parameterized bean class must be @Dependent: class org.apache.cxf.jaxrs.provider.SourceProvider"}}

我假设有一个依赖冲突，但是没有关于如何避免它的线索。
beans.xml？ JBoss的部署，structure.xml？禁用任何wildfly模块？

I assume there is a dependency conflict, but have no clue on how to avoid it. beans.xml? jboss-deployment-structure.xml? Disable any wildfly modules?

Regards，
Philipp

Regards, Philipp

推荐答案

p>除了Tika将一大堆可疑的依赖关系转移到您的运行时类路径上的另一个非常不受欢迎的传递依赖关系的事实上，您正在遇到此问题：

Besides the fact that Tika dumps a gigantic pile of questionable dependencies with a further mountain of very unwelcome transitive dependencies onto your runtime classpath, you are running into this issue:

http://weld.cdi-spec.org/documentation/#4

https://issues.jboss.org/浏览/ CDI-377

基本上CDI 1.1中已经解决了CDI 1.2中的不兼容问题;在Wildfly手动更新Weld到2.3.x版本可能会完全消除问题。

Basically it is an incompatibility issue in CDI 1.1 that has been resolved in CDI 1.2; manually updating Weld to version 2.3.x in Wildfly may take the problem away entirely.

禁止进行手动升级，您可以通过声明META- INF / jboss-all.xml文件具有以下内容。假设你有战争，确切的路径是webapp / META-INF / jboss-all.xml。

Barring doing a manual upgrade, you can make the problem go away by declaring a META-INF/jboss-all.xml file with the following content. Assuming you have a war, the precise path is webapp/META-INF/jboss-all.xml.

<jboss xmlns="urn:jboss:1.0">
    <weld xmlns="urn:jboss:weld:1.0" require-bean-descriptor="true"/>
</jboss>

并确保定义一个WEB-INF / beans.xml文件（再次：假设一场战争）在您自己的需要CDI支持的模块中。这迫使Weld只尝试配置有一个beans.xml文件作为其中一部分的模块，哪个CXF将不会。

And make sure to define a WEB-INF/beans.xml file (again: assuming a war) in your own modules that need CDI support. This forces Weld to only try to configure modules which have a beans.xml file as part of them, which CXF will not.

除了我真的会调查依赖看看通过Tika拉入的东西;例如，您将发现javax.inject API放在编译范围上，因此与您的应用程序一起部署，您真的不想要的。

Besides all that I would really investigate the dependency tree and see what is pulled in through Tika; for example you will find that the javax.inject API is put on the compile scope and thus deployed with your application, something you really do not want.

这篇关于Tika解析器在Wildfly上的部署问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！