cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Wallez <>
Subject Re: Configuration of TreeBuilder
Date Fri, 26 Apr 2002 17:42:58 GMT
Carsten Ziegeler wrote:

>currently the TreeBuilderSelector is not a real Avalon Component,
>it is configured in an XML file called "treeprocessor-builtins.xml".

What makes it not a real Avalon component that its class name is 
hardcoded in TreeProcessor, not that its configuration isn't in 
cocoon.xconf. Now is there a real need to have an alternate 
implementation for this basic selector ?

>Can we make a real avalon component out of this and move the
>configuration into the cocoon.xconf?
>I think this would reduce the code of the treeprocessor in some
>areas and make the configuration more consistent with the
>configuration of other components.

The configuration of the pipeline languages is in a separate file 
because designing/modifying a pipeline language is not a common task and 
IMO doesn't belong to the usual system-assembly tasks handled by 
cocoon.xconf. Also, I think adding these 160 lines of declarations won't 
help frightened newbies to understand the big picture.

Nevertheless, the treeprocessor allows to name an alternate 
configuration file using the "config" attribute recently added by 
Ovidiu. If you want to, we can also allow the full treeprocessor 
configuration to be present in cocoon.xconf.


Sylvain Wallez
  Anyware Technologies                  Apache Cocoon 

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

View raw message