Eric Caron schrieb:
Hello,
Our application is using some XSP files to generate some dynamic content
with ESQL. Despite having all parts of the sitemap set to noncaching and
reading in Cocoon that XSP is not cached by default, the XSP file seems
to be cached. My question is: how could XSP be caching and where/how do
I stop it?
AFAIK, XSP are not cached in any sense, but translated to Java classes
which are then compiled on the fly. This happens upon the first request
for the XSP. If you change the XSP file Cocoon detects this and
recreates and recompiles the Java class.
Proof that XSP is caching:
1) Simple sitemap that has pipeline's type as noncaching.
2) Simple pipleline that calls XSP as generator and serializes it as XML.
3) Generate page, change SQL, reload page (contents won't reflect change
to SQL)
4) Touch XSP file, reload page, new SQL changes will appear.
I don't understand - where are your SQL statements ? In the XSP ? If so
then changing the SQL also changes the XSP file !?
BTW for SQL calls you can also use Cocoon's SQL transformer, to avoid
writing an XSP yourself.
--
Wolfgang
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
