Leszek Gawron escribió:
If user wants to make JXTG automatically cacheable he/she must
explicitly state it in configuration:
<map:generator src="org.apache.cocoon.template.JXTemplateGenerator">
<automatic-cache-key>
<use-sitemap-parameters>true</use-sitemap-parameters>
<use-request-parameters>true</use-request-parameters>
<use-request-attributes>true</use-request-attributes>
<use-session-parameters>false</use-session-parameters>
<use-cookie-parameters>false</use-cookie-parameters>
</automatic-cache-key>
</map:generator>
Hi Leszek,
Sorry to join the party too late. I have been busy the last months, but
I am still alive. :-)
I am just reading this mails and i will said: "Please forget the
following comment if you already discussed it":
It is fine to have a single place to define the jx caching behavior on
how it is going to generate the cache key. We also need to take into
account that in some cases the user may want a more fine grained
solution. Suppose the user wants (for some reason) to turn on jx caching
and avoid jx caching in few pipelines or the opposite: The user does not
want jx caching at all except in some few pipelines where he wants to
have jx cache working.
Given the above need we might use the standard parameter at the pipeline
level to overwrite default pipeline caching:
<map:generate src="myTemplate.jx" type="jx"/>
<map:parameter name="use-automatic-cache-key" value="true|false"/>
</map:generate>
Or somehow to overwrite the default configuration when we call the
generator.
Makes sense?
Best Regards,
Antonio Gallardo.
