Uploaded image for project: 'MidPoint'
  1. MidPoint
  2. MID-3090

Dynamically linked WSDL contains unproxied xsd reference

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Trivial
    • Resolution: Unresolved
    • Affects Version/s: 3.3.1
    • Fix Version/s: 5.0
    • Component/s: Model
    • Labels:
      None
    • Environment:

      midpoint 3.3.1 built from 3.3.1 tag

      Description

      When using SOAP WS interface, there is one glitch, that prevents rigid software to use WSDL.
      Such client searches for URI in path /midpoint/ws/xml.xsd

      Here is the reason (lets say localhost:8080 is midPoint installation):

      1. WS client is pointed to "http://localhost:8080/midpoint/ws/model-3?wsdl"
      2. this WSDL contains refference to common-3 on proxy-path "http://localhost:8080/midpoint/ws/model-3?xsd=http://midpoint.evolveum.com/xml/ns/public/common/common-3"
      3. common-3.xsd contains refference to XMLSchema on proxy path "http://idm-test.srv.int.avast.com:8080/midpoint/ws/model-3?xsd=http://www.w3.org/2001/XMLSchema" (the same applies for fault-3)
      4. XMLSchema contains unproxied reference to xml.xsd on path "xml.xsd"
        which leads to request for http://localhost:8080/midpoint/ws/xml.xsd

      This info can be nicely seen in SOAP-UI, right click on modelBindig -> WSDL Content -> xml.xsd ("<html> <body>No service was found.</body></html>")

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              semancik Radovan Semancik
              Reporter:
              petr.gasparik Petr Gašparík
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated: