WSDL 2.0 test case problems - unknown host & schema visibility

• From: John Kaputin <KAPUTIN@uk.ibm.com>
• Date: Fri, 23 Sep 2005 10:17:29 +0100
• To: www-ws-desc@w3.org
• Message-ID: <OFF580E1E7.44213955-ON80257085.0030249E-80257085.00330A47@uk.ibm.com>

This WSDL test case has element references that are prefixed with a
namespace that is schema imported within <types>, however the
schemaLocation URL  cannot be resolved (java.net.UnknownHostException:
greath.example.com).  A wsdl processor might use a catalog to resolve such
a host name, but I guess that's not the objective of this test case.
See:
https://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/test-suite/documents/good/CreditCardFaults-1G/use-credit-card-faults.wsdl
<types>
  <xs:import
    namespace="https://greath.example.com/2004/schemas/resSvc"
    schemaLocation="https://greath.example.com/2004/schemas/resSvc.xsd" />
</types>
I think there is another problem too. This wsdl imports another wsdl
document containing a schema import of "credit-card-faults.xsd".  That
schema should not be visible to the top level wsdl, unless it imports the
schema directly in its <types> element (i.e. if WSDL B xs:imports Schema X
and WSDL A wsdl:imports WSDL B,  Schema X is not visible to WSDL A.  WSDL A
must xs:import Schema X directly). However in this test case, the top level
wsdl does have element references to that schema's namespace. For this test
case to work, I think the top level schema needs to xs:import
"credit-card-faults.xsd" in its <types> element.
John Kaputin

Received on Friday, 23 September 2005 09:17:43 UTC