0 Replies Latest reply on Sep 29, 2009 3:14 AM by Phil.Arnold

    CFMX8 Problem calling ASP.NET web service, or a way to upgrade AXIS?

    Phil.Arnold Level 1

      I'm trying to talk to an ASP.NET web service using CFMX8, but it doesn't work - it works with PHP and ASP.NET calling it, but not CF...


      I'm just trying to do a CreateObject("webservice", URL) and it returns this error:

      Name: http://URL/template.svc?wsdl. WSDL: http://URL/template.svc?wsdl. java.io.IOException: Emitter failure. There is an undefined portType (portType name) in the WSDL document http://URL/template.svc?wsdl=wsdl0. Hint: make sure  is fully qualified. It is recommended that you use a web browser to retrieve and examine the requested WSDL document to ensure it is correct. If the requested WSDL document cannot be retrieved or is dynamically generated, it is likely that the target web service has programming errors.


      I've validated the WSDL with both XMLSpy 2009 and SOAPUI 3 and they both say it's fine, so the only thing I can think of is that the AXIS version that CF uses (which happens to be 3 years old now) is having problems calling the WSDL.


      Note that ASP.NET puts in cyclic imports of WSDLs, so the main WSDL imports a second WSDL, which in turn imports the original WSDL, etc.


      I have validated with AXIS 1.4 and it has the same problem, so it appears to be a problem with AXIS1, but I've not managed to validate with AXIS2 yet to find out if that has the same issue.



      Has anyone got a solution to this as I'm pulling my hair out, and it's only CF that has the problem with the web service, so it makes us look like we're using the inferior product...


      Any suggestions on what to say to the ASP.NET people to fix this problem at their end, because I don't know WSDLs well enough to be able to read them this deeply and supply the required code to fix this - the portType is actually defined, but AXIS seems to dislike the way the WSDL is put together and rejects it...


      Thanks in advance.