Publish spring-jpa-1.0.xsd [DATAJPA-21] about spring-data-jpa HOT 11 CLOSED

Oliver Drotbohm commented

Thomas, could you please look at this? Let me know if I can help out there

from spring-data-jpa.

Dave Carey commented

Just to confirm the issue and to mention that I tried to workaround the issue by following http://www.jroller.com/habuma/entry/fixing_spring_modules_xsd_errors - but failed - for some reason eclipse is failing to recognize the xsd in the M1 distribution jar

from spring-data-jpa.

Thomas Risberg commented

copied the Spring Data schema files to www.springframework.org/schema/data

from spring-data-jpa.

Stevo Slavić commented

Thanks, but now there is a different related issue: spring-jpa-1.0.xsd references http://www.springframework.org/schema/data/repository/spring-repository.xsd which is not available at that URI. Should we file that as separate issue?

from spring-data-jpa.

Thomas Risberg commented

OK, I have coped that one as well. You should be able to see it in a few minutes once the data is synched

from spring-data-jpa.

Stevo Slavić commented

spring-repository-1.0.xsd is there now but not spring-repository.xsd which spring-jpa-1.0.xsd references

from spring-data-jpa.

Stevo Slavić commented

I guess both versionless copy of all the schemas should be published as well since they are the latest ones

from spring-data-jpa.

Thomas Risberg commented

I've created the symbolic links for the version less references. I would think that spring-jpa-1.0.xsd should reference spring-repository-1.0.xsd instead of spring-repository.xsd. I'll create a separate issue for that.

from spring-data-jpa.

Thomas Risberg commented

I've created the symbolic links for the version less references. I would think that spring-jpa-1.0.xsd should reference spring-repository-1.0.xsd instead of spring-repository.xsd. I'll create a separate issue for that.

from spring-data-jpa.

Stevo Slavić commented

Thanks for quick and transparent support!

Related issue now I have still with validation of spring context files is that spring-jpa-1.0.xsd can not be used with spring 3.1 M1 and it's XSDs like in following sprign context config:

<beans xmlns="http://www.springframework.org/schema/beans"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xmlns:p="http://www.springframework.org/schema/p"
	xmlns:util="http://www.springframework.org/schema/util"
	xmlns:aop="http://www.springframework.org/schema/aop"
	xmlns:tx="http://www.springframework.org/schema/tx"
	xmlns:context="http://www.springframework.org/schema/context"
	xmlns:jpa="http://www.springframework.org/schema/data/jpa"
	xsi:schemaLocation="http://www.springframework.org/schema/beans
		http://www.springframework.org/schema/beans/spring-beans-3.1.xsd
		http://www.springframework.org/schema/util
		http://www.springframework.org/schema/util/spring-util-3.1.xsd
		http://www.springframework.org/schema/tx
		http://www.springframework.org/schema/tx/spring-tx-3.1.xsd
		http://www.springframework.org/schema/aop
		http://www.springframework.org/schema/aop/spring-aop-3.1.xsd
		http://www.springframework.org/schema/context
		http://www.springframework.org/schema/context/spring-context-3.1.xsd
		http://www.springframework.org/schema/data/jpa
		http://www.springframework.org/schema/data/jpa/spring-jpa-1.0.xsd">

	<jpa:repositories base-package="foo.bar.dao"
		entity-manager-factory-ref="entityManagerFactory"
		transaction-manager-ref="transactionManager"/>
</beans>

Cause is that spring-jpa-1.0.xsd references/imports versionless spring-context.xsd which imports versionless spring-beans.xsd, so eclipse XML validation complains that there are multiple XSD elements with same name - ones from 3.0 versionless spring core XSDs, and ones from 3.1 in my context config.

Not sure if it will be acceptable and what the policy is for spring core XSDs from 3.1 M1 to be published as versionless XSDs too, before spring 3.1 final is released. Maybe separate issue for this on spring core JIRA project

from spring-data-jpa.

Thomas Risberg commented

I have created a separate JIRA issue DATAJPA-24 to track the versioning issues for these schemas

from spring-data-jpa.