DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=32095>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=32095 Cache Event invalidation not working with non sitemap components ------- Additional Comments From [EMAIL PROTECTED] 2004-11-09 02:43 ------- I've taken a closer look and I think something is wrong with XMLFileModule too. From what I see, it never stores the SourceValidity, but creates a new one from the src string and checks that. As I recall, though the SourceValidity contract is: - retrieve a previously used Source which may not be valid - call getValidity() on it and on that SV call .isValid() - if that answers VALID or INVALID you have your answer, move on - if that answers "not known" (int 0), then resolve a new source with the same path - on that new Source, call getValidity and pass that to usedSource.isValid (newValidity) So, based on this I would guess that this is also broken for things like ExpiresValidity, which requires that you check the already used Validity object, not create a new one. To test, modify your test to return a new ExpiresValidity due to expire long in the future. If this is indeed broken, you should be able to modify the returned result every time instead of only after the expiration times out. A fix for the event-cache would rely on this problem being fixed. Geoff
