Autowire-Problem

[markuse1501]

Hey!

Following situation:

There's a service interface UserService

public interface UserService
{
...
	List<User> findAllUsers();
...
}

..and the appropriate implementation UserServiceImpl

@Service
public class UserServiceImpl implements UserService
{
	@Autowired
	UserRepository userRepository;

	public List<User> findAllUsers() {
		return userRepository.findAll();
	}
...
}

Now I try to write a JUnit test for my service implementation, it looks like this so far...

public class UserServiceImplTest
{
	@Autowired
	public UserService userService;
	
...
}

But when I run the test, I get the following error:

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'net.twentyfourseven.blog.service.UserServiceImplTest': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: public net.twentyfourseven.blog.service.UserService net.twentyfourseven.blog.service.UserServiceImplTest.userService; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No matching bean of type [net.twentyfourseven.blog.service.UserService] found for dependency: expected at least 1 bean which qualifies as autowire candidate for this dependency. Dependency annotations: {@org.springframework.beans.factory.annotation.Autowired(required=true)}

The implentation und interface are within the same package, and I scan my path via

<context:component-scan base-package="net.twentyfourseven.blog" />
<context:annotation-config />

Does anyones knows whats the problem here????

Thank you!

Markus

[Marten Deinum]

Judging from your code your testcase isn't loading anything... Also why would the context be creating your testcase?!

[sushantnayak]

Try to use the following to autowire,

	
<bean class="org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor" />

instead of

<context:annotation-config />

[Marten Deinum]

That is what annotation-config already does and which isn't needed because it is implied by the component-scan...