but was actually of type 'com.sun.proxy.$Proxy16'
程序员文章站
2022-07-04 22:06:15
...
报错信息如下
org.springframework.beans.factory.BeanNotOfRequiredTypeException: Bean named 'userServiceImpl' is expected to be of type 'com.swdeve.spring.ioc.service.impl.UserServiceImpl' but was actually of type 'com.sun.proxy.$Proxy16'
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:389)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:204)
at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1093)
at com.swdeve.spring.ioc.service.impl.JunitTest.test(JunitTest.java:21)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:541)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:763)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:463)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:209)
引起报错的那行代码如下
UserService userService = ctx.getBean("userServiceImpl",UserServiceImpl.class);
原因分析:
项目中使用了org.aspectj.lang.annotation.Aspect切面技术,即UserServiceImpl是一个切入点,针对org.aspectj.lang.annotation.Aspect的实现原理是基于接口的动态代理技术,而不是基于实现类的动态代理技术,所以以上代码应该改为
UserService userService = ctx.getBean("userServiceImpl",UserService.class);
自此,问题解决
上一篇: 操作系统相关概念
下一篇: 揭开面纱看看黑客用哪些工具(2)
推荐阅读
-
but was actually of type 'com.sun.proxy.$Proxy**'的两种解决方法
-
but was actually of type 'com.sun.proxy.$Proxy16'
-
spring中动态代理 but was actually of type [com.sun.proxy.$Proxy18]
-
解决使用@AutoWired注入出现的but was actually of type 'com.sun.proxy.$Proxy**问题
-
关于 but was actually of type 'com.sun.proxy.$Proxy14'
-
but was actually of type ‘com.sun.proxy.$Proxy**‘ AOP事务代理混用
-
but was actually of type 'com.sun.proxy.$Proxy18'
-
Bean named ‘Target‘ is expected to be of type ‘com.itheima.aop.Target‘ but was actually of type ‘com
-
**Bean named 'XXX' is expected but was actually of type 'com.sun.proxy.$Proxy**'的两种解决方法**
-
声明式事务配置报错:but was actually of type 'com.sun.proxy.$Proxy**'解决