eclipse - Bean marked with @Configuration fails in creation and fails startup of application -


i have spring mvc app created using spring 4.1.0.release. have class has been marked @configuration mark configuration class.

the xml config in application context below

<bean id="a" class="a"></bean> 

the application failing on startup following error. i'm using eclipse jetty 8 plugin.

org.springframework.beans.factory.beancreationexception: error creating bean name 'a' defined in servletcontext resource [/web-inf/applicationcontext.xml]: initialization of bean failed; nested exception java.lang.nosuchmethoderror: a(class name)(lorg/springframework/beans/factory/beanfactory;)v @ org.springframework.beans.factory.support.abstractautowirecapablebeanfactory.docreatebean(abstractautowirecapablebeanfactory.java:548) @ org.springframework.beans.factory.support.abstractautowirecapablebeanfactory.createbean(abstractautowirecapablebeanfactory.java:476) @ org.springframework.beans.factory.support.abstractbeanfactory$1.getobject(abstractbeanfactory.java:302) @ org.springframework.beans.factory.support.defaultsingletonbeanregistry.getsingleton(defaultsingletonbeanregistry.java:229) @ org.springframework.beans.factory.support.abstractbeanfactory.dogetbean(abstractbeanfactory.java:298) @ org.springframework.beans.factory.support.abstractbeanfactory.getbean(abstractbeanfactory.java:193) @ org.springframework.beans.factory.support.constructorresolver.instantiateusingfactorymethod(constructorresolver.java:370) @ org.springframework.beans.factory.support.abstractautowirecapablebeanfactory.instantiateusingfactorymethod(abstractautowirecapablebeanfactory.java:1113) @ org.springframework.beans.factory.support.abstractautowirecapablebeanfactory.createbeaninstance(abstractautowirecapablebeanfactory.java:1008) @ org.springframework.beans.factory.support.abstractautowirecapablebeanfactory.getsingletonfactorybeanfortypecheck(abstractautowirecapablebeanfactory.java:861) @ org.springframework.beans.factory.support.abstractautowirecapablebeanfactory.gettypeforfactorybean(abstractautowirecapablebeanfactory.java:791) @ org.springframework.beans.factory.support.abstractbeanfactory.istypematch(abstractbeanfactory.java:541) @ org.springframework.beans.factory.support.defaultlistablebeanfactory.dogetbeannamesfortype(defaultlistablebeanfactory.java:406) @ org.springframework.beans.factory.support.defaultlistablebeanfactory.getbeannamesfortype(defaultlistablebeanfactory.java:381) @ org.springframework.beans.factory.support.defaultlistablebeanfactory.getbeansoftype(defaultlistablebeanfactory.java:485) @ org.springframework.beans.factory.support.defaultlistablebeanfactory.getbeansoftype(defaultlistablebeanfactory.java:478) @ org.springframework.context.support.abstractapplicationcontext.getbeansoftype(abstractapplicationcontext.java:1052) @ org.springframework.amqp.rabbit.core.rabbitadmin.initialize(rabbitadmin.java:356) @ org.springframework.amqp.rabbit.core.rabbitadmin$11.oncreate(rabbitadmin.java:323) @ org.springframework.amqp.rabbit.connection.compositeconnectionlistener.oncreate(compositeconnectionlistener.java:32) @ org.springframework.amqp.rabbit.connection.cachingconnectionfactory.createconnection(cachingconnectionfactory.java:373) @ org.springframework.amqp.rabbit.connection.connectionfactoryutils$1.createconnection(connectionfactoryutils.java:80) @ org.springframework.amqp.rabbit.connection.connectionfactoryutils.dogettransactionalresourceholder(connectionfactoryutils.java:130) @ org.springframework.amqp.rabbit.connection.connectionfactoryutils.gettransactionalresourceholder(connectionfactoryutils.java:67) @ org.springframework.amqp.rabbit.listener.blockingqueueconsumer.start(blockingqueueconsumer.java:365) @ org.springframework.amqp.rabbit.listener.simplemessagelistenercontainer$asyncmessageprocessingconsumer.run(simplemessagelistenercontainer.java:1009) @ java.lang.thread.run(thread.java:745) 

the strange part application run fine on team mates systems not on mine.

any appreciated.

java.lang.nosuchmethoderror occurs if there issue jar loaded. think in machine trying run code on, has classpath set path loading older version of jar.

  1. it possible lower version of spring jars may exist in share folder or in class path.

  2. if maven project,do mvn dependency:tree , check other dependency loading lower version of spring.

  3. you can see paths of jars loaded in application.

public static void main(string[] args) {

urlclassloader classloader = (urlclassloader)currentclass.class.getclassloader(); system.out.println(arrays.tostring(classloader.geturls()));

}


Comments

Popular posts from this blog

javascript - Thinglink image not visible until browser resize -

firebird - Error "invalid transaction handle (expecting explicit transaction start)" executing script from Delphi -

mongodb - How to keep track of users making Stripe Payments -