problem in setting up circular reference

[hbagchi]

I am unable to figure out the problem in this application context setting,

<!-- Default batch job configuration set -->
	<bean id="defaultService" class="com.gn.rb.batch.framework.DefaultService"/>
	<bean id="defaultBatchJob" class="com.gn.rb.batch.framework.DefaultBatchJob">
		<property name="serviceName" value="Default" />
		<property name="batchJobShutdownHook" ref="defaultBatchJobShutdownHook"/>
		<property name="service" ref="defaultService" />
	</bean>
	<bean id="defaultBatchJobShutdownHook" class="com.gn.rb.batch.framework.DefaultBatchJobShutdownHook">
		<property name="batchJob" ref="defaultBatchJob"/>
	</bean>
<!--  -->

I am getting an error,
Error creating bean with name 'defaultBatchJob': Bean with name 'defaultBatchJob' has been injected into other beans [defaultBatchJobShutdownHook] 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.

Please advice.

[cwilkes]

Bean with name 'defaultBatchJob' has been injected into other beans [defaultBatchJobShutdownHook]

I'm not sure how much more spelled out the error message can get. What you have is A requiring B in its settings. However B also requires A. You can't do that.

The fix is to figure out if A needs B or if B needs A. In your case I'm not sure why the defaultBatchJobShutdownHook needs to know about the defaultBatchJob.

[litterat]

Circular dependencies

If you are using predominantly constructor injection it is possible to write and configure your classes and
beans such that an unresolvable circular dependency scenario is created.
Consider the scenario where you have class A, which requires an instance of class B to be provided via
constructor injection, and class B, which requires an instance of class A to be provided via constructor
injection. If you configure beans for classes A and B to be injected into each other, the Spring IoC
container will detect this circular reference at runtime, and throw a
BeanCurrentlyInCreationException.
One possible solution to this issue is to edit the source code of some of your classes to be configured via
setters instead of via constructors. Another solution is not to use constructor injection and stick to setter
injection only.

[hbagchi]

As always thanks for the lightning fast response. Taking the first advice I have changed the removed the circular relationship. Now I have a different problem.
I want to make the batch job classes serializable since I want to persists them as objects to a database.
Strangely, the moment I add "implements Serializable" to the batch job class
the application fails with this message,

Failed to convert property value of type [$Proxy1] to required type [com.generali.ruby.batch.framework.AbstractBatchJob] for property 'remittanceShareBatchJob'; nested exception is java.lang.IllegalArgumentException: Cannot convert value of type [$Proxy1] to required type [com.generali.ruby.batch.framework.AbstractBatchJob] for property 'remittanceShareBatchJob': no matching editors or conversion strategy found

It seems making a spring instantiated class serializable has some side effects and needs to handled differently.

Please advice.

[karldmoore]

I guess you are using proxies somewhere (e.g. TransactionProxyFactoryBean) and you aren't programming to interfaces. You'll either need to add proxyTargetClass="true" or program to interfaces.
http://www.springframework.org/docs/...l#aop-proxying