Closed Bug 107794 Opened 23 years ago Closed 23 years ago

Rewrite SOAP

Categories

(Core :: XML, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla0.9.9

People

(Reporter: hjtoi-bugzilla, Assigned: rayw)

References

Details

I am opening some bugs to track the progress.
Tentatively scheduling for 0.9.7.
No longer blocks: 107795
Target Milestone: --- → mozilla0.9.7
Has Netscape/mozilla.org considered going with XML-RPC rather then SOAP? To my understanding, SOAP is just Microsoft and W3C's bloated, buggy fork of XML-RPC. Is there a project page anywhere for an outline of the plan? I can't find one.
Mozilla already has support for XML-RPC AFAIK. SOAP was worked on by the same guy who did XML-RPC by the way, and has several nice features that XML-RPC doesn't. So it's good that Mozilla will support both.
Status: NEW → ASSIGNED
The to do list looks like this (in some order): 1. Land the branch SOAP_20010403_BRANCH onto the tip, working out the MOZ_SOAP versus MOZ_WSDL conflicts over schema, which is needed by both. 2. Work out security issues so that xpconnect works correctly with it. 3. Complete the serialization / deserialization implementations of complex types and arrays. 4. Lots of tests.
Target milestone changed.
Target Milestone: mozilla0.9.7 → mozilla0.9.8
Target Milestone: mozilla0.9.8 → Future
Target Milestone: Future → mozilla0.9.9
We are getting closer to closing this bug. Perhaps it is now time to close it and open new bugs for the remaining issues. The code is there for arrays and complex types, and it has been on the tip for some time. Look in mozilla/extensions/xmlextras/tests/soap* for the few tests that have been written (3 out of 4 work and there is a patch for the 4th). These give simple examples of how to use the new SOAP. We are still fixing / expanding the code at this time to handle arbitrary order and better control embedded types.
I just committed more code related to structs and SOAP. I gave structs their own encoder / decoder. About everything is now there to carefully encode/decode while following the model group of the type and going down to the subtypes. This was the biggest thing I had designed for that was not there yet. I may get around to writing test cases for it, but the way we get good test cases is when the proxies start working, because they deliver schema with everything they do. This didn't have a bug logged on it. I have not added the code to treat repeated elements as arrays, but it is unclear whether that is a good thing to do. There are still lots of things outside of Arrays and Structs (and in some cases inside of them) which are gray areas, not because we cannot support them, but because it is not clear how we should support them.
I am still working on smaller things, but they all have bugs logged, so I am closing this.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
QA Contact: petersen → rakeshmishra
You need to log in before you can comment on or make changes to this bug.