remove the schema caching feature in xml resolution?

[cchou]

There has not been a requirement for the schema caching feature in xmlresolution. The schema caching code was developed without being discussed and spec out and it has created a lot of issues because it's creating state in the xmlresolution. As determined during daitss requirement phase, web caching is provided by Squid for the solution of the central web caching mechanism used by daitss, shared by submission, xmlresolution and aip descriptor validator.

Since the schema caching in xmlresolution is duplicating the effort done by Squid, perhaps we shall consider to remove the feature/code?

[cchou]

Lydia's concern: how does the fact that Squid cached schemas can't be viewed impact this?
Carol's comment: not all Squid-cached schemas are duplicated in the secondary cache.

Action item: for future discussion when time permits and/or if problems with the current process arise.