cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vadim Gritsenko <>
Subject Re: [Ann/RFC] Virtual Sitemap Components
Date Mon, 11 Apr 2005 13:02:38 GMT
Sylvain Wallez wrote:
> Daniel Fagerstrom wrote:
>>     <map:transformers default="xslt">
>>       <map:transformer name="virtual2" 
>> src="org.apache.cocoon.transformation.VirtualPipelineTransformer">
>>         <map:source param="src2"/>
>>         <map:transform src="vpc-include.xsl">
>>            <map:parameter name="file" value="{src}"/>
>>         </map:transform>
>>         <map:transform src="vpc-include.xsl">
>>            <map:parameter name="file" value="{src2}"/>
>>         </map:transform>
>>       </map:transformer>
>>     </map:transformers>
>>   </map:components>
> It seems weird to me to see sitemap statements in the <map:components> 
> section. But they're also used as any other component. Hmm...
> What about either:
> - leave them in <map:components> but with special element names, e.g. 
> <map:virtual-generator> that maps to the VirtualPipelineGenerator class

It can be
       <map:virtual name="a">

That's enough information to build it.

> - or separate them in a <map:virtual-components> section just as we have 
> today <map:resources> and <map:views>?

What would happen with default component? If we go this route,


      <map:transformers default="???">
        <map:transformer name="a">

What will be in place of "???", and how this would relate to the default 
transformer in the map:components section?

> I would favor the second solution, even if this doesn't seem to be 
> absolutely necessary for the implementation.

I'd prefer first solution, which lacks the problem of default components.


>> VPCs are not cacheable yet. Its probably not that hard to add caching, 
>> but it requires that we extend the ProcessingPipeline interface with 
>> some methods that are needed for VPCs. It also requires that we find 
>> some syntax for declaring what pipeline type that should be used for a 
>> specific VPC.

Not sure that this is desired. We should have configurable caching, with 
following levels of caching:

   * No Caching: Returns null key
   * Caching: Returns pipeline key, validity
   * Caching, with private cache: Same as above,
     plus caches output of the pipeline locally (same as
     caching pipeline).

> Why do we have to choose a particular pipeline type? Isn't this defined 
> by the <map:pipeline type=""> surrounding the call to the VPC?

No, that pipeline is not used within VPC. VPC as a component is part of this 
external pipeline, but internally it has its own.


View raw message