Mismatched port type on <binding> element causes a hang

RESOLVED INCOMPLETE

Status

RESOLVED INCOMPLETE
16 years ago
a year ago

People

(Reporter: nisheeth_mozilla, Unassigned)

Tracking

({hang})

Trunk
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [fix in hand], URL)

Attachments

(1 attachment)

(Reporter)

Description

16 years ago
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

16 years ago
Pointing to testcase that exhibits the problem in the URL field.
(Reporter)

Comment 2

16 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

Comment 3

16 years ago
Created attachment 125539 [details] [diff] [review]
Patch v1.0 [ Stop processing the wsdl document if the port name is invalid ]

Updated

16 years ago
Status: NEW → ASSIGNED
Whiteboard: [fix in hand]
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

Updated

a year ago
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.