Carsten Ziegeler wrote:
> The "S-xml-1_=NOP Validity" is appended by the xml serializer, so
> in fact the cached entry with the "S-xml-1_=NOP Validity" is for
> a complete pipeline with serializer. I'm still wondering
> why this is the value for prev. For which internal pipeline
> does this happen?
Any/every pipeline that builds up the xsp.
I created a very simple pipeline (see below) to test and I got the same
problem, ie "S-xml-1_=NOP Validity" appearing in the prev. I cannot find
the code appends the "S-xml-1_=NOP Validity" as follows:
prev: {G-file--7461341140568259924_=TimeStamp Validity[1060277818000],
T-xslt-2097470703455153761_=TimeStamp Validity[1062494248000], S-xml-1_=NOP
Validity}
curr: {G-file--7461341140568259924_=TimeStamp Validity[1060277818000],
T-xslt-2097470703455153761_=TimeStamp Validity[1062494248000]}
>From sitemap
<map:match pattern="test-*.xml">
<map:generate type="serverpages" src="cocoon://crm/test-{1}.xsp"/>
<map:serialize type="xml"/>
</map:match>
<map:match pattern="test-*.xsp">
<map:generate src="tableDefs/{1}.xml"/>
<map:transform src="stylesheets/test.xsl"/>
<map:serialize type="xml"/>
</map:match>
my serialiser is: org.apache.cocoon.serialization.XMLSerializer
my serverpages generator is:
org.apache.cocoon.generation.ServerPagesGenerator
>From .xconf
my event-pipeline
class="org.apache.cocoon.components.pipeline.CachingEventPipeline
