【问题标题】:Tomcat 7 does not scan annotations when using Jersey 2Tomcat 7 使用 Jersey 2 时不扫描注解
【发布时间】:2015-12-10 14:02:29
【问题描述】:

我有一个 Jersey 2 Maven 项目。

web.xml:

<?xml version="1.0" encoding="UTF-8"?>
<!-- This web.xml file is not required when using Servlet 3.0 container,
see implementation details http://jersey.java.net/nonav/documentation/latest/jax-rs.html -->
<web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
    <servlet>
        <servlet-name>com.api.rest.ApplicationResource</servlet-name>
        <servlet-class>org.glassfish.jersey.servlet.ServletContainer</servlet-class>        
        <load-on-startup>1</load-on-startup>
    </servlet>
    <servlet-mapping>
        <servlet-name>com.api.rest.ApplicationResource</servlet-name>
        <url-pattern>/api/*</url-pattern>
    </servlet-mapping>
</web-app>

pom.xml

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">

    <modelVersion>4.0.0</modelVersion>

    <groupId>com.api</groupId>
    <artifactId>GLI_API</artifactId>
    <packaging>war</packaging>
    <version>1.0-SNAPSHOT</version>
    <name>GLI_API</name>

    <build>
        <finalName>GLI_API</finalName>
        <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-compiler-plugin</artifactId>
                <version>2.5.1</version>
                <inherited>true</inherited>
                <configuration>
                    <source>1.8</source>
                    <target>1.8</target>
                </configuration>
            </plugin>
        </plugins>
    </build>

    <dependencyManagement>
        <dependencies>
            <dependency>
                <groupId>org.glassfish.jersey</groupId>
                <artifactId>jersey-bom</artifactId>
                <version>${jersey.version}</version>
                <type>pom</type>
                <scope>import</scope>
            </dependency>
        </dependencies>
    </dependencyManagement>

    <dependencies>
        <dependency>
            <groupId>org.glassfish.jersey.containers</groupId>
            <artifactId>jersey-container-servlet</artifactId>
            <!-- use the following artifactId if you don't need servlet 2.x compatibility -->
            <!-- artifactId>jersey-container-servlet</artifactId -->
        </dependency>

        <dependency>
            <groupId>org.glassfish.jersey.media</groupId>
            <artifactId>jersey-media-moxy</artifactId>
        </dependency>

        <dependency>
            <groupId>org.glassfish.jersey.media</groupId>
            <artifactId>jersey-media-multipart</artifactId>
            <version>2.21</version>
        </dependency>


        <dependency>
            <groupId>com.zaxxer</groupId>
            <artifactId>HikariCP-java6</artifactId>
            <version>2.2.5</version>
        </dependency>
        <dependency>
            <groupId>mysql</groupId>
            <artifactId>mysql-connector-java</artifactId>
            <version>5.1.36</version>
        </dependency>
        <dependency>
            <groupId>commons-codec</groupId>
            <artifactId>commons-codec</artifactId>
            <version>1.9</version>
        </dependency>
        <dependency>
            <groupId>org.codehaus.jackson</groupId>
            <artifactId>jackson-mapper-asl</artifactId>
            <version>1.9.13</version>
        </dependency>
        <dependency>
            <groupId>org.mindrot</groupId>
            <artifactId>jbcrypt</artifactId>
            <version>0.3m</version>
        </dependency>
        <dependency>
            <groupId>net.sf.json-lib</groupId>
            <artifactId>json-lib</artifactId>
            <version>2.4</version>
            <classifier>jdk15</classifier>
        </dependency>
        <dependency>
            <groupId>com.cloudinary</groupId>
            <artifactId>cloudinary-http44</artifactId>
            <version>1.2.1</version>
        </dependency>
    </dependencies>
    <properties>
        <jersey.version>2.19</jersey.version>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    </properties>
</project>

我的项目在本地工作时运行良好。但是当我将它部署在我的远程服务器上时它不再起作用了。

所以基本上发生的情况是,WAR 被正确部署,但在 catalina.out 中实际上没有错误或警告。我在每个定义的端点上都得到 404。

catalina.out

Sep 14, 2015 2:03:00 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive /var/lib/tomcat7/webapps/GLI_API.war
Sep 14, 2015 2:04:17 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive /var/lib/tomcat7/webapps/ICDS_API.war
Sep 14, 2015 2:04:23 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /var/lib/tomcat7/webapps/ROOT
Sep 14, 2015 2:04:23 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8080"]
Sep 14, 2015 2:04:23 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 84867 ms

应用资源

package com.api.rest;

import java.util.logging.Logger;


import org.glassfish.jersey.filter.LoggingFilter;
import org.glassfish.jersey.server.ResourceConfig;
import org.glassfish.jersey.server.ServerProperties;
import com.api.provider.ResponseCorsFilter;
import org.glassfish.jersey.media.multipart.MultiPartFeature;


public class ApplicationResource extends ResourceConfig {

    private static final Logger LOGGER = null;   


    public ApplicationResource() {
        // Register resources and providers using package-scanning.
        packages("com.api");
        System.out.println("started");

        register(MultiPartFeature.class);

        // Register my custom provider - not needed if it's in my.package.
        register(ResponseCorsFilter.class);
        // Register an instance of LoggingFilter.
        register(new LoggingFilter(LOGGER, true));

        // Enable Tracing support.
        property(ServerProperties.TRACING, "ALL");
    }
}

可能是什么问题?我在tomcat8上开发(但不记得具体使用了什么)并部署在tomcat7上。这会是个问题吗?


这个端点应该是可达的:http://54.228.220.152:8080/GLI_API/api/item

其他 API 工作正常 - 所以服务器一般都在工作。

另外 - 如果你没有最终答案,如果你能指出我要查看的文件/目录,我将非常感激,因为我没有收到任何错误。

【问题讨论】:

  • 你能把 1 设置为 0 或 -1 吗?
  • 你能粘贴你的 API 控制器代码吗?
  • 也许这篇文章能帮上忙——stackoverflow.com/questions/17616708/…
  • 查看编辑 :) 将检查启动时加载
  • 好的——我从这篇文章中得到的是添加@ApplicationPath("/")——很快就会报告。 load-on-startup 0/1 没有影响:(

标签: java maven tomcat annotations jersey-2.0


【解决方案1】:

您可以尝试通过将此初始化参数设置为您的 servlet 来启用注释扫描:

<servlet>
 ...
 <servlet-class>org.glassfish.jersey.servlet.ServletContainer</servlet-class>

 <init-param>
  <param-name>jersey.config.server.provider.packages</param-name>
  <param-value>com.yourproject.packageWhereYourResourcesAre</param-value>
 </init-param>
...
</servlet>

更新

您似乎已针对 Java 8 进行编译,而 Tomcat 则使用 Java 7 运行?试试这个:

<configuration>
    <source>1.7</source>
    <target>1.7</target>
</configuration>

您可能还想将您的 web.xml 更新到 3.0:

<web-app version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd">

【讨论】:

  • 非常感谢 - 这有帮助。我现在可以使用不受支持的主要次要版本。我以为我的控制器中有这个:packages("com.api");有什么区别?我有时在 web.xml 和我的 ApplicationController 之间很困惑
  • 结果:我在 JDK 1.8 中编译,但服务器上没有 - 哎哟:(
猜你喜欢
  • 1970-01-01
  • 2013-12-31
  • 1970-01-01
  • 2021-05-04
  • 2012-05-19
  • 2015-01-26
  • 2012-04-07
  • 1970-01-01
  • 2011-07-05
相关资源
最近更新 更多