caching of generated xsp

I use generated XSP in my setup, which is working fine using the following sitemap code:

<map:match pattern="page-*.xsp">
   <map:generate src="" type="serverpages"/>
   <map:transform src=""/>
   <map:serialize type="xml"/>

</map:match>

<map:match pattern="page-*">
<map:generate src="" type="serverpages"/>

<map:transform src=""/>
<map:serialize type="html"/>
</map:match>

this is all working very well, does however generate and compile a

new xsp everytime a new request is made.

If the source was a file resource instead of a 'cocoon:/' source I take

that the xsp only gets compiled when the date of the source file is

newer than an existing compiled version.

How can control the 'modified' date for a cocoon resource?

thanks,

Jakob

Reply via email to