webMethods

webMethods

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Back to discussions
Expand all | Collapse all

Importing WSDL fails to resolve location whereas SOAPUI does...

  • 1.  Importing WSDL fails to resolve location whereas SOAPUI does...

    Posted Mon April 27, 2015 09:21 AM

    Hi, I am trying to import a WSDL into CentraSite with all WSDL and XSDs present. Unfortunately CentraSite does not resolve the import location and consequently prompts for every single WSDL and XSD. When I import into SOAP UI, there is no problem.

    To try another route, I then attempted to import the WSDL via the designer (9.6) and it too does not like the WSDL.

    anyone aware of what the cause might be or any pointers?

    Partial sample - Intention is MyParentWS.WSDL imports MyChildWS.WSL

    <?xml version="1.0" encoding="UTF-8"?>

    <wsdl:definitions name=“MyParentWS-v1”
    targetNamespace=“http://www.mycompany.co.uk/wsdl/services/MyChildWS/MyParentWS/V1”
    xmlns:tns=“http://www.mycompany.co.uk/wsdl/services/MyChildWS/MyParentWS/V1”
    xmlns:MyChildWS=“http://www.mycompany.co.uk/wsdl/services/MyChildWS/MyChildWS/V1”
    xmlns:wsdl=“http://schemas.xmlsoap.org/wsdl/”
    xmlns:soapbind=“http://schemas.xmlsoap.org/wsdl/soap/”>
    wsdl:documentationVersion 1.0</wsdl:documentation>

    <wsdl:import namespace=“http://www.mycompany.co.uk/wsdl/services/MyChildWS/MyChildWS/V1” location=“MyChildWS.wsdl”/>

    <wsdl:binding name=“AccountBinding-MyParentWS-v1” type=“MyChildWS:MyChildWSPortType”>

    :
    :
    :

    Even with the location set, CentraSite proceeds to prompt for MyChildWS.wsdl


    #webMethods
    #CentraSite
    #API-Management


Related Content