280283 - Some characters in SOAP operation names gets munged in WSDL proxy method names

Status: RESOLVED EXPIRED

(Core Graveyard :: Web Services, defect)

Description

[Mårten Svantesson]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

Some non alphanumeric characters in operation names gets munged in WSDL proxy
method names. For example TE_att-achment_getDetails becomes
TE_005fatt_002dachment_005fgetDetails. It seems like the characters gets
replaced by _ followed by the string representation of their UCS-2 encoding.

The file http://www.f.kth.se/~f95-msv/testop.html illustrates the problem using
the WSDL file http://www.f.kth.se/~f95-msv/foo.xml containing a couple of
examples of problematic operation names.

(Surprisingly the proxy methods still work.)

Reproducible: Always

Steps to Reproduce:

Comment 1

[timeless]

well, erp. - isn't a legal character for javascript symbols, and clearly _ was
chosen as the escape character. what precisely do you want to have happen?
should people be required to use: foo["a-_b"]() to call these silly soap methods?

Comment 2

[Mårten Svantesson]

I found the problem with an WSDL file containing operations with underscores. It
was a bit surprising to get problems with those...
The other odd characters in the given test file were only put in to see what
happens and illustrate the mechanism.

As for how to handle characters that are illegal in javascript I do think that
something like what you described would be suitable.:

proxy.op["strange+operation"]()

Comment 3

[timeless]

i'm glad you think that's clever, i personally think that's insane.

Comment 4

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 5

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.