I am using the org.springframework.batch.test.JobLauncherTestUtils class (Spring batch test framework). I have 2 spring batch jobs defined in my xml context file.

If I define the job launcher in xml ie

then it works as expected using the job bean defined eventsBatchJob. Without defining the job property I would get an error saying that 2 beans of that type exist as it tries to autowire by type.

However if I try to use @Configuration instead of xml to define the "eventsJobLauncherTestUtils" bean I run into trouble.

@Bean(name = "eventsJobLauncherTestUtils")
public JobLauncherTestUtils eventsJobLauncherTestUtils() {
JobLauncherTestUtils jobLauncherTestUtils = new JobLauncherTestUtils();
//eventsBatchJob is injected
jobLauncherTestUtils.setJob(eventsBatchJob);
return jobLauncherTestUtils;
}

Despite having set the job property in code above and there is no error in that method it glitches with the error that it cannot autowire as 2 beans jobs of that type exist. This should not be the case as I have set the job property explicitly. It is my understanding the above code should work in the same way as the xml snippet I posted above. (using spring version 3.0.5 and tried 3.0.6 and the 3.1.2Milestone but to no avail).

The JobLauncherTestUtils class has an autowire annotation set for the setJob accessor but the class itself is not defined as spring bean via annotations.

i find it works well without @Configuration

Help would be appriciated.

Because the SVN repository seems to have a problem now. Here is the error message I am getting…

>svn co https://src.sprin
gframework.org/svn/spring-samples/configuration-basic/trunk configuration-basic
svn: OPTIONS of 'https://src.springframework.org/svn/spring-samples/configuratio
n-basic/trunk': Could not resolve hostname `src.springframework.org': The reques
ted name is valid and was found in the database, but it does not have the correc
t associated data being resolved for.
(https://src.springframework.org)

or, mark one of the @Bean methods with @Primary, and then simply call
getBean(AccountRepository.class) – the 'primary' bean will be the one returned