Hello,
in Cocoon1 it was possible to use XSP logicsheets that were not configured by using a PI like:
<?xml-logicsheet href="logicsheets/hello.xsl"?>
In the Cocoon2 samples I see that now now there is an alternative way to specify the logicsheet by using within the <xsp:page> element:
<xsp:logicsheet location="logicsheets/hello.xsl"/>
However, no matter which version I use, I cannot get my <xsp:logic> and <xsp:expr> Blocks evaluated. Their content is copied verbatim to the output instead of compiled and executed. All the XSL-specific stuff I use in my logicsheet *does* work, which is why the hello.xsl logicsheet supplied with Cocoon also works fine - it simply does not use any <xsp:logic> or <xsp:expr> blocks.
So, what can I do? I know, I could configure my logicsheet in cocoon.xconf, but then I'd have to restart Cocoon on every change and I could not have specific logicsheets for virtual hosts - everything would be centralized.
Also, using the context: pseudo-protocol might be a solution for development, but according to the Wiki docs that does not carry over into production. I don't want to evaluate the logicsheet on every request, just when it is changed.
Any other ideas? In Cocoon1 it was enough to use the xml-logicsheet PI and everything else worked automatically - what effect does this PI have in Cocoon2 anyway?
Thanks in advance for any pointers,
Ulrich
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
