Topic
  • 4 replies
  • Latest Post - ‏2013-03-30T10:09:01Z by SystemAdmin
SystemAdmin
SystemAdmin
56 Posts

Pinned topic Problem in Consuming WCF Data Service in Cast Iron

‏2013-03-18T09:34:48Z |
Hi,

I am trying to consume a WCF Data service in Cast Iron and getting some issues in it.

Following are steps followed by me:
1. Created a WCF Data Service(C#).
2. Hosted this service at one of my development server.
3. Created an orchestration in Cast Iron Studio.
4. Created an WebService end point.

I am getting the folowing error while creating the endpoint:
Could not load the document http://serverName/VDName/Service.svc/?wsdl into the repository.
Error: The document is not a schema@http://www.w3.org/2001/XMLSchema: document element mismatch got document

I have taken Webservice End Point type as Invoke, Location as Remote, and putting my service URL in WSDL-> Add URL and getting the error at this point only.

Please let me know if anyone in the community had ever tried or consumed WCF Data Service in Cast Iron Studio; and if ever had faced such issues and how resolved them.

Thanks in advance.
Updated on 2013-03-30T10:09:01Z at 2013-03-30T10:09:01Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    56 Posts

    Re: Problem in Consuming WCF Data Service in Cast Iron

    ‏2013-03-27T12:48:37Z  
    The WSDL is probably not WS-I compliant. If it is WS-I compliant and Studio cannot consume it, your should probably open a support case.

    When I have had to consume Microsoft WSDLs, the "wrapped" form causes fewer problems.
  • SystemAdmin
    SystemAdmin
    56 Posts

    Re: Problem in Consuming WCF Data Service in Cast Iron

    ‏2013-03-29T05:58:13Z  
    You can validate whether the WSDL is actually WS-I compliant. When you encountered error while importing the WSDL into orchestration in Studio, the error will be logged under Cast Iron Installation folder/error.log and the stacktrace for the error can be found there.

    You might want to look at these articles, I have past experience and got stuck while importing MS Exchange 2007 WSDL file as well. Still haven't find how to resolve it and perhaps anyone could share how to overcome this as well. Another question I want to raise is whether this implies that Cast Iron only support WS-I compliant web service?

    http://www-01.ibm.com/support/docview.wss?uid=swg21452782
    http://www-01.ibm.com/support/docview.wss?uid=swg21580263
  • SystemAdmin
    SystemAdmin
    56 Posts

    Re: Problem in Consuming WCF Data Service in Cast Iron

    ‏2013-03-29T14:50:07Z  
    You can validate whether the WSDL is actually WS-I compliant. When you encountered error while importing the WSDL into orchestration in Studio, the error will be logged under Cast Iron Installation folder/error.log and the stacktrace for the error can be found there.

    You might want to look at these articles, I have past experience and got stuck while importing MS Exchange 2007 WSDL file as well. Still haven't find how to resolve it and perhaps anyone could share how to overcome this as well. Another question I want to raise is whether this implies that Cast Iron only support WS-I compliant web service?

    http://www-01.ibm.com/support/docview.wss?uid=swg21452782
    http://www-01.ibm.com/support/docview.wss?uid=swg21580263
    Regarding the Exchange WSDL, adding this snippet to the Exchange WSDL just below the closing </wsdl:binding> element should enable you to import the WSDL into Studio (change location to match your Exchange server):

    <wsdl:service name="ExchangeService">
    <wsdl:port name="ExchangeServicePort" binding="tns:ExchangeServiceBinding">
    <soap:address location="https://yourExchangeHost.yourDomain.com/EWS/Exchange.asmx" />
    </wsdl:port>
    </wsdl:service>

    It may help to download the messages.xsd and types.xsd schemas as well to the same folder that you downloaded the WSDL to before attempting to import the WSDL into Studio.
  • SystemAdmin
    SystemAdmin
    56 Posts

    Re: Problem in Consuming WCF Data Service in Cast Iron

    ‏2013-03-30T10:09:01Z  
    Regarding the Exchange WSDL, adding this snippet to the Exchange WSDL just below the closing </wsdl:binding> element should enable you to import the WSDL into Studio (change location to match your Exchange server):

    <wsdl:service name="ExchangeService">
    <wsdl:port name="ExchangeServicePort" binding="tns:ExchangeServiceBinding">
    <soap:address location="https://yourExchangeHost.yourDomain.com/EWS/Exchange.asmx" />
    </wsdl:port>
    </wsdl:service>

    It may help to download the messages.xsd and types.xsd schemas as well to the same folder that you downloaded the WSDL to before attempting to import the WSDL into Studio.
    Paul, you've made my day!!!