Spring 3.0: Unable to locate Spring NamespaceHandler for XML schema namespace?

No WEB-INF/lib/spring/org.springframework. Aop-3.0.0.RELEASE. Jar, just WEB-INF/lib/org.springframework.

Aop-3.0.0.RELEASE. Jar Same with the rest of the jars.

Yep -- according to this, subdirectories under WEB-INF/lib aren't valid. Never knew one way or another how that'd work... nice to know now. Code.google.Com/appengine/docs/java/tools/ant.

Html#Copying_JARs – delfuego Dec 21 '09 at 3:39 By the way, I suspect that the reason it works fine in IntelliJ is that IntelliJ is using a custom classloader... – delfuego Dec 21 '09 at 3:39 Yes, that fixed it. IntelliJ does not complain , because it has the jars added in directly under the libraries section. – Nick Hristov Dec 21 '09 at 11:26 One more thing to note, ant's copy task has a "flatten" argument, which is perfect for this task.

– Nick Hristov Dec 21 '09 at 18:05.

maven.apache.org/plugins/maven-shade-plu... I ran into a similar problem using the maven-shade-plugin. I found the solution to my problems in their example page above.

If it's deployment, it might be because whatever mechanism of deployment you use -- maven-assembly making a single JAR with dependencies is a known culprit -- is collapsing all your JARs into a single directory and the Spring schema and handler files are overwriting each other.

Using IntelliJ for an IDE. No problems in the IDE, everything checks out. I am using ant to assemble the web app, and the listing above is from the war directory.

– Nick Hristov Dec 21 '09 at 2:06 +1 to delfuego for linking to MASSEMBLY-360; that's exactly the problem I'm having. – Andrew Swan Mar 11 '10 at 3:38 If using Spring 2.5.6, you can work around this by using the all-in-one "spring" JAR file that comes with that version (as opposed to separately using spring-core, spring-beans, spring-jdbc, etc. ) – Andrew Swan Mar 11 '10 at 4:02 +1 to delfuego. – Chandranshu May 26 at 8:34.

I have the same problem with spring 3.0.2 and spring-beans-3.0.xsd. My solution: Create a file META-INF/spring. Schemas in the source folder and copy all necesary definitions.

Create spring. Handlers too. I think that the class PluggableSchemaResolver is not working correctly.

static.springsource.org/spring/docs/3.0.... from the javadoc: "By default, this class will look for mapping files in the classpath using the pattern: META-INF/spring. Schemas allowing for multiple files to exist on the classpath at any one time. " but in my case, this class only read the first spring.

Schemas finded. Grettings. Pacovr.

1 for mentioning PluggableSchemaResolver. Here's a good article on the subject: denis-zhdanov.blogspot. Com/2010/01/… – opyate Nov 7 at 17:20.

Not related to your problem but you might be better off using the versioned names of the xsd files.

In case someone else runs into this problem, I just did using Eclipse; running the project via the right click action. This error occurred in the J2EE view, but did NOT occur in the Java view. Not sure - assuming something with adding libraries to the correct 'lib' directory.

I am also using a Maven project, allowing m2eclipse to manage dependancies.

You can also try using the one-jar maven plugin which fixed the problem for us. Simply follow the instructions from here.

I ran into a similar error, but refering to Spring Webflow in a newly created Roo project. The solution for me turned out to be (Project) / right-click / Maven / Enable Maven Dependencies (followed by some restarts and republishes to Tomcat). It appeared that STS or m2Eclipse was failing to push all the spring webflow jars into the web app lib directory.

I'm not sure why. But enabling maven dependency handling and then rebuilding seemed to fix the problem; the webflow jars finally get published and thus it can find the schema namespace references. I investigated this by exploring the tomcat directory that the web app was published to, clicking into WEB-INF/lib/ while it was running and noticing that it was missing webflow jar files.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.