SOAP and WSDL help.

Question

I'll try to make this as simple as possible in hope I get a
response. I have a particular web service I need to consume. Using
its WSDL file I have locally, how can I make a direct SOAP call to
it using the actual XML SOAP envelope? It balks when trying to use
cfinvoke with CFinvokearguments, giving me a "method doesn't exit"
error. I figure I can invoke the service somehow using CFHTTP and
using the entire soap envelope to call the web service. Am I
barking up the wrong tree here?
Looking at the actual soap body inside the envelope, Since
its XML there are a number of child tags inside i.e.
<soapenv:Body>
<the_request>
<security_header>
<some_element>whatever</some_element>
<another_element>whatever2</another_element>
</security_header>
<config_header>
<some_configelement>whatever</some_configelement>
<another_configelement>whatever2</another_configelement>
</config_header>
<data>
<some_dataelement>whatever</some_dataelement>
<another_dataelement>whatever2</another_dataelement>
</data>
</the_request>
</soapenv:body>
Thats it, no magic, no soap headers, nothing. Its all
contained within the body. Side note: How does CFinvoke arguments
keep track of what child elements they are under in the call? Any
help would be appreciated..
Thanks! Jeff

Answer 1

I wish I could give more details. Heck, I would post the
entire WSDL and soap call, but I am under NDA with the company that
I am implementing it from. I am also in between a rock and hard
place, because they DO NOT have any coldfusion implementation of
their product and know nothing about the language. So, I am SOL
when I am having problems with consuming their web service.
With that being said, I have used CFINVOKE and CFinvoke
arguement. Odd thing is that when I do and pass the correct
arguments, it tells me that the method doesn't exist. Now, I have
even heard that you must include all optional arguments with some
web services. I tried that too, still it tells me the method I
chose doesn't exist. Very frustrating.
Thats why I thought there might be a way to use the entire
soap envelope against the WSDL to produce a result other than
"method doesn't exist".
Jeff