cocoon-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From br...@apache.org
Subject cvs commit: cocoon-2.0/src/webapp/WEB-INF cocoon.xconf
Date Fri, 02 May 2003 15:34:39 GMT
bruno       2003/05/02 08:34:39

  Modified:    src/webapp/WEB-INF cocoon.xconf
  Log:
  Disable incremental-processing by default.
  Removed incremental-processing parameter from XSLTC since it doesn't support it anyway.
  Added warning about bug 13186 and some other blah blah.
  
  Revision  Changes    Path
  1.3       +17 -4     cocoon-2.0/src/webapp/WEB-INF/cocoon.xconf
  
  Index: cocoon.xconf
  ===================================================================
  RCS file: /home/cvs/cocoon-2.0/src/webapp/WEB-INF/cocoon.xconf,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- cocoon.xconf	10 Mar 2003 09:12:07 -0000	1.2
  +++ cocoon.xconf	2 May 2003 15:34:39 -0000	1.3
  @@ -129,13 +129,26 @@
     </store-janitor>
     <!-- ============================ STORE END ========================= -->
   
  -  <!-- XSLT Processor:
  -    For Xalan: Turn 'incremental-processing' to true if you want a continous output (if
set to false the transformer 
  -    delivers SAX events after all transformations has been done). -->
  +  <!--+
  +      | XSLT Processor
  +      |
  +      | 'incremental-processing' (only works with Xalan) allows the XSLT
  +      | processor to start the output of the transformation as soon as possible.
  +      | if set to false, the transforer waits until the end of the
  +      | transformation to deliver the output.
  +      | WARNING: * if you enable incremental-processing, you should be aware of
  +      |            the following bug:
  +      |            http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13186
  +      |          * incremental-processing creates an additional, non-pooled thread.
  +      |          * using incremental-processing does not save memory, the input
  +      |            tree will still be build completely.
  +      |          * incremental processing is a 'static' thing in Xalan: if you
  +      |            enable it on one xslt-processor, enable it on all.
  +      +-->
     <xslt-processor class="org.apache.cocoon.components.xslt.XSLTProcessorImpl"
                     logger="core.xslt-processor">
        <parameter name="use-store" value="true"/>
  -     <parameter name="incremental-processing" value="true"/>
  +     <parameter name="incremental-processing" value="false"/>
     </xslt-processor>
   
     <!-- Xpath Processor:
  
  
  

Mime
View raw message