[hugh]

Hi,

It’s a major pita that the xml editor automatically loads xml schemas if the schemaLocation attribute is set. This is independent of validation — validation is off — but the editor I guess wants the schema so it can do intellisensey things.

Downloading and processing a complex graph of xsd files slows down the ide very noticeably, and twice has caused out of memory errors in the ide, forcing me to restart.

Secondly, “cancelling” the operation does not seem to interrupt anything. The ide continues sluggishly until MyEclipse is done with whatever it is doing.

Thirdly, if you’re *going* to download these xsd files, at least *cache* them. I sometimes see two or three “Downloading yourfile.xsd” for exactly the same file, pending simultaneously. Since you’re using HTTP to download the files, try using “If-modified-since” headers etc. to avoid redownloading unchanged files.

Fourthly: use the disk, not memory, for the cache.

We need to be able to switch off and on this feature. Intellisense is nice, and good work. We need a really interactive way to suppress or enable the feature — it would suck if the only way to switch is in some preferences dialog. A right mouse / context menu thing ought to do it.

Regards,

Hugh

[Riyad Kalla]

Hugh,
I agree with your suggestions but let me see if I can provide some help here to work around the current situation. 1) Try and use this tip to improve performance: http://myeclipseide.com/PNphpBB2+file-viewtopic-t-10087.html

and as far as using a cache of the XSD files, that is what the XML Catalog is for. You can add those XSD entries to the catalog then the editor will stop going online to grab them… I agree it can be a bit overzealous at times. We’ll work on that.

[hugh]

@support-rkalla wrote:

Hugh,
I agree with your suggestions but let me see if I can provide some help here to work around the current situation. 1) Try and use this tip to improve performance: http://myeclipseide.com/PNphpBB2+file-viewtopic-t-10087.html

and as far as using a cache of the XSD files, that is what the XML Catalog is for. You can add those XSD entries to the catalog then the editor will stop going online to grab them… I agree it can be a bit overzealous at times. We’ll work on that.

Thanks for your reply, Riyad. I will look at that reference.

It’s not clear to me from your remark about the XML catalog that you understand the caching issue I raised. I understand the purpose of the catalog. My remark is about standard HTTP client side programming. If MyEclipseIDE were to use the simple, standard HTTP caching headers, it would dramatically improve performance.

To be explicit: When you get an XSD file via HTTP (or any document for that matter), you save the ETag and Last-modified headers along with the document, in your cache. next time you need the document, you look in your cache, and if it is present, you ask send a “conditional GET” to the server. That is, you send a GET to the server along with headers “If-Modified-Since” + the saved date header, and/ or “If-modified” + the saved ETag header. If the server returns 304 not Modified, you don’t need to get the document again.

As much a a pain as it was to spell it out in that prev. paragraph, it’s less painful than all the waiting.

And XML catalog, sure, if I’m using a certain schema over and over, maybe I’ll take the trouble and stop everything to install some schemas there. But if you guys would cache HTTP properly, I’d rarely need to do that.

Thanks again,

Hugh

[Author]

Posts