Closed
Bug 200426
Opened 22 years ago
Closed 8 years ago
Mismatched port type on <binding> element causes a hang
Categories
(Core Graveyard :: Web Services, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: nisheeth_mozilla, Unassigned)
References
()
Details
(Keywords: hang, Whiteboard: [fix in hand])
Attachments
(1 file)
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...
|
Reporter | |
Comment 1•22 years ago
|
||
Pointing to testcase that exhibits the problem in the URL field.
|
|
Reporter | |
Comment 2•22 years ago
|
||
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
|
||
Updated•21 years ago
|
Assignee: harishd → web-services
Status: ASSIGNED → NEW
|
||
Updated•16 years ago
|
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
Closed: 8 years ago
Resolution: --- → INCOMPLETE
|
||
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•