[Springframework-developer] Re: Error message with no context

[Barry K. <gr...@me...>]

This error was caused due a parent bean with no class attribute but also no lazy-init=true.
That was easy enough to fix, but it would be nice if the error message
indicated the bean name.

-bk

Barry Kaplan wrote:

> I just got this exception at startup:
> 
> org.springframework.beans.factory.BeanCreationException: Error creating 
> bean with name 'com.its' defined in URL 
> [file:/C:/cvs.local/its.dev/_build/idea4/server/beanRefFactory.xml]: 
> Instantiation of bean failed; nested exception is 
> org.springframework.beans.FatalBeanException: Could not instantiate 
> class 
> [org.springframework.context.support.ClassPathXmlApplicationContext]; 
> constructor threw exception; nested exception is 
> java.lang.IllegalStateException: Bean definition does not carry a 
> resolved bean class
> org.springframework.beans.FatalBeanException: Could not instantiate 
> class 
> [org.springframework.context.support.ClassPathXmlApplicationContext]; 
> constructor threw exception; nested exception is 
> java.lang.IllegalStateException: Bean definition does not carry a 
> resolved bean class
> java.lang.IllegalStateException: Bean definition does not carry a 
> resolved bean class
> 
> The exception message does not indicate /which/ bean it is refering to.
> 
> -bk
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by OSTG. Have you noticed the changes on
> Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
> one more big change to announce. We are now OSTG- Open Source Technology
> Group. Come see the changes on the new OSTG site. www.ostg.com