Nice tip; do you have any stats on the volume of requests for those w3c schemas? I'm trying to get a picture of an "astonishing number" :)

We have had some around 90 million hit days, lower lately from a few services and our some automated blocking both at http and tcp level.

Hi Norm,

AIUI, the argument for using a catalogue over an HTTP cache is that it assures that the documents are available, even when there's a network segment if the cache needs to fetch something.

Putting aside the arguments that you can pre-seed a cache, and have it intelligently fail over, which I think address this concern about caching adequately in all but the most pathological case, why is a catalogue the appropriate solution in this use case?

I.e., if people are already going to the network to get their dependencies, and you just want to make that more efficient and less of a burden on the origin server, a cache is just as efficient, and far less intrusive and less failure prone; you don't have to do all of the mucking about, and you don't have to remember all of the different URIs you're using -- with the possibility of missing a few, or having more added later.

Hi Mark,

Yes, caching has a lot of advantages. And maybe anyone competent to setup a Glassfish application could install and manage one.

The advantage of catalogs (or one of them) is that they're dead simple to install and use. Many people with insufficient skill or experience or ability to setup their own local proxy cache have had great success with catalogs.

I've tried to bring the benefits of caching to the ease of catalogs with a caching catalog resolver. I'll write that up in the Glassfish context "real soon now".

Another advantage of catalogs, from my perspective, is it's easy to use them to lie. Send me a document that claims to need a DTD that has a system identifier that ends with "/docbook.dtd" and I point it to my local copy of DocBook V4.5. I don't care what version you claimed to need or what else you said about its identifier. Similarly, I use them to tinker with entity sets for online and print publishing too.

Hello all,

I was trying to use XML catalog to try to solve my problem with intensive Internet shutdown. When I call the method

org.jdom.Document document = sxb.build(list[i]);

where sxb = new SAXBuilder()

I have the following error: 504 for URL: http://www.w3.org/TR/xhtml1/DTD/xhtml-symbol.ent

How do I use your system to solve that?

I've done CatalogResolver resolver = new CatalogResolver();

But how I make it used by the build method?

Thx