This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

In this case the spring container was able in reading all xml files whose names started with spring and finished with context. Now if i write as I showed the ContextListener seems to search for the only one file the one called "spring-*-context.xml"
Content of spring-gwtDispatch-context.xml

Note that both spring-application-context.xml and spring-gwtDispatch-context.xml are inside in two different eclipse maven project (at the end 2 different jars)

When I launch the GWT project by using the GWT Eclipse plugin it seems to me that the container is not able in scanning the beans listed in file "spring-gwtDispatch-context.xml" while it's able in scanning beans listed in the other file.
On other side I built a simple unit test. This is its code:

As you can see the loaded bean number is different. Can anybody suggest to me why this is happening? I'm fighting with this issue from 3 days
I'm not able in understanding if it's a spring container issue, GWT issue (note that GWT plugin starts by using jetty servlet container) or, more probably, a my issue.

Comment

Hi all
I solved the issue...at least it seems
The problem seems to be related to the Maven eclipse plug-in; in fact by disabling the workspace resolution property in the Web application project all worked good

Angelo

Comment

I know i solved as i said yesterday...but by removing the workspace resolution option means that every time i change something on other maven projects i need to run the "mvn clean install" command and this makes me be little bit slow....
Do you have any idea on how i can solve this issue?