[Building Sakai] Help needed on Evaluation Tool

[Liu, Peter]

Thanks Adam and I will take a look at the trunk.

________________________________
From: Adam Marshall [mailto:adam.marshall at oucs.ox.ac.uk]
Sent: Tuesday, March 30, 2010 10:06 AM
To: Liu, Peter; sakai-dev
Subject: RE: Help needed on Evaluation Tool

we use trunk. that's what we were recommended to use.

adam

From: sakai-dev-bounces at collab.sakaiproject.org [mailto:sakai-dev-bounces at collab.sakaiproject.org] On Behalf Of Liu, Peter
Sent: 30 March 2010 14:32
To: sakai-dev
Subject: [Building Sakai] Help needed on Evaluation Tool

Hi,

I am trying to deploy the Evaluation Tool for our Sakai 2.6.x version. What would be the best version of Evaluation Tool to use?

Currently, I try to use the CT_2-6-x (https://source.sakaiproject.org/contrib/evaluation/branches/CT_2-6-x) for our Sakai-2.6.x version.
However, I cannot get it to work due to the following error message (shown at end of the email). It complaints the reference circulation issues during the tomcat (5.5.26) start. I have made some digging and find out that the following two beans are referenced to each other.


File: external-logic.xml
<bean
      id="org.sakaiproject.evaluation.logic.externals.EvalExternalLogic"
      class="org.sakaiproject.evaluation.logic.externals.EvalExternalLogicImpl"
      init-method="init">
      ....
      <property name="settings" ref="org.sakaiproject.evaluation.logic.EvalSettings" />
      ....
</bean>

File: spring-hibernate.xml
<bean id="org.sakaiproject.evaluation.logic.EvalSettings"
        class="org.sakaiproject.evaluation.logic.EvalSettingsImpl" init-method="init">
        <property name="dao" ref="org.sakaiproject.evaluation.dao.EvaluationDao" />
        <property name="externalLogic"
            ref="org.sakaiproject.evaluation.logic.externals.EvalExternalLogic" />
    </bean>



Do I missing any configuration setting to solve this circulation? Or this is a bug in the current branch.

It will be highly appreciated if you can provide any suggestion.


--------------------------------------------------
Peter Liu
Academic Media & Technology
Information Technology Services
Yale University

Office: 203 432-7867


2010-03-29 20:48:46,097  INFO main org.sakaiproject.component.app.scheduler.ScheduledInvocationManagerImpl - init()
2010-03-29 20:48:46,394 ERROR main org.sakaiproject.util.NoisierDefaultListableBeanFactory - Failed to preinstantiate the singleton named org.sakaiproject.entitybroker.impl.event.EventReceiverCoordinator. Destroying all Spring beans.
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.sakaiproject.evaluation.logic.entity.ConfigEntityProvider' defined in file [C:\apache-tomcat-sakai2.6-5.26\components\sakai-evaluation-pack\WEB-INF\entity-providers.xml]: Cannot resolve reference to bean 'org.sakaiproject.evaluation.logic.EvalSettings' while setting bean property 'settings'; nested exception is org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'org.sakaiproject.evaluation.logic.EvalSettings': Bean with name 'org.sakaiproject.evaluation.logic.EvalSettings' has been injected into other beans [org.sakaiproject.evaluation.logic.externals.EvalExternalLogic] 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.
Caused by:
org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'org.sakaiproject.evaluation.logic.EvalSettings': Bean with name 'org.sakaiproject.evaluation.logic.EvalSettings' has been injected into other beans [org.sakaiproject.evaluation.logic.externals.EvalExternalLogic] 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.createBean(AbstractAutowireCapableBeanFactory.java:429)
      at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:251)
      at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:156)
      at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:248)
      at org.sakaiproject.util.NoisierDefaultListableBeanFactory.getBean(NoisierDefaultListableBeanFactory.java:115)
      at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160)
      at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:261)
      at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:109)
      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1099)
      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:861)
      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:421)
      at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:251)
      at org.sp


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20100330/0aebba5b/attachment.html