我正在尝试包装灰熊与泽西作为一个单一的罐子使用Maven阴影插件。但是我总是收到No container provider supports the type class org.glassfish.grizzly.http.server.HttpHandler这样的消息
代码在Eclipse中运行良好,但不能在打包的jar中运行:
public class Main {
private static URI getBaseURI() {
return UriBuilder.fromUri("http://localhost/").port(9998).build();
}
public static final URI BASE_URI = getBaseURI();
protected static HttpServer startServer() throws IOException {
System.out.println("Starting grizzly...");
ResourceConfig rc = new PackagesResourceConfig("share.test");
rc.getFeatures().put(JSONConfiguration.FEATURE_POJO_MAPPING, Boolean.TRUE);
return GrizzlyServerFactory.createHttpServer(BASE_URI, rc);
}
public static void main(String[] args) throws IOException {
HttpServer httpServer = startServer();
System.in.read();
httpServer.stop();
}
}下面是一个完整的例外
$ java -jar target/webServiceTest-0.0.1-SNAPSHOT.jar
Starting grizzly...
Mar 20, 2012 12:48:53 PM com.sun.jersey.api.core.PackagesResourceConfig init
INFO: Scanning for root resource and provider classes in the packages:
share.test
Mar 20, 2012 12:48:54 PM com.sun.jersey.api.core.ScanningResourceConfig logClasses
INFO: Root resource classes found:
class share.test.NonJAXBBeanResource
class share.test.Hello
Mar 20, 2012 12:48:54 PM com.sun.jersey.api.core.ScanningResourceConfig init
INFO: No provider classes found.
Exception in thread "main" java.lang.IllegalArgumentException: No container provider supports the type class org.glassfish.grizzly.http.server.HttpHandler
at com.sun.jersey.api.container.ContainerFactory.createContainer(ContainerFactory.java:196)
at com.sun.jersey.api.container.ContainerFactory.createContainer(ContainerFactory.java:134)
at com.sun.jersey.api.container.grizzly2.GrizzlyServerFactory.createHttpServer(GrizzlyServerFactory.java:242)
at share.test.Main.startServer(Main.java:27)
at share.test.Main.main(Main.java:31)我正在使用maven构建jar包。
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-shade-plugin</artifactId>
<version>1.5</version>
<configuration>
<transformers>
<transformer implementation="org.apache.maven.plugins.shade.resource.ManifestResourceTransformer">
<manifestEntries>
<Main-Class>share.test.Main</Main-Class>
<Build-Number>1</Build-Number>
</manifestEntries>
</transformer>
</transformers>
</configuration>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>shade</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>我是否需要更改阴影插件以包含其他内容?
发布于 2012-03-21 17:38:15
错误看起来像是插件没有正确地合并来自不同jars的META-INF/services记录-如果在几个jars的META-INF/services目录中有多个同名的文件,它们需要合并,而不是用另一个替换。检查是否是这种情况。
发布于 2015-03-16 00:15:22
以下链接帮助我找出了下面的解决方案:
尤其是答案
您没有使用带有依赖项的jar作为您的程序集插件配置的descriptorRef,而是创建了我们自己的程序集,例如在src/assembly/depmerge.xml中(见下文)。此组装配置将添加一个负责META-INF/ containerDescriptorHandler的服务。
跑
mvn clean compile assembly:single要获取目标中的jar文件,您可以使用
java -jar target/x.y.-version-jar-with-dependencies.jarpom.xml:
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.5.3</version>
<configuration>
<archive>
<manifest>
<mainClass>${mainClass}</mainClass>
</manifest>
</archive>
<descriptor>src/assembly/depmerge.xml</descriptor>
</configuration>
</plugin>src/assembly/depmerge.xml:
<!--
see http://maven.apache.org/guides/mini/guide-assemblies.html
see http://maven.apache.org/plugins/maven-assembly-plugin/descriptor-refs.html
-->
<assembly
xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2 http://maven.apache.org/xsd/assembly-1.1.2.xsd">
<!-- TODO: a jarjar format would be better -->
<id>jar-with-dependencies-and-services</id>
<formats>
<format>jar</format>
</formats>
<includeBaseDirectory>false</includeBaseDirectory>
<dependencySets>
<dependencySet>
<outputDirectory>/</outputDirectory>
<useProjectArtifact>true</useProjectArtifact>
<unpack>true</unpack>
<scope>runtime</scope>
</dependencySet>
</dependencySets>
<!--
https://stackoverflow.com/questions/1607220/how-can-i-merge-resource-files-in-a-maven-assembly
-->
<containerDescriptorHandlers>
<containerDescriptorHandler>
<handlerName>metaInf-services</handlerName>
</containerDescriptorHandler>
</containerDescriptorHandlers>
</assembly>发布于 2012-09-19 10:24:40
我只是犯了个愚蠢的错误。也可以在pom中配置maven-assembly-plugin。
程序集似乎替换了META-INF/services并覆盖了文件com.sun.jersey.spi.container.ContainerProvider中的"com.sun.jersey.server.impl.container.grizzly2.GrizzlyContainerProvider
正如guide http://maven.apache.org/plugins/maven-assembly-plugin/提到的,如果您的项目想要将工件打包到一个超jar中,组装插件只提供基本的支持。要获得更多控制,请使用Maven Shade插件。
<!-- mvn assembly:assembly -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-assembly-plugin</artifactId>
<configuration>
<archive>
<manifest>
<addClasspath>true</addClasspath>
<mainClass>XXX.DaemonMain</mainClass>
</manifest>
</archive>
<descriptorRefs>
<descriptorRef>jar-with-dependencies</descriptorRef>
</descriptorRefs>
</configuration>
</plugin> https://stackoverflow.com/questions/9787265
复制相似问题