+1  A: 

Your Spring context has a bean definition using LocalContainerEntityManagerFactoryBean. This creates an EntityManagerFactory, not an EntityManager.

AssignmentDao needs to get itself wired with an EntityManagerFactory.

Alternatively, you can replace the LocalContainerEntityManagerFactoryBean with a LocalEntityManagerFactoryBean, which will create an EntityManager directly. However, you need to be careful with that one, it has some downsides. See that part of the Spring docs for a full explanation of the options.

It's confusing, because the naming conventions of JPA and Spring overlap each other, so naming these classes is a real bugger.

skaffman
assignmentDao is wired by annotation, that one was inserted at the last minute for debugging, disregard. So far all examples that I have found use the EntityManagerFactory in the configuration and the EntityManager for injection. I have used it this way with Mysql w/o JUnit-Spring Integration and it worked.
@sebajb: Read the link I posted. Section 13.5.2 talks about to combine things in the way you need.
skaffman
Thanks. I need to read the doc and see what suits my need. LocalEntityManagerFactoryBean seems however too limited for my requirements. I will just inject an EntityManagerFactory instead.