Custom Dataconnector's Schema

[Cantor, Scott]

It means you didn't have it correct originally and it's been loading it "remotely", though in your case it wasn't remote in a network sense. If you had stuck a remote URL in schemaLocation it would have happily resolved that, which is why we fixed it to stop doing that.

You have to fix your spring schema namespace mapping file to properly direct the value in the schemaLocation mapping into the classpath resource path you want it to use.

Spring is badly broken in this area but in a nutshell it insists on using the schemaLocation to locate the schema based on the namespace and then (optionally) maps from that location to a resource to load if you want it to pull from a jar via the META-INF spring.schemas file.

We just fixed it so that it it doesn't work if you bypass spring.schemas by accident or on purpose.

-- Scott