non-compatible bean definition of same name and class
2013-04-24 14:38
603 查看
在整合struts2.1.6+spring2.5.6开发中,使用了注解和struts-convention来实现零配置管理。spring也使用注解annotation方式。现在的问题是:我在连个个不同package中有两个相同名称的类,只是类所在的目录不同。例如在 com.idearsoft.idear.module.SystemMaintain.action下有个HomeAction.java,在 com.idearsoft.idear.module.Main.action也有一个HomeAction.java。在应用服务器启动时总是提示这两个homeAction 冲突。
回答:
spring管理bean大概类似把bean实例化放到map中,它会以配置的id和name(如果配置的话)
为key存放起来,2个一样的肯定要成冲突楼主应该给他们换个名字就成啦
controller("systemHomeAction")
controller("moduleHomeAction")
回答:
spring管理bean大概类似把bean实例化放到map中,它会以配置的id和name(如果配置的话)
为key存放起来,2个一样的肯定要成冲突楼主应该给他们换个名字就成啦
controller("systemHomeAction")
controller("moduleHomeAction")
相关文章推荐
- SpringMVC conflicts with existing, non-compatible bean definition of same name and class 的解决办法
- non-compatible bean definition of same name and class
- ....conflicts with existing, non-compatible bean definition of same name and class
- 记录:non-compatible bean definition of same name and class [com.XXX.XXX]
- spring 'arroudAspect' for bean class [com.dw.test.ArroudAspect] conflicts with existing, non-compatible bean definition of same name and class [com.dw.aspect.ArroudAspect]
- SpringMVC conflicts with existing, non-compatible bean definition of same name and class 的解决办法
- conflicts with existing, non-compatible bean definition of same name and class
- non-compatible bean definition of same name and class [x
- SpringMVC conflicts with existing, non-compatible bean definition of same name and class 的解决办法
- 【spring】non-compatible bean definition of same name and class
- 异常解决:non-compatible bean definition of same name and class【com.xxx.xxx.XXX】
- SpringMVC conflicts with existing, non-compatible bean definition of same name and class 的解决办法 问题起因
- SpringMVC 启动报错,conflicts with existing, non-compatible bean definition of same name and class ...
- SpringMVC conflicts with existing, non-compatible bean definition of same name and class 的解决办法,sprin
- conflicts with existing, non-compatible bean definition of same name and class
- SpringMVC中类名重名(SpringMVC conflicts with existing, non-compatible bean definition of same name )
- 关于问题The fully qualified name of the bean's class, except if it serves only as a parent definition fo
- 关于问题The fully qualified name of the bean's class, except if it serves only as a parent definition fo
- whether the results are the same of getClass().getName() called in child class and parent class?
- 关于问题The fully qualified name of the bean's class, except if it serves only as a parent definition fo