Problem with Spring WS application configuration?

Question

Java

upd : Added screenshots of settings
Hello!
I'm getting started with spring-ws. For the test, I decided to make a small program - a web service for working with mongoDb.
I started with a simple one - just a WebService following the example of www.mkyong.com/webservices/jax-ws/jax-ws-spring-in...
everything worked, good. I tried separately mongo www.mkyong.com/mongodb/spring-data-mongodb-hello-w... , everything is ok too.
Tried to combine everything together, got the problem:

??? 12, 2013 11:55:46 PM org.apache.catalina.core.ApplicationContext log
INFO: Loading Spring root WebApplicationContext
??? 12, 2013 11:55:46 PM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener
org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Unable to locate NamespaceHandler for namespace [http://www.springframework.org/schema/data/mongo]
Offending resource: ServletContext resource [/WEB-INF/applicationContext.xml]

I spent three days studying the problem, but I still did not understand anything. Please, prompt in what party to dig.
I launch through Intellij, if that.
Sources: github.com/arturgspb/mongo-ws-test
Screenshots

Answer 1

And check if all the libs are in "WEB-INF/lib" and if they are added to the artifact

Answer 2

The problem seems to be the lack of a schema in the application context headers, in particular for www.springframework.org/schema/data/mongo.
listing app would help to figure it out. context.
maybe I didn’t quite understand the essence of your problem, but if I were you, I wouldn’t suffer with various things with spring and used the wonderful hibernate library as an intermediary between you and the database, which offers us the necessary functionality for communicating with any data source. combined with JPA annotations, you will get a wonderful tool for communicating with the database in a few minutes.
I can say for sure that the problem with the import is in the header application context. dig for information on this topic.