148888 - Rid SOAP module of global |NS_NAMED_LITERAL_STRING| usage

Status: VERIFIED FIXED

(Core Graveyard :: Web Services, defect)

Description

[Brian Ryner (not reading)]

As discussed in bug 148884, these cause problems and are not supported.  The
SOAP module uses them extensively, and this prevents it from being included in a
static build.  (Couldn't find a good component for soap or xmlextras, please
change it if I missed something).

Comment 1

[Brian Ryner (not reading)]

.

Comment 2

[Ray Whitmer]

First, we will need to discover what the proper alternative is.

Comment 3

[Brian Ryner (not reading)]

Just to clarify, with the patch we implemented in bug 148884, this is no longer
causing a problem in the static build... so feel free to push this off as you
see fit.

Comment 4

[Heikki Toivonen (remove -bugzilla when emailing directly)]

harishd is now the SOAP owner, reassigning.

Comment 5

[John Gaunt (redfive)]

Is there a good replacement for these? As is commented above the issues with the
static build have been resolved, so do we even need bother with this fix? Can
this be Won't Fixed or Works-for-Med?

Is there something inherently evil about the NS_NAMED_LITERAL_STRING? Does a
newer, smaller, faster, implementation exist that does what we need it to do in
the SOAP code?

adding jag to cc after our brief talk in IRC the other day.

Comment 6

[John Gaunt (redfive)]

taking SOAP bugs

Comment 7

[Darin Fisher]

this bug was fixed with my patch for bug 234916

Comment 8

[Stephen Donner [:stephend] Not actively reading bugmail]

Verified FIXED using LXR.