Hi,
Is the hereunder described issue with XML serializers known?
A sitemap having several xml serialization patterns:
<map:pipeline>
<map:match pattern="showterm.xml">
<map:generate type="term"/>
<map:serialize type="xml"/>
</map:match>
<map:match pattern="hierarchies">
<map:generate type="topterms"/>
<map:serialize type="xml" />
</map:match>
...
This pipeline is observed to have an 'eternal cache':
whichever pattern is matched first gives the correct answer.
All subsequent requests, whatever the URL, whatever the get-parameters
return the contents of the cache.
In order to get fresh results you need to destroy the caching stuff
under work/... first.
Is this known? I may as well get rid of it by checking out the very last
cocoon-3 version! Just asking.
Thank you,
Jos
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
