cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Torsten Curdt <tcu...@dff.st>
Subject Re: [vote] move tree-processor in the main trunk
Date Thu, 07 Feb 2002 12:34:01 GMT
> Ok,
>
> sitemap code generation is getting slower every day and is likely to
> become worse as we add more bugfixes and error generation.
>
> Clearly, developping on cocoon with 20 seconds delays between changes is
> a nightmare and would scare people away instantly.
>
> Now that we have a functional interpreted sitemap engine, I suggest we
> move this on the main trunk and keep improving on it from there.

+1

> Also, I would like to propose a name change: TreeProcessor isn't exactly
> self-explanatory as a 'sitemap interpreter'.

So you propose "SitemapInterpreter"? Since the compiled one is
actually named the "SitemapManager"... what about

 - InterpretedSitemapManager
 - SitemapInterpreterManager
 - ... ?

> Moreover, I'd love to be able to decide what to use (interpreted or
> compiled) from cocoon.xconf.... or, in case the treeprocessor ends up
> faster all the time, simply blast the compiled version and get rid of
> that stupid javac!

...thought that's already there?!

Taken from the list:

cocoon.xconf:
  <!--
    <sitemap file="sitemap.xmap"
             reload-method="asynchron"
             check-reload="yes"
             logger="sitemap"/>
  -->

  <sitemap class="org.apache.cocoon.treeprocessor.TreeProcessor"
           logger="sitemap"/>

--
Torsten


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message