Referencing WCF (Windows Communication Foundation) web services

Question

I am having some issues referencing a WCF based web service.
Apex can consume the WSDL just fine, but when I attempt to use any of the methods I start running into errors.
For example, there is a simple method that accepts a username and returns a facility ID. If I use the apex built-in web service test tool, I see the following request and response:
<?xml version='1.0' encoding='UTF-8'?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
mlns:xsd="http://www.w3.org/2001/XMLSchema">
     <SOAP-ENV:Body><ns1:FetchRequest xmlns:ns1="http://microsoft.com/wsdl/types/"><ns1:UserName>TAUS461</ns1:UserName>
/ns1:FetchRequest></SOAP-ENV:Body>
</SOAP-ENV:Envelope>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><s:Fault>
<faultcode xmlns:a="http://schemas.microsoft.com/net/2005/12/windowscommunicationfoundation/dispatcher">a:InternalServiceFault</faultcode><faultstring xml:lang="en-US">
Procedure or function 'Prc_Fetch' expects parameter '@userName', which was not supplied.</faultstring><detail>
<ExceptionDetail xmlns="http://schemas.datacontract.org/2004/07/System.ServiceModel"
xmlns:i="http://www.w3.org/2001/XMLSchema-instance"><HelpLink i:nil="true"/><InnerException i:nil="true"/>
<Message>Procedure or function 'Prc_Fetch' expects parameter '@userName', which was not supplied.</Message><StackTrace>   at WA.Ecy.ADS.FS.Service.BusinessLogic.FacilitySiteBAO.Fetch(String userName) in
C:\Projects\FS 2008\Development\Services\FS.Service\Source\Business Logic\FS.Service.BusinessLogic\FacilitySiteBAO.cs:line 418&#xD;
at FS.Service.ServiceImplementation.FacilitySiteService.Fetch(FetchRequest request) in
C:\Projects\FS 2008\Development\Services\FS.Service\Source\Service Interface\FS.Service.ServiceImplementation\GeneratedCodeFacilitySiteService.cs:line 1588&#xD;
   at SyncInvokeFetch(Object , Object[] , Object[] )&#xD;
   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]&amp; outputs)&#xD;
   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc&amp; rpc)&#xD;
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc&amp; rpc)&#xD;
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage4(MessageRpc&amp; rpc)&#xD;
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage3(MessageRpc&amp; rpc)&#xD;
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage2(MessageRpc&amp; rpc)&#xD;
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage1(MessageRpc&amp; rpc)&#xD;
   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)</StackTrace><Type>System.Data.SqlClient.SqlException</Type></ExceptionDetail></detail></s:Fault></s:Body></s:Envelope>I get a similar error regardless of which method I attempt to call.
So, I thought that I would try Jason Straub's [link FLEX_WS_API|http://jastraub.blogspot.com/2008/06/flexible-web-service-api.html] package. First I opened SOAPUI, pointed to the WSDL and generated a test request for the Fetch method. The request looked like this:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn: WA.Ecy.ADS.FacilitySite.Services">
   <soapenv:Header/>
   <soapenv:Body>
      <urn:FetchRequest>
         <!--Optional:-->
         <urn:UserName>TAUS461</urn:UserName>
      </urn:FetchRequest>
   </soapenv:Body>
</soapenv:Envelope>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
   <s:Header>
      <ActivityId CorrelationId="dcdd3433-7f61-48f4-b3e3-c2a6647409d3" xmlns="http://schemas.microsoft.com/2004/09/ServiceModel
Diagnostics">2aeead53-c9df-41df-9a77-3798be030775</ActivityId>
   </s:Header>
   <s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
      <FetchResponse xmlns="urn: WA.Ecy.ADS.FacilitySite.Services">
         <FacilitySiteId>99997167</FacilitySiteId>
      </FetchResponse>
   </s:Body>
</s:Envelope>So far so good, SOAPUI can call and retrieve from this method. Now I put this into place with FLEX_WS_API
declare
l_env clob;
l_url varchar2(1000) := 'http://ecydevws/FacilitySiteService/FacilitySiteService.svc'; -- dev web service URL
l_response xmltype;
p_username varchar2(30) := 'TAUS461';
begin
     -- start creating the soap envelope
     l_env := '<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn: WA.Ecy.ADS.FacilitySite.Services">
             <soapenv:Header/>
             <soapenv:Body>
                <urn:FetchRequest>
                <urn:UserName>'||p_username||'</urn:UserName>
                </urn:FetchRequest>
             </soapenv:Body>
          </soapenv:Envelope>';
     -- get the response
     l_response := flex_ws_api.make_request (
          p_url => l_url,
          p_action => 'http://WA.Ecy.ADS.FacilitySite.Services/Fetch',
          p_version => '1.1',
          p_envelope => l_env);
-- for testing, put the respone into a table
insert into ws_results values (l_response);
end;Doing this,my response becomes
<s:Envelope xmlns:s=
"http://schemas.xmlsoap.org/soap/envelope/"><s:Body><s:Fault><faultcode xmlns:a="http://schemas.microsoft.com
ws/2005/05/addressing/none">a:ActionNotSupported</faultcode>
<faultstring xml:lang="en-US">
The message with Action 'http://WA.Ecy.ADS.FacilitySite.Services/Fetch' cannot be processed at the receiver, due to a ContractFilter
mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver)
or a binding/security mismatch between the sender and the receiver.  Check that sender and receiver have the same contract and the same
binding (including security requirements, e.g. Message, Transport, None).</faultstring></s:Fault></s:Body></s:Envelope>So it appears to me that the WCF service is expecting something else in soap header, but I am confused on why the SOAPUI call works as is.
Does anyone with WCF knowledge have any ideas of how to get this to work or if the problem is even with WCF?
Thanks, Tony

Answer 1

as of now only file with wsdl extention is supported,