Details

    • Type: Task Task
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Complete
    • Affects Version/s: 1.0 M1
    • Fix Version/s: 1.0 M2
    • Component/s: Namespace
    • Labels:
      None

      Description

      Eclipse can't validate spring context files which reference http://www.springframework.org/schema/data/jpa/spring-jpa-1.0.xsd since it's not available. Would have to manually create XML catalog entry. spring-security-3.1.xsd is already available even though Spring Security 3.1 is in RC status, so it seems to be a common practice to have XSD published even if it might change til final release.

        Issue Links

          Activity

          Hide
          Stevo Slavić added a comment -

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

          Show
          Stevo Slavić added a comment - I guess both versionless copy of all the schemas should be published as well since they are the latest ones.
          Hide
          Thomas Risberg added a comment -

          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.

          Show
          Thomas Risberg added a comment - 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.
          Hide
          Thomas Risberg added a comment -

          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.

          Show
          Thomas Risberg added a comment - 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.
          Hide
          Stevo Slavić added a comment -

          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.

          Show
          Stevo Slavić added a comment - 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.
          Hide
          Thomas Risberg added a comment -

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

          Show
          Thomas Risberg added a comment - I have created a separate JIRA issue DATAJPA-24 to track the versioning issues for these schemas.

            People

            • Assignee:
              Thomas Risberg
              Reporter:
              Stevo Slavić
            • Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: