Hi Kelven, Sateesh! Not sure why but the class wasn't getting into any jar - I just recreated the workspace and that fixed the issue.. thanks a lot for the prompt help!
Regards, Vijay -----Original Message----- From: Sateesh Chodapuneedi Sent: Wednesday, July 10, 2013 9:31 PM To: Vijayendra Bhamidipati; [email protected] Subject: RE: bean injection failure Vijay, I did clean build. Not seeing error. Is ListVmwareDcsCmd.class in one of the jars? Probably you might want to do a grep in target directory. - Sateesh > -----Original Message----- > From: Kelven Yang > Sent: 11 July 2013 06:59 > To: [email protected] > Cc: Sateesh Chodapuneedi > Subject: Re: bean injection failure > > Is ListVmwareDcsCmd.class in one of the jars? > > Kelven > > On 7/10/13 5:55 PM, "Vijayendra Bhamidipati" > <[email protected]> wrote: > > >I'm running into the following spring exception when starting up the > >mgmt. server on latest master: > > > >org.springframework.beans.factory.BeanCreationException: Error > >creating bean with name 'apiDiscoveryServiceImpl': Injection of > >autowired dependencies failed; nested exception is > >org.springframework.beans.factory.BeanCreationException: Could not > >autowire field: protected java.util.List > >org.apache.cloudstack.discovery.ApiDiscoveryServiceImpl._services; > >nested exception is org.springframework.beans.factory.BeanCreationException: > >Error creating bean with name 'VmwareManager' defined in class path > >resource [nonossComponentContext.xml]: BeanPostProcessor before > >instantiation of bean failed; nested exception is > >java.lang.NoClassDefFoundError: ListVmwareDcsCmd > > at > >org.springframework.beans.factory.annotation.AutowiredAnnotationBeanP > >os > >tPr > >ocessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor. > >jav > >a:287) > > at > >org.springframework.beans.factory.support.AbstractAutowireCapableBean > >Fa > >cto > >ry.populateBean(AbstractAutowireCapableBeanFactory.java:1106) > >. > >. > > > >Looks like the ListVmwareDcsCmd bean is missing - I tried adding it > >to applicationContext.xml.in and even nonosscomponentContext.xml.in, > >but that isn't fixing the issue, and it's unclear to me why that's happening. > > Sateesh/team, can you please take a look? > > > >Cheers! > >Regards, > >Vijay
