tracker issue : CF-3832635

select a category, or use search below
(searches all categories and all time range)

WSDL auto-generation seems in-correct

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Eric Harris / Eric Harris (Eric Harris)

Created: 09/26/2014

Components: Web Services

Versions: 11.0

Failure Type: Non Functioning

Found In Build/Fixed In Build: CF11_Final / CF11 Update5

Priority/Frequency: Critical / All users will encounter

Locale/System: English / Win 2008 Server R2 64 bit

Vote Count: 1

Listed in the version Issues Fixed doc
Problem Description:  New install of Coldfusion 11.  

Modified axis2.xml file to allow for SSL Web Service calls.  

    <transportReceiver name="http" class="coldfusion.xml.rpc.CFAxisServletListener">
      <parameter name="port">80</parameter>
    <transportReceiver name="https" class="coldfusion.xml.rpc.CFAxisServletListener">
      <parameter name="port">443</parameter>

Added Internal Root certificate to cacerts file.  When example .cfc file that has remote calls for auto-generation of WSDL, the generated wsdl does not look correct.  In the port definition at the bottom, it does not seem to be using https for the 443 soap endpoint:

<wsdl:port name="ujaWSHttpSoap11Endpoint" binding="ns:ujaWSSoap11Binding">
<soap:address location=""/>
<wsdl:port name="ujaWSHttpsSoap11Endpoint" binding="ns:ujaWSSoap11Binding">
<soap:address location=""/>

In coldfusion 10, this binding looks like:

<wsdl:port name="ujaWSHttpSoap11Endpoint" binding="ns:ujaWSSoap11Binding">
<soap:address location=""/>
<wsdl:port name="ujaWSHttpsSoap11Endpoint" binding="ns:ujaWSSoap11Binding">
<soap:address location=""/>

Calls from external WS engines ( SOAP UI 5.0.0 and Chrome Extension ( Advanced Rest client 3.1.7 ) seem to still work.  However, when I make a call from CF using cfinvoke I get "Cannot perform web service invocation" : Connection reset at org.apache.axis2.AxisFault.makeFault(

Steps to Reproduce:

Create cfc for remote invocation, generated wsdl will look like above

Actual Result:

soap binding does not have https to match :443 call

Expected Result:

soap binding should have https

Any Workarounds:


----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3832635

External Customer Info:
External Company:  
External Customer Name: eric.harris_wv
External Customer Email:  
External Test Config: My Hardware and Environment details:

Windows 2008 R2

IIS 7.5

Coldfusion 11



We are experiencing the same issue. I believe it didn't start until after we ran the first update for CF11. This was a production server and we now have to contact all consumers of the webservice and let them know the webservice is not available until further notice.
Vote by External U.
10817 | October 08, 2014 03:53:55 PM GMT
The endpoint URL is not correct when HTTPS is configured in the axis2.xml. The port was coming correct. But the protocol was wrong. It was always coming as "http". Fixed the issue by using the correct protocol that is configured in axis2.xml.
Comment by Paul N.
10814 | November 19, 2014 12:53:34 AM GMT
@Paul - Can you elaborate on what you changed in the axis2.xml file? Thanks!
Comment by External U.
10815 | February 04, 2015 11:14:28 AM GMT
The fix for this bug is available in the pre-release build of ColdFusion 11 Update 5
Comment by CFwatson U.
10816 | February 20, 2015 09:29:37 AM GMT