박창준
unread,Dec 9, 2009, 8:27:16 PM12/9/09Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Korea Spring User Group
버전 : spring 2.5
순환참조관련에러인데 어떻게 해결해야 할지 모르겠습니다.
검색을 해봐도 뭘 어떻게 해야할지 감도 못잡겠고.. ^^;;
도움요청합니다.
[에러메세지]
[BORD0060_Biz] in its raw version as part of a circular reference, but
has eventually been wrapped (for example as part of auto-proxy
creation). This means that said other beans do not use the final
version of the bean. This is often the result of over-eager type
matching - consider using 'getBeanNamesOfType' with the
'allowEagerInit' flag turned off, for example.
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference
(BeanDefinitionValueResolver.java:274)
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary
(BeanDefinitionValueResolver.java:104)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues
(AbstractAutowireCapableBeanFactory.java:1274)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean
(AbstractAutowireCapableBeanFactory.java:1042)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean
(AbstractAutowireCapableBeanFactory.java:539)
Truncated. see log file for complete stacktrace
org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'BORD0010_Biz' defined in ServletContext
resource [/WEB-INF/xml/spring/applicationContext_ord_biz.xml]: Cannot
resolve reference to bean 'BORD0050_Biz' while setting bean property
'bord0050Biz'; nested exception is
org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'BORD0050_Biz' defined in ServletContext
resource [/WEB-INF/xml/spring/applicationContext_ord_biz.xml]: Cannot
resolve reference to bean 'BORD0020_Biz' while setting bean property
'bord0020Biz'; nested exception is
org.springframework.beans.factory.BeanCurrentlyInCreationException:
Error creating bean with name 'BORD0020_Biz': Bean with name
'BORD0020_Biz' has been injected into other beans [BORD0060_Biz] in
its raw version as part of a circular reference, but has eventually
been wrapped (for example as part of auto-proxy creation). This means
that said other beans do not use the final version of the bean. This
is often the result of over-eager type matching - consider using
'getBeanNamesOfType' with the 'allowEagerInit' flag turned off, for
example.
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference
(BeanDefinitionValueResolver.java:274)
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary
(BeanDefinitionValueResolver.java:104)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues
(AbstractAutowireCapableBeanFactory.java:1274)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean
(AbstractAutowireCapableBeanFactory.java:1042)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean
(AbstractAutowireCapableBeanFactory.java:539)
Truncated. see log file for complete stacktrace
org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'BORD0050_Biz' defined in ServletContext
resource [/WEB-INF/xml/spring/applicationContext_ord_biz.xml]: Cannot
resolve reference to bean 'BORD0020_Biz' while setting bean property
'bord0020Biz'; nested exception is
org.springframework.beans.factory.BeanCurrentlyInCreationException:
Error creating bean with name 'BORD0020_Biz': Bean with name
'BORD0020_Biz' has been injected into other beans [BORD0060_Biz] in
its raw version as part of a circular reference, but has eventually
been wrapped (for example as part of auto-proxy creation). This means
that said other beans do not use the final version of the bean. This
is often the result of over-eager type matching - consider using
'getBeanNamesOfType' with the 'allowEagerInit' flag turned off, for
example.
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference
(BeanDefinitionValueResolver.java:274)
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary
(BeanDefinitionValueResolver.java:104)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues
(AbstractAutowireCapableBeanFactory.java:1274)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean
(AbstractAutowireCapableBeanFactory.java:1042)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean
(AbstractAutowireCapableBeanFactory.java:539)
Truncated. see log file for complete stacktrace
org.springframework.beans.factory.BeanCurrentlyInCreationException:
Error creating bean with name 'BORD0020_Biz': Bean with name
'BORD0020_Biz' has been injected into other beans [BORD0060_Biz] in
its raw version as part of a circular reference, but has eventually
been wrapped (for example as part of auto-proxy creation). This means
that said other beans do not use the final version of the bean. This
is often the result of over-eager type matching - consider using
'getBeanNamesOfType' with the 'allowEagerInit' flag turned off, for
example.
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean
(AbstractAutowireCapableBeanFactory.java:553)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory
$1.run(AbstractAutowireCapableBeanFactory.java:485)
at java.security.AccessController.doPrivileged(Native Method)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean
(AbstractAutowireCapableBeanFactory.java:455)
at org.springframework.beans.factory.support.AbstractBeanFactory
$1.getObject(AbstractBeanFactory.java:251)
Truncated. see log file for complete stacktrace
>
<2009. 12. 10 오전 10시 22분 09초 KST> <Error> <Deployer> <BEA-149231>
<Unable to set the activation state to true for the application
'KtPointWebApp'.
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts
(WebAppModule.java:975)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:
361)
at weblogic.application.internal.flow.ModuleStateDriver$3.next
(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState
(StateMachineDriver.java:26)
at weblogic.application.internal.flow.ModuleStateDriver.start
(ModuleStateDriver.java:60)
Truncated. see log file for complete stacktrace
org.springframework.beans.factory.BeanCurrentlyInCreationException:
Error creating bean with name 'BORD0020_Biz': Bean with name
'BORD0020_Biz' has been injected into other beans [BORD0060_Biz] in
its raw version as part of a circular reference, but has eventually
been wrapped (for example as part of auto-proxy creation). This means
that said other beans do not use the final version of the bean. This
is often the result of over-eager type matching - consider using
'getBeanNamesOfType' with the 'allowEagerInit' flag turned off, for
example.
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean
(AbstractAutowireCapableBeanFactory.java:553)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory
$1.run(AbstractAutowireCapableBeanFactory.java:485)
at java.security.AccessController.doPrivileged(Native Method)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean
(AbstractAutowireCapableBeanFactory.java:455)
at org.springframework.beans.factory.support.AbstractBeanFactory
$1.getObject(AbstractBeanFactory.java:251)
Truncated. see log file for complete stacktrace
>
<2009. 12. 10 오전 10시 22분 09초 KST> <Notice> <Log Management>
<BEA-170027> <The server initialized the domain log broadcaster
successfully. Log messages will now be broadcasted to the domain log.>