John Williams wrote:
>
> Carsten Ziegeler wrote:
> > > Inspecting the contents of the currValidity and prevValidity
> Maps I find
> > > that they are equivalent excepting that the prevValidity contains an
> entry
> > > "S-xml-1_=NOP Validity" so the test fails and code is
> > > re-generated.
> >
> > Huh! That's strange, now as far as I remember the code, the prevValidity
> > should
> > not contain "S-xml-1_=NOP Validity", as this is the validity for the
> > serializer
> > which is not used for internal pipeline calls. Hmm.
>
> I assume you mean src="cocoon://foo" calls and not internal-only
> pipelines,
> ie one with internal-only="true".
Yes.
>
> I have a fairly deep pipeline underlying the generated XSP "file"
> from which
> .java is generated. Maybe this depth exposes a problem in discarding
> NOPCacheValidity for internal pipeline calls. Can you see from
> the following
> which class is adding the "S-xml-1_=NOP Validity", I will then
> have a poke
> around/debug.
>
>
> Below are some details of the case causing the problems:
>
> create-categories.xsp - which has the "S-xml-1_=NOP Validity" in the
> prevValidity is:
> {
> aggregation of {
>
> aggregation of {tableDefs/categories.xml,
> appDef/categories/UISpecifics.xml and appDef/terminologyMappings.xml}
> transformed with stylesheets/buildUIStructure.xsl
> and
> appDef/categories/aCustomisation.xml
> }
> transformed with stylesheets/applyCustomisation.xsl
> }
> transformed with stylesheets/create.xsl
>
> This is what validities look like: (equal besides the "S-xml-1_=NOP
> Validity")
>
> prev: {G-file-7747944243312186483_=TimeStamp Validity[1062058603973],
> T-xslt--3690387136403106359_=Aggregated Validity[TimeStamp
> Validity[1061982760000]:TimeStamp Validity[1061976654000]], S-xml-1_=NOP
> Validity}
>
> curr: {G-file-7747944243312186483_=TimeStamp Validity[1062058603973],
> T-xslt--3690387136403106359_=Aggregated Validity[TimeStamp
> Validity[1061982760000]:TimeStamp Validity[1061976654000]]}
>
> Relevant part of the sitemap is as follows:
>
> <map:match pattern="table-*_*.xml">
> <map:aggregate element="root">
> <map:part src="cocoon://crm/table-{1}.xml"/>
> <map:part src="appDef/{1}/{2}.xml" strip-root="true"/>
> </map:aggregate>
> <map:transform src="stylesheets/applyCustomisation.xsl"/>
> <map:serialize type="xml"/>
> </map:match>
>
> <map:match pattern="table-*.xml">
> <map:aggregate element="UIDef">
> <map:part src="tableDefs/{1}.xml"/>
> <map:part src="appDef/{1}/UISpecifics.xml"/>
> <map:part src="appDef/terminologyMappings.xml"/>
> </map:aggregate>
> <map:transform src="stylesheets/buildUIStructure.xsl"/>
> <map:serialize type="xml"/>
> </map:match>
>
> <map:match pattern="*-*.xsp">
> <map:generate src="cocoon://crm/table-{2}.xml"/>
> <map:transform src="stylesheets/{1}.xsl"/>
> <map:serialize type="xml"/>
> </map:match>
>
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?
Carsten
