Closed
Bug 121643
Opened 24 years ago
Closed 24 years ago
SOAP is not correctly identifying complex types with simple content
Categories
(Core :: XML, defect)
Tracking
()
RESOLVED
FIXED
mozilla0.9.9
People
(Reporter: rayw, Assigned: rayw)
Details
The checks within the product need to all check the content model of a complex
type and if it is simple, treat it as simple. No tests yet for this.
| Assignee | ||
Updated•24 years ago
|
Status: NEW → ASSIGNED
| Assignee | ||
Updated•24 years ago
|
Target Milestone: --- → mozilla0.9.9
| Assignee | ||
Comment 1•24 years ago
|
||
I checked in a fix to this, with no complaints. I added a function
HasSimpleValue to do the more extended test in nsDefaultSOAPEncoding and invoked
it throughout -- much easier than changing Schema IDL, although that might have
been justified. I also fixed places where the superclass was not being properly
identified, where the type was a simple restriction instead of a complex type.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Updated•23 years ago
|
QA Contact: petersen → rakeshmishra
You need to log in
before you can comment on or make changes to this bug.
Description
•