cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Wallez <>
Subject Re: [vote] move tree-processor in the main trunk
Date Thu, 07 Feb 2002 16:42:17 GMT
Jason Foster wrote:

> <snip/>
>> Just to make things clear : sitemap is only one of the possible uses 
>> of the TreeProcessor : it's a generic framework for implementing 
>> pipeline assembly languages (hence "Processor") with an evaluation 
>> tree (hence "Tree").
>> The supported languages are defined in treeprocessor.xconf or 
>> cocoon.xconf, and the interpreted sitemap is "only" a particular 
>> pipeline assembly language implemented using this framework, but we 
>> could implement others like Berin's proposal or Daniela Gehle's 
>> flowmap (go back to october 2001 in the archives to find them).
> Does that mean that XSPs that do not use compiled code fragments (Go 
> Python! Go JavaScript! Go JavaBean! Down with Java source code!) can 
> be handled by the TreeProcessor? 

Read carefully : "...a generic framework for implementing *pipeline 
assembly languages*...". XSP is a generator language and cannot be 
implemented with TreeProcessor. Moreover, TreeProcessor has no notion of 
taglib. Sorry ;)



Sylvain Wallez
Anyware Technologies -

To unsubscribe, e-mail:
For additional commands, email:

View raw message