To fix these XML validation issues, you can completely remove version notations, as shown below, and let Spring load general schema locations.
<?xml version="1.0" encoding="UTF-8"?> <beans xmlns="http://www.springframework.org/schema/beans" xmlns:context="http://www.springframework.org/schema/context" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:jdbc="http://www.springframework.org/schema/jdbc" xmlns:jpa="http://www.springframework.org/schema/data/jpa" xmlns:tx="http://www.springframework.org/schema/tx" xsi:schemaLocation=" http://www.springframework.org/schema/beans http://www.springframework.org/schem...ring-beans.xsd http://www.springframework.org/schema/context http://www.springframework.org/schem...ng-context.xsd http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx.xsd http://www.springframework.org/schema/data/jpa http://www.springframework.org/schem...spring-jpa.xsd http://www.springframework.org/schema/jdbc http://www.springframework.org/schema/jdbc/spring-jdbc.xsd">
Enabling shared schema locations or an XSD version does not produce different results for application behavior. Also, try reorganizing pom.xml and make sure that the time dependencies have been resolved with the correct version.
The strange part of this permission is that it worked for me in several applications, but did not work in others, where I received the same error. For me, sometimes changing the ed-version of XSDs to a generic one, and then changing them back to version again, worked out. Eclipse Luna-tic behavior!
PS: No offense intended for fans of Eclipse.
source share