The SourceCacheImpl class uses the source uri for a key to the cached
object. I believe that I have run into problems with this in the past
with templated publications.
fallback://config/ac/usecase-policies.xml can refer to a number of
different files depending upon the publication from which it is being
used, but it is used for the key to the cached object in
SourceCacheImpl. This has the potential to produce unexpected results.
Should the SourceCache objects be publication specific (key of something
like {pub}:fallback://config/ac/usecase-policies.xml)? I guess we could
also just use the absolute url as a key for the cached object. Or
perhaps I am missing something and just need some sleep.
--Doug
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
