I can now confirm (at least on my development server)... the 7.0.2 updater does
NOT seem compatible with one of my older web service's WSDL (even upon
rolling the older axis.jar back as Tom suggested). The 7.0.2 updater DOES
work after making the modification that Andrew has mentioned -
I can now confirm (at least on my development server)... the 7.0.2
updater does NOT seem compatible with one of my older web service's
WSDL (even upon rolling the older axis.jar back as Tom suggested).
The 7.0.2 updater DOES work after making the modification that Andrew
has mentioned -
Tom, thanks for the feedback. I agree 100% that the WSDL is invalid (Mindreef's
Soapscope tool revealed the WSDL to have 6 errors related to message attributes
being in the input and output tags.
Oddly, but the same invalid WSDL was working on our development server (and
still is on our
Tom, thanks for the feedback. I agree 100% that the WSDL is invalid (Mindreef's
SoapScope tool revealed the WSDL to have 6 errors related to message attributes
being in the input and output tags).
Oddly, but the same invalid WSDL was working on our development server (and
still is on our
I ran into the same issue with one of our web services after upgrading
to the 7.0.2 Updater.
Could not generate stub objects for web service invocation.
Name: http://: http://. WSDLException (at
/definitions/binding/operation[1]/input): faultCode=INVALID_WSDL:
Encountered illegal
Hi Tom. Thanks for your reply. The WSDL is browse-able with IE and FireFox,
so at least it's well-formed. Of note: it's the same WSDL that runs fine under
CFMX 7.0.1 hotfix 2. In fact we rolled our affected server back to 7.0.1
yesterday and the web service's WSDL is working again. Here's the
Subject: Re: 7.0.2 Updater - tighter WSDL validation?
Hi Tom. Thanks for your reply. The WSDL is browse-able with IE and
FireFox, so at least it's well-formed. Of note: it's the same WSDL that runs
fine under CFMX 7.0.1 hotfix 2. In fact we rolled our affected server back
to 7.0.1 yesterday
I ran into the same issue with one of our web services after upgrading to the
7.0.2 Updater.
Could not generate stub objects for web service invocation.
Name: http://: http://. WSDLException (at
/definitions/binding/operation[1]/input): faultCode=INVALID_WSDL:
Encountered illegal
]
Sent: July 1, 2006 1:08 AM
To: CF-Talk
Subject: RE: 7.0.2 Updater - tighter WSDL validation?
Um, I was referring to the WSDL of a webservice... no CFC here :) The
webservice wasn't built in CF either.
I couldn't consume the webservice using CFMX7.0.2, so we saved the WSDL to
file and changed some
:[EMAIL PROTECTED]
Sent: Saturday, 1 July 2006 5:46 AM
To: CF-Talk
Subject: Re: 7.0.2 Updater - tighter WSDL validation?
Andrew,
I'm not familiar with INPUT tags being part of the CFC set of tags...can you
enlighten me?
TIA
Cheers
Bryan Stevenson B.Comm.
VP Director of E-Commerce Development
.
-Original Message-
From: James Holmes [mailto:[EMAIL PROTECTED]
Sent: Friday, 30 June 2006 1:59 PM
To: CF-Talk
Subject: Re: 7.0.2 Updater - tighter WSDL validation?
You could try saving the WSDL locally and editing it yourself to
correct the problem.
On 6/30/06, Andrew Stevens [EMAIL PROTECTED
Hi I've just upgraded some servers to 7.0.2.
We have a web service that previously worked fine. Now the WSDL is no longer
acceptable/valid;
Name: http://*/. WSDL: http://. WSDLException (at
/definitions/binding/operation[1]/input): faultCode=INVALID_WSDL: Encountered
illegal extension
You could try saving the WSDL locally and editing it yourself to
correct the problem.
On 6/30/06, Andrew Stevens [EMAIL PROTECTED] wrote:
Hi I've just upgraded some servers to 7.0.2.
We have a web service that previously worked fine. Now the WSDL is no longer
acceptable/valid;
Name:
13 matches
Mail list logo
