I am using Cocoon 2.0.4. Can someone please explain why the interpreted
sitemap engine is faster than the compiled one? Also, is it the "class"
attribute that determines whether Cocoon is using the compiled vs. the
interpreted sitemap engine? Seems like if you omit the class attribute,
it should use the interpreted engine but if you specify
class="org.apache.cocoon.sitemap.SitemapManager", it uses the compiled
engine??
<!-- ======================== The sitemap
============================== -->
<!--
Compiled sitemap engine. This is the original engine, that is now
replaced
by the interpreted engine (see above).
If you want to use this engine, uncomment this element and comment the
defaut one below.
Reloading of the sitemap:
The check-reload attribute determines if the sitemap is reloaded on
change.
Set to "no", the sitemap is generated once at startup.
Set to "yes", the sitemap is regenerated if it changes.
The reload-method specifies the method for the regeneration:
asynchron: WARNING: this reload method is broken and won't be fixed.
Synchron is now made default and preferred reload method.
synchron: If the sitemap changes, the sitemap is regenerated at the
next request. When the regeneration is finished, the request
(and all subsequent ones) is served with the new sitemap.
For development environment, set the check-reload to yes.
For production environment, it is advisable to set the check-reload
to no.
-->
<sitemap check-reload="yes"
class="org.apache.cocoon.sitemap.SitemapManager" file="sitemap.xmap"
logger="sitemap" reload-method="synchron"/>
<!--
New implementation of the sitemap. It is interpreted, so load times
are super-fast,
and request processing is slightly faster than with the compiled
engine thanks to
the HotSpot VM.
To use this engine, comment the declaration above and uncomment the
declaration below.
-->
<!-- sitemap logger="sitemap"/ -->
