Mozilla does not refresh wsdl file changes once the file is loaded



Core Graveyard
Web Services
15 years ago
4 months ago


(Reporter: Ashish Bhatt, Unassigned)


Windows XP

Firefox Tracking Flags

(Not tracked)




15 years ago
As the summary says the wsdl file is not refreshed once it is loaded. Changes
only take effect when mozilla is restarted. Even clearing the cache does not work.

Steps to reproduce
1. Run any testcase that uses a wsdl file
2. Once the testcase successfully executes add a method to wsdl file
3. Call the new method, it gives proxy.method not a function
4. restart mozilla
5. Call the new method, works fine
i noticed that the first time i loaded in today's
build the meta refresh didn't kick in at all (no redirection occurred). is this
the same problem?

Comment 2

15 years ago
sairuh: I don't think the problems are related. The problem ( well not really a
problem IMO ) described in this bug is because of caching of the wsdl document
by the wsdl code. May be we need an extra method on the proxy to invalidate the
cached entry or something.  
Severity: normal → minor
Priority: -- → P5
Target Milestone: --- → mozilla1.4beta
Assignee: harishd → web-services
Target Milestone: mozilla1.4beta → ---
There was a bug in XMLHttpRequest until recently where it would always use
cached copy. Dunno if that is the cause of this bug, but if not, it should at
least help in fixing this... See bug 200706.

Comment 4

14 years ago
I'm not sure whether it should be considered as a bug. You could add version in
your targetNamespace, as suggested by w3, and so change version in it when WSDL
content change. As mozilla use targetNamespace to identify WSDL schema as long
as targetNamespace doesn't change I will never get reloaded.
Assignee: web-services → nobody
QA Contact: ashshbhatt → web-services
WSDL is gone from Gecko.
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE


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