ANY advice would be apprecated. I\'m stumped...
Problem
On my laptop, anytime our application tries to load the application-config.xml, I ge
I would assume you have wrong spring jars - perhaps one for spring 2.5 and one for 3.0. The classloader loads, say, spring-core for version 3.0, and the rest for 2.5. This would result in such errors.
I'd suggest going through your maven dependency graph and remove all redundant ones. If necessary, use <exclusions>
in your pom.
Before that clean your project on all machines.
I had similiar error when trying to run Mule service on Mule ESB embedded in Tomcat. The solution was to change JDK from default:
java version "1.6.0_18"
OpenJDK Runtime Environment (IcedTea6 1.8.1) (6b18-1.8.1-0ubuntu1)
OpenJDK 64-Bit Server VM (build 16.0-b13, mixed mode)
to good old Sun JDK:
java version "1.6.0_20"
Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode)
of course, it might have been version/patch issue. If only I had the time to investigate...
I had the same problems and another measure helped: delete the whole .metadata folder. Later import projects from their place or checkout them from the svn(if you use some). The problem is that we don't really know, what metadata are broken, so the natural next step is to delete all of them. I think, it is the deepest possible cleaning apart from reinstallation of Eclipse + plugins.