Complex data types can be real trouble for CF web service developers. Though usually the error it generates is something along the lines of:
Web service method with parameters(...) cannot be found
The fact that your error message mentioned the WSDL file made me think that it was a communication issue between the CF server and the SAP server. So far the best method I've found for modeling complex objects for web service invocations is to create an object via an XML-text-parsing operation in then passing the resulting complex object to the web service:
Say you have a WS who takes a custom complex object called "person", which has attributes "fname" and "lname":
1) Store xml text that models the object structure in a cf variable*
<cfsavecontent variable="sXML">
<person>
<fname>Joe</fnam>
<lname>Smith</lname>
</person>
</cfsavecontent>
* not sure if you want to use XML children or attributes here. might need to play around with this one
2) Parse the XML into another CF variable
<cfset xmlObj = XMLParse(sXML)>
3) Pass the xmlObj variable as the input value for your web service invocation variable.
4) Celebrate
I've had to play around with a number of different techniques in getting complex objects working in web services over the years, so there are a bunch of options out there - from simply passing a CF structure to using java to create a custom input class to creating custom web service stubs. In every case, though, the error message for getting it wrong always seems to be about not being able to find/match up the web service method with the method definitions in the WSDL and nothing to do with being able to access the WSDL file itself.
12
Replies
AdChoices