Thats fantastic news. I've had implementing a caching resolver on my TODO list for a while, so its nice to see that someone else has done it! :)

One item that was on my feature list was to have the cache interaction with HTTP headers, e.g. making use of ETags and Last-Modified where available. Is this something you've considered?

Cool, thanks! Do you think that there is chance of integrating this code directly into JDK, so there will be no need for installing and configuring this manually for each Java applications which deals with XML?

the caching seems a great addition Norm.

You say 'Caching requires write-access to a cache directory which you must identify through a Catalog property.' Is that a relative path to the directory from the properties file (or the catalog file), and can we ignore the write permissions for Windows please?

regards DaveP

Leigh, the cache does check Last-Modified headers when it retrieves an HTTP URI from the cache. I'll see about doing ETag checking as well.

Jirka, I think that's a possibility. :-)

Dave, I'm not sure I've tested a relative path for the cache; I suppose making it relative to the property file (if there is one) is as good an idea as any.

There's no way to "ignore" the write permissions, either the application can write to the directory that you specify for the cache or it can't. If it can't, uhm, caching won't work :-)