Copy link to clipboard
Copied
I'm troubleshooting a problem a client is having with their migration from CF9 to CF10. A webservice call that previously worked, no longer is working. When I call it from my CF10 server, I get this error:
C:...\cfusion\stubs\WS-853189522_2...\service.java:10: class, interface, or enum expected package ...;
The ellipses are to replace proprietary files paths and names.
When I add the cfinvoke attributes wsversion and refreshwsdl, I get a "Unable to read WSDL from URL: .../service.asmx?WSDL" error instead of the above error. I also changed the default ws version from 2 to 1 in the CF Administrator, with no change. Are there any other known issues with CF10 that would interfere with a webservice call that worked in an earlier version?
I found the answer, and it turned out to be quite simple. After making the change to the default webservice version in CF Admin, I needed to restart the server. It now works, although I am curious as to why adding the wsversion attribute to the cfinvoke tag calling the webservice didn't work. My concern now is that if they add an Axis 2 webservice call in the future that they may run into this problem again.
Copy link to clipboard
Copied
I found the answer, and it turned out to be quite simple. After making the change to the default webservice version in CF Admin, I needed to restart the server. It now works, although I am curious as to why adding the wsversion attribute to the cfinvoke tag calling the webservice didn't work. My concern now is that if they add an Axis 2 webservice call in the future that they may run into this problem again.