+972 52-548-6969
SSIS & WCF - Not on best terms
I wanted to get SSIS to call a service in my application if it has successfully completed an operation. I quickly built the following service using WCF:
[ServiceContract]
public interface ISsisNotifications
{
[OperationContract]
void UpdatedDatabase();
}
public class SsisNotifications : ISsisNotifications
{
public void UpdatedDatabase()
{
}
}
I didn't ask for something complex like (gasp!) passing parameters, or doing something with the result. All I wanted was the simplest possible scenario. It refused to do that. I found this post about similar problems, but even after hand editing the dtsx file (a daunting task), it still failed to work.
An ASMX service works just fine, but of course that this means that I have to separate technologies just for something as simple as that. Yuck!
Comments
So it would appear the problem would be the imported schemas in the WSDL, right? If so, then SSIS would not be the first tool to get confused by them, unfortunately.
I wonder if then using the "Inline XSD" extension I created for WCF a while ago on the WCF service would help at all here.... See
http://www.winterdom.com/weblog/2006/10/03/InlineXSDInWSDLWithWCF.aspx)
Nope, tried that, and it didn't work.
Did you also try the tip about removing the
<xsd:import schemaLocation="http://localhost:50344/MyWebService/Service.svc?<xsd=xsd2" namespace="http://schemas.datacontract.org/2004/07/"/>
Part of the WSDL?
http://sjbdeveloper.blogspot.com/2007/03/fixing-wcf-ssis-web-service-task.html
Comment preview