SOAP Request - Works in soapUI, but not in Coldfusion

Hi Folks,

As a newcoming to the world of webservices, I've been using soapUI to build requests, test them for output, then code the CFML from them.  So far, with the small number of web services I've worked with, it's been fine.

However, I've come across one that works fine in soapUI, but isn't working once I bring it into my Coldfusion page.

A <cfdump> shows the return is giving a '404 Not Found'.  There's obviously something wrong somewhere, but I'm not sure where!
<!--- soap request (xml) from soapUI --->
 
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:api="http://api.wsdomain.com/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
   <soapenv:Header>
      <api:getQuota></api:getQuota>
      <api:UserAuthentication>
         <api:iId>myuserID</api:iId>
         <api:sPassword>mypassword</api:sPassword>
         <api:sType>myusertype</api:sType>
      </api:UserAuthentication>
   </soapenv:Header>
   <soapenv:Body>
      <api:getTransactionList>
         <!--Optional:-->
         
         <api:dStartDate>2009-01-01T00:00:00</api:dStartDate>
         <api:dEndDate>2009-02-01T00:00:00</api:dEndDate>
         <api:sDateType>transaction</api:sDateType>
         <api:iLimit>100</api:iLimit>
      </api:getTransactionList>
   </soapenv:Body>
</soapenv:Envelope>
 
<!--- Coldfusion Page --->
 
<cfsavecontent variable="localscope.soapRequest">
<cfoutput>
        
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:api="http://api.wsdomain.com/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
   <soapenv:Header>
      <api:getQuota></api:getQuota>
      <api:UserAuthentication>
         <api:iId>myuserid</api:iId>
         <api:sPassword>mypassword</api:sPassword>
         <api:sType>myusertype</api:sType>
      </api:UserAuthentication>
   </soapenv:Header>
   <soapenv:Body>
      <api:getTransactionList>
         <!--Optional:-->
         
         <api:dStartDate>2009-01-01T00:00:00</api:dStartDate>
         <api:dEndDate>2009-02-01T00:00:00</api:dEndDate>
         <api:sDateType>transaction</api:sDateType>
         <api:iLimit>100</api:iLimit>
      </api:getTransactionList>
   </soapenv:Body>
</soapenv:Envelope>
 
</cfoutput>
</cfsavecontent>
<cfdump var="#xmlparse(localscope.soapRequest)#">
 
<cfhttp url="http://api.wsdomain.com/V3/AffiliateService" method="POST" resolveurl="NO">
<cfhttpparam type="header" name="content-type" value="text/xml">
<cfhttpparam type="header" name="charset" value="utf-8">
<cfhttpparam type="header" name="Content-Length" value="#len(trim(localscope.soapRequest))#">
<cfhttpparam type="xml" name="body" value="#trim(localscope.soapRequest)#">
</cfhttp>
 
<!--- Note that the cfhttp url is what soapUI is posting to (shown in the RAW display).  I have, however, tried both --->

Open in new window

ReveroomAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

srikanthmadishettiCommented:
You are hitting http://api.wsdomain.com/V3/AffiliateService url isn't it?

Is this the correct url .
Try hit the url with cfhttp method head and print cfhttp.responseheader.status_code if it  has 404 then it is broken link
0
ReveroomAuthor Commented:
Thanks for the reply.

The status code does indeed return a 404 error - both with that url and with the alternative referenced in the request (same, minus the /v3/etc etc).

That's what puzzles me more than anything - it returns fine in soapUI.
0
ReveroomAuthor Commented:
I've found the solution :-)

It turned out to be as simple as the capitalization within the URL.  In my CFhttp I was using /V3/ - changing it to /v3/ fixed it.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
srikanthmadishettiCommented:
Thats what even i was suggesting , IF you hit that url it was returning 404 so there was problem with url u gave  so check and pass the correct url.


0
srikanthmadishettiCommented:
Any way glad that you resolved your problem
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Web Servers

From novice to tech pro — start learning today.