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: http://*****/. WSDL: http://****. WSDLException (at > /definitions/binding/operation[1]/input): faultCode=INVALID_WSDL: Encountered > illegal extension attribute 'message'. Extension attributes must be in a > namespace other than WSDL's.: It is recommended that you use a web browser to > retrieve and examine the requested WSDL document for correctness. If the > requested WSDL document can't be retrieved or it is dynamically generated, it > is likely that the target web service has programming errors. > > Does anyone hav any advice on making 7.0.2 validate WSDL the same way as > 7.0.1? > > I had really hoped to run 7.0.2 but this is a show stopper for us. The > webservice is a third party product I have no control over :( > > Any advice is appreciated. > > Thanks. > > (ps: this always occured on Tomcat, so I'm guessing it's the JVM upgrade or > Jrun changes that have done it?) > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:245109 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
