Class not found CallableProcessingInterceptor: migrated to 3.1.4

前端 未结 1 635
温柔的废话
温柔的废话 2021-01-26 18:14

Stack trace:

SEVERE: Servlet /tsl threw load() exception
java.lang.ClassNotFoundException: org.springframework.web.context.request.async.CallableProcessingInterc         


        
相关标签:
1条回答
  • 2021-01-26 18:35

    Similar answer to this question and this question - the answer is one of:

    • You have some old JAR files remaining in your deployment directory from an attempted upgrade to Spring 3.2.x (where this class exists), followed by a downgrade to Spring 3.0.x or 3.1.x
    • You have conflicting dependencies, with different versions of Spring (i.e. some 3.1 and some 3.2 dependencies). This can be determined by running mvn dependency:tree from your build directory. Look for conflicting versions.

    In fact, I did notice that your project has issues with conflicting versions, dependency:tree does show conflicts with some of the Spring components:

    [INFO] +- org.springframework.security:spring-security-core:jar:3.1.3.RELEASE:compile
    [INFO] |  +- org.springframework:spring-aop:jar:3.0.7.RELEASE:compile
    [...snip...]
    [INFO] +- org.springframework.ws:spring-ws-core:jar:2.1.2.RELEASE:compile
    [INFO] |  +- org.springframework.ws:spring-xml:jar:2.1.2.RELEASE:compile
    [INFO] |  +- org.springframework:spring-oxm:jar:3.1.3.RELEASE:compile
    

    Although you are trying to include Spring 3.1.4.RELEASE, you can see some components are pulling in different versions since you haven't specified them specifically.

    This isn't causing the issue in this question, but it may over time lead to similar problems.

    0 讨论(0)
提交回复
热议问题