> On Tue, 2003-09-02 at 13:44, Hauke Ernst wrote: > > > -----Urspr�ngliche Nachricht----- > > > Von: Bruno Dumon [mailto:[EMAIL PROTECTED] > > > Gesendet: Montag, 1. September 2003 17:58 > > > An: [EMAIL PROTECTED] > > > Betreff: Re: AW: AW: Incremental Processing in Cocoon 2.1 > > > > > > On Mon, 2003-09-01 at 16:23, Hauke Ernst wrote: > > > > On Mon, 2003-09-01 at 14:04, Hauke Ernst wrote: > > > > > Hello, > > > > > > > > > > yes, this is how it worked for 2.0.3. > > > > > > > > > > The problem only occurs with 2.1. My configuration in cocoon.xconf > is > > > > > > > > > > <xslt-processor logger="core.xslt-processor"> > > > > > <parameter name="use-store" value="true"/> > > > > > <parameter name="incremental-processing" value="true"/> > > > > > </xslt-processor> > > > > > > > > > > <!--+ > > > > > | Xalan XSLT Processor > > > > > +--> > > > > > <component > class="org.apache.excalibur.xml.xslt.XSLTProcessorImpl" > > > > logger="core.xslt-processor" > > > > role="org.apache.excalibur.xml.xslt.XSLTProcessor/xalan"> > > > > > <parameter name="use-store" value="true"/> > > > > > <parameter name="incremental-processing" value="true"/> > > > > > <parameter name="transformer-factory" > > > > value="org.apache.xalan.processor.TransformerFactoryImpl"/> > > > > > </component> > > > > > > > > > > Unfortunately, this does not lead to a streamed output. > > > > > > > > - How can you be so sure? > > > > > > > > > > > > One of my test-transformations applied on a huge dataset takes > between 1 > > > > and minutes. In cocoon 2.0.3, I can see that the output is delivered > > > > immediately, in 2.1 the output starts to appear on the screen after > 1-2 > > > > minutes. > > > > The pipeline is > > > > > > > > <map:match pattern="renderhierarchicalfiletoc_xalan.xml"> > > > > <map:generate src="Testfiles/hierarchicalTOC.xml"/> > > > > <map:transform type="xalan" > > > > src="stylesheets/toc_fromhierarchicaltoc2.xsl"/> > > > > <map:serialize encoding="UTF-8" type="html"/> > > > > > > BTW, that "encoding" attribute doesn't exist. > > > > > > > </map:match> > > > > > > > > There is no sorting in the transformation which could prevent it > from > > > > streaming. > > > > > > ok, you might be right, though AFAIK nothing changed in Cocoon that > > > should prevent this behaviour. To be absolutely sure that it's Cocoon > > > who doesn't set the incremental-processing parameter, could you try > out > > > using the attached transformer? It prints the name of the current > thread > > > to standard output. If you put one such transformer right before and > one > > > right after your XSLT transform, it should print out two different > > > names. > > > > > > If you need more instructions on how to do this, just let me know. > > > > Thanx for your help. That transformation prints > > > > Thread = Thread-13 > > Thread = Thread-22 > > Ok, then we're sure Xalan is working in streaming mode. So it's > something else that makes the streaming not work. Do you have any other > components in your pipeline which could break the streaming? >
No, no idea. The pipeline (see above) is quite trivial, isn't it? > I've checked the serializers and their default buffer size is 8192, I > guess that shouldn't be a problem. You could always try changing it to 0 > by adding: > > <outputBufferSize>0</outputBufferSize> > > inside the map:pipe element of the pipeline implementation you're using > (likely the caching one). I use profile-caching and I added that node outputBufferSize, but no change in behaviour, sorry. Greetings, Hauke Ernst > > -- > Bruno Dumon http://outerthought.org/ > Outerthought - Open Source, Java & XML Competence Support Center > [EMAIL PROTECTED] [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
