If the type attribute on a <binding> element is mis-spelt and doesn't refer to any defined port type in a WSDL document, Mozilla hangs. We should throw some kind of error in this case...
Pointing to testcase that exhibits the problem in the URL field.
Harish and I looked at this and fixed it in his tree. Over to Harish so that he can check in the fix. Now, we get a WSDL processing error if the port type referenced on the <binding> element doesn't match any port type defined in the WSDL file.
Assignee: nisheeth → harishd
Created attachment 125539 [details] [diff] [review] Patch v1.0 [ Stop processing the wsdl document if the port name is invalid ]
15 years ago
Assignee: harishd → web-services
Status: ASSIGNED → NEW
Assignee: web-services → nobody
QA Contact: ashshbhatt → web-services
Native WSDL and SOAP support has been removed from Mozilla 1.9/Firefox 3
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.