> ... which means that these two URLs produce different
> Validity objects
> in from-an-xsp pipeline. Is it right?
> But what about validity? Seems that it changes.
>
Yes the validity changes, but ContentAggregator's key is the same. If
two objects have the same Key, it looks like only the second one is
stored/retrieved from the cache.
> Right now it has:
> key += HashUtil.hash("P=" +
> part.stripRootElement + ':' +
> current.getSystemId() + ';');
>
> And that is correct.
>
Yes, I mean to add my change *after* the other lines, so that
getLastModified is part of the key. Here is the whole section:
if (current.getLastModified() == 0) {
return 0;
} else {
if (part.element == null) {
key += HashUtil.hash("P=" +
part.stripRootElement + ':' +
current.getSystemId() + ';');
} else {
key += HashUtil.hash("P=" +
part.element.prefix +
':' +
part.element.name +
'<' + part.element.namespace +
">:" +
part.stripRootElement + ':' +
current.getSystemId() + ';');
}
key += current.getLastModified(); // <-- ADD THIS
LINE
}
If this still doesn't make sense, I will take a moment to try to
reproduce this in the standard 2.0.3 distribution....
Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
