Uploaded image for project: 'Spring Web Services'
  1. Spring Web Services
  2. SWS-594

SchemaCollection issue when XSD files are in the classpath, in different JAR artifacts

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.5.8
    • Fix Version/s: 1.5.9
    • Component/s: XML
    • Labels:
      None
    • Environment:
      Spring WS 1.5.8, WAR file deployed in either Tomcat or Jetty.

      Description

      Problem described in issue SWS-413 has partially been fixed.

      Given XSD-A importing XSD-B, both in the classpath, the fix works if XSD-A and XSD-B are in the same classpath location (both in WEB-INF/classes, or in the same JAR file), but it does not work if the XSD files are located in different JAR files, for example.

      The provided patch fixes this : if the imported XSD could not be resolved with the same base URI, we must keep searching in the classpath, (last statements should not be in an else block).

        Activity

        obillard Olivier Billard created issue -
        obillard Olivier Billard made changes -
        Field Original Value New Value
        Attachment CommonsXsdSchemaCollection.diff [ 16083 ]
        arjen.poutsma Arjen Poutsma made changes -
        Fix Version/s 1.5.9 [ 11296 ]
        arjen.poutsma Arjen Poutsma made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        arjen.poutsma Arjen Poutsma made changes -
        Remaining Estimate 0d [ 0 ]
        Time Spent 2m [ 120 ]
        arjen.poutsma Arjen Poutsma made changes -
        Status In Progress [ 3 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        arjen.poutsma Arjen Poutsma made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            arjen.poutsma Arjen Poutsma
            Reporter:
            obillard Olivier Billard
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0d
              0d
              Logged:
              Time Spent - 2m
              2m