Hi Felix,
I was only experiencing this problem with xsl:include="fallback://...
ex:
pub1 and pub2 both use default for a template
-pub1 has an xslt dir with its own page2xhtml.xsl (all other xsl falls
back to default/xslt/)
-pub2 doesn't have an xslt dir
-request comes in for /pub1/authoring/xhtmlres.html
-at some point the sitemap does a transform using
default/xslt/page2xhtml-xhtml.xsl
-all that is in the xsl is fallback://xslt/page2xhtml.xsl
-pub1/xslt/page2xhtml.xsl is used
-expected result
-request comes in for /pub2/authoring/xhtmlres.html
-at some point the sitemap does a transform using
default/xslt/page2xhtml-xhtml.xsl
-all that is in the xsl is fallback://xslt/page2xhtml.xsl
-***pub1/xslt/page2xhtml.xsl is used***
-unexpected result
Setting the XSLT Processor's use-store param to false seems to fix the
problem for me. Don't know if performance will take a big hit though.
HTH
--Doug
Felix Röthenbacher wrote:
Hi
I wonder how the fallback: protocol behaves when it comes
to caching? If several publications are in use at the same
time and resources are accessed with the fallback: protocol,
it seems that a cached resource is used instead of the resource
which applies to the current publication. Has anyone else
seen this behaviour?
Thanks for sharing your thoughts,
- Felix
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
