Enhance schema cache in schema code and in wsdl code

RESOLVED EXPIRED

Status

Core Graveyard
Web Services
--
enhancement
RESOLVED EXPIRED
14 years ago
4 months ago

People

(Reporter: Cédric Chantepie, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040710 Firefox/0.9.0+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040710 Firefox/0.9.0+

Enhancement for patch of bug #244592, if schema corresponding to given
targetNamespace has already been loaded doesn't even try to do XML request.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
(Reporter)

Updated

14 years ago
Depends on: 249366
(Reporter)

Comment 1

14 years ago
Created attachment 152783 [details] [diff] [review]
Patch also using error handling proposal

depends on patch for #249366
(Reporter)

Updated

14 years ago
Attachment #152783 - Attachment is obsolete: true
(Reporter)

Updated

14 years ago
Summary: Prevent schema loaded from processing a new XML request if schema is already loaded → Enhance schema cache in schema code and in wsdl code
(Reporter)

Comment 2

14 years ago
Created attachment 152928 [details] [diff] [review]
Schema cache enhancement proposal

Remove duplicate schema code from nsWSDLoader, let schema cache only in
nsSchemaLoader. Improve cache support and add boolean pref
"webservices.schema.cache".
(Reporter)

Updated

14 years ago
Attachment #152928 - Attachment description: Schema cache enhance proposal → Schema cache enhancement proposal
(Reporter)

Updated

14 years ago
OS: MacOS X → All
Hardware: Macintosh → All
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/
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED

Updated

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