Hi all,
 
I'm using the official release version of Cocoon 2.0, and I'm running into some weird caching behavior with XSP's.  Basically, it looks like Cocoon gives me back a cached version of my XSP on every other request.  So, for example, if my XSP looks like this:
<xsp:page language="java" xmlns:xsp="http://apache.org/xsp">
    <xsp:logic>
        int counter = 0;
    </xsp:logic>
   
    <page>
        <xsp:logic>
            counter++;
        </xsp:logic>
        <title>State Test</title>
        <content>
            counter is <xsp:expr>counter</xsp:expr>.<br/>
        </content>
    </page>
</xsp:page>
And if my pipeline looks like this:
<map:match pattern="stateTest.xsp">
      <map:generate type="serverpages" src="stateTest.xsp"/>
      <map:transform src="stylesheets/page/simple-page2html.xsl"/>  <!-- uses xslt default -->
      <map:serialize type="html"/>
</map:match>
What I see is that my counter increments on every other request:
    1st request --> counter is 1
    2nd request --> counter is 1
    3rd request --> counter is 2
    4th request --> counter is 2
    5th request --> counter is 3
    ...
 
Can someone tell me why Cocoon behaves like this, and where the setting is that causes this (if there is one)?  Thanks!
 
Harry

--------------
Harry Lai
[EMAIL PROTECTED]
512.342.2623 x2170

 

Reply via email to