remove call to new from nsSOAPEncoding constructor - use Init()

RESOLVED INCOMPLETE

Status

RESOLVED INCOMPLETE
16 years ago
11 months ago

People

(Reporter: mozilla, Unassigned)

Tracking

Trunk
mozilla1.5alpha
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
We create the nsSOAPEncodingRegistyr object mRegistry in the nsSOAPEncoding
constructor using new. Since we can't return failure from the constructor that
call needs to be moved into an Init() method.
(Reporter)

Updated

16 years ago
Status: NEW → ASSIGNED

Comment 1

16 years ago
This was raised before.  My concern with respect to adding an Init method is
that this is an object that may be constructed from Javascript, and it makes it
significantly more difficult for a javascript user to use.
Hmm, good point. Could we hook in to the JS constructor for this object and call
Init() from there, or do we use a generic one?
(Reporter)

Comment 3

16 years ago
Ray and I had a long talk about this. I then investigated with dougt and
dbradley and verified that do_CreateInstance gets called when you create an
XPCOM object in JS (like we are doing here). So it looks like we will be able to
make this change with no impact on script writers, or any existing scripts
calling SOAP stuff.
(Reporter)

Comment 4

16 years ago
This is going to be big and scary enough that I don't see it landing in 1.4f.
Target Milestone: --- → mozilla1.5alpha
(Reporter)

Updated

11 years ago
Assignee: mozilla → nobody
Status: ASSIGNED → NEW
QA Contact: ashshbhatt → web-services
We dropped SOAP.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE

Updated

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