解决:javax.annotation.ManagedBean' found and supported for component scanning问题

本文记录了将项目从JDK7升级到JDK8后,访问时出现的Spring框架异常,包括详细的错误信息和解决过程,涉及jar包冲突及JSTL缺失问题。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

今天将负责的项目从jdk7升级到jdk8,启动正常,但是访问时候出现了这个错误,记录下来防止以后以后遇到不知道啥原因.

org.springframework.context.annotation.ClassPathBeanDefinitionScanner JSR-250 ‘javax.annotation.ManagedBean’ found and supported for component scanning
acspassos: (2019-04-09 19:14:50.157 [http-bio-9083-exec-1]) INFO - org.springframework.context.annotation.ClassPathBeanDefinitionScanner JSR-330 ‘javax.inject.Named’ annotation found and supported for component scanning
gframework.web.servlet.DispatcherServlet Context initialization failed
org.springframework.beans.factory.BeanDefinitionStoreException: Failed to read candidate component class: file [D:\PlatformSVN\acs\acspassos\target\classes\com\acs\acspassos\controller\BindCellphoneController.class]; nested exception is org.springframework.core.NestedIOException: ASM ClassReader failed to parse class file - probably due to a new Java class file version that isn’t supported yet: file [D:\PlatformSVN\acs\acspassos\target\classes\com\acs\acspassos\controller\BindCellphoneController.class]; nested exception is java.lang.IllegalArgumentException
at org.springframework.context.annotation.ClassPathScanningCandidateComponentProvider.findCandidateComponents(ClassPathScanningCandidateComponentProvider.java:281) ~[spring-context-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.context.annotation.ClassPathBeanDefinitionScanner.doScan(ClassPathBeanDefinitionScanner.java:242) ~[spring-context-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.context.annotation.ComponentScanBeanDefinitionParser.parse(ComponentScanBeanDefinitionParser.java:84) ~[spring-context-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.beans.factory.xml.NamespaceHandlerSupport.parse(NamespaceHandlerSupport.java:73) ~[spring-beans-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1438) ~[spring-beans-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1428) ~[spring-beans-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:185) ~[spring-beans-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.doRegisterBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:139) ~[spring-beans-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:108) ~[spring-beans-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:493) ~[spring-beans-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:390) ~[spring-beans-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:334) ~[spring-beans-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302) ~[spring-beans-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:174) ~[spring-beans-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:209) ~[spring-beans-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:180) ~[spring-beans-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:125) ~[spring-web-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:94) ~[spring-web-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:130) ~[spring-context-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:537) ~[spring-context-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:451) ~[spring-context-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.web.servlet.FrameworkServlet.configureAndRefreshWebApplicationContext(FrameworkServlet.java:651) ~[spring-webmvc-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:599) ~[spring-webmvc-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:665) ~[spring-webmvc-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.web.servlet.FrameworkServlet.initWebApplicationContext(FrameworkServlet.java:518) ~[spring-webmvc-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.web.servlet.FrameworkServlet.initServletBean(FrameworkServlet.java:459) ~[spring-webmvc-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.java:136) [spring-webmvc-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at javax.servlet.GenericServlet.init(GenericServlet.java:160) [tomcat-embed-core-7.0.47.jar:7.0.47]
at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1280) [tomcat-embed-core-7.0.47.jar:7.0.47]
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1193) [tomcat-embed-core-7.0.47.jar:7.0.47]
at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:865) [tomcat-embed-core-7.0.47.jar:7.0.47]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:136) [tomcat-embed-core-7.0.47.jar:7.0.47]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) [tomcat-embed-core-7.0.47.jar:7.0.47]
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502) [tomcat-embed-core-7.0.47.jar:7.0.47]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) [tomcat-embed-core-7.0.47.jar:7.0.47]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100) [tomcat-embed-core-7.0.47.jar:7.0.47]
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953) [tomcat-embed-core-7.0.47.jar:7.0.47]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) [tomcat-embed-core-7.0.47.jar:7.0.47]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) [tomcat-embed-core-7.0.47.jar:7.0.47]
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1041) [tomcat-embed-core-7.0.47.jar:7.0.47]
at org.apache.coyote.AbstractProtocolAbstractConnectionHandler.process(AbstractProtocol.java:603)[tomcat−embed−core−7.0.47.jar:7.0.47]atorg.apache.tomcat.util.net.JIoEndpointAbstractConnectionHandler.process(AbstractProtocol.java:603) [tomcat-embed-core-7.0.47.jar:7.0.47] at org.apache.tomcat.util.net.JIoEndpointAbstractConnectionHandler.process(AbstractProtocol.java:603)[tomcatembedcore7.0.47.jar:7.0.47]atorg.apache.tomcat.util.net.JIoEndpointSocketProcessor.run(JIoEndpoint.java:310) [tomcat-embed-core-7.0.47.jar:7.0.47]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_151]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_151]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_151]
Caused by: org.springframework.core.NestedIOException: ASM ClassReader failed to parse class file - probably due to a new Java class file version that isn’t supported yet: file [D:\PlatformSVN\acs\acspassos\target\classes\com\acs\acspassos\controller\BindCellphoneController.class]; nested exception is java.lang.IllegalArgumentException
at org.springframework.core.type.classreading.SimpleMetadataReader.(SimpleMetadataReader.java:56) ~[spring-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.core.type.classreading.SimpleMetadataReaderFactory.getMetadataReader(SimpleMetadataReaderFactory.java:80) ~[spring-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.core.type.classreading.CachingMetadataReaderFactory.getMetadataReader(CachingMetadataReaderFactory.java:102) ~[spring-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.context.annotation.ClassPathScanningCandidateComponentProvider.findCandidateComponents(ClassPathScanningCandidateComponentProvider.java:257) ~[spring-context-3.2.2.RELEASE.jar:3.2.2.RELEASE]
… 44 common frames omitted
Caused by: java.lang.IllegalArgumentException: null
at org.springframework.asm.ClassReader.(Unknown Source) ~[spring-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.asm.ClassReader.(Unknown Source) ~[spring-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.asm.ClassReader.(Unknown Source) ~[spring-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.core.type.classreading.SimpleMetadataReader.(SimpleMetadataReader.java:53) ~[spring-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
… 47 common frames omitted

百度之后发现是因为jar包重复,看到这里就猜测是servlet和jspjar包的原因,但是打开自己工程下的lib目录,没有发现这两个jar包,后来发现别的jar包重复也可能会报这个异常,索性把lib目录删掉了,此时出现的是另一个异常,详情可看这个页面https://blog.youkuaiyun.com/pioneer1010/article/details/89160639.原因是把jstl包也给删除了,导致解析jsp页面异常,从网上下载一个jar包,放到lib目录中就没事了.

<think>好的,我现在要解决用户的问题:Java中出现java.lang.ClassNotFoundException: javax.annotation.security.DeclareRoles的异常。首先,我需要理解这个问题的原因,然后找到合适的解决方案。 首先,用户提到的异常是类找不到,这说明在运行时,JVM无法加载指定的类。类名是javax.annotation.security.DeclareRoles,这属于Java的注解相关类。根据以往的知识,这类问题通常是因为缺少相关的依赖库,或者模块路径配置不正确,尤其是在使用Java 9及以上版本时,模块系统(JPMS)可能导致某些原本在早期版本中默认包含的类被移除或需要显式引入。 接下来,我需要回忆相关的解决方案。例如,之前处理过类似的ClassNotFoundException,比如javax.xml.bind相关的类缺失,解决方法通常是添加JAXB API的依赖,因为从Java 9开始,这些类被移出了Java SE的标准库,需要手动引入。类似地,javax.annotation包中的类可能也被移到了其他模块或需要额外依赖。 查阅用户提供的引用内容,特别是引用[3]和引用[4],都是关于处理JAXB相关类找不到的问题解决方法是添加jaxb-api等依赖。虽然问题不同,但思路相似,即添加缺失的依赖库。 接下来,我需要确认javax.annotation.security.DeclareRoles属于哪个库。根据Java EE的历史,这些注解类通常包含在Java EE的API库中,如javax.annotation-api。在Java EE转向Jakarta EE之后,部分包名发生了变化,但用户的问题中的类仍然属于javax.annotation包,因此可能需要添加旧的javax.annotation-api依赖。 检查Maven仓库,可以找到javax.annotation的依赖项,例如: ```xml <dependency> <groupId>javax.annotation</groupId> <artifactId>javax.annotation-api</artifactId> <version>1.3.2</version> </dependency> ``` 添加这个依赖应该能解决类找不到的问题。此外,如果用户使用的是Java 9+,并且项目使用模块化系统(module-info.java),需要确认模块是否打开了必要的导出,或者是否添加了requires javax.annotation.api。 另外,可能的其他情况包括依赖冲突或版本不兼容,但根据常见的解决方式,首先应该尝试添加显式依赖。 总结解决方案的步骤应该是: 1. 添加javax.annotation-api依赖。 2. 确保构建工具正确引入依赖。 3. 检查模块配置(如果使用模块化系统)。 4. 清理并重新构建项目。 最后,生成相关问题,比如其他注解类缺失的问题,或者模块化配置的问题,以便用户进一步了解可能遇到的类似情况。</think>### 解决方案 出现`java.lang.ClassNotFoundException: javax.annotation.security.DeclareRoles`的原因是Java项目缺少包含该类的依赖库。`DeclareRoles`属于Java EE安全注解的一部分,在Java 9及以上版本中,部分Java EE模块被移除,需手动添加依赖。 #### 具体步骤: 1. **添加依赖** 在Maven项目中,添加`javax.annotation-api`依赖(包含`javax.annotation.security`包): ```xml <dependency> <groupId>javax.annotation</groupId> <artifactId>javax.annotation-api</artifactId> <version>1.3.2</version> </dependency> ``` Gradle项目则添加: ```groovy implementation 'javax.annotation:javax.annotation-api:1.3.2' ``` 2. **模块化项目检查**(Java 9+) 若项目使用`module-info.java`,需添加模块声明: ```java requires java.annotation; ``` 3. **清理并重新构建** 执行`mvn clean install`或Gradle的`clean build`,确保依赖生效。 #### 补充说明 - 该类通常用于声明EJB或Web应用的角色权限注解(如`@DeclareRoles`),常见于Java EE/Jakarta EE项目[^1][^3]。 - 若使用Spring Boot,需排除冲突依赖或调整版本兼容性。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值