Return-Path: 
 <users-return-55039-apmail-cocoon-users-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-users-archive@www.apache.org
Received: (qmail 31710 invoked from network); 1 Sep 2003 17:25:55 -0000
Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 1 Sep 2003 17:25:55 -0000
Received: (qmail 86429 invoked by uid 500); 1 Sep 2003 17:25:26 -0000
Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org
Received: (qmail 86382 invoked by uid 500); 1 Sep 2003 17:25:26 -0000
Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:users-help@cocoon.apache.org>
list-unsubscribe: <mailto:users-unsubscribe@cocoon.apache.org>
list-post: <mailto:users@cocoon.apache.org>
Reply-To: users@cocoon.apache.org
Delivered-To: mailing list users@cocoon.apache.org
Received: (qmail 86361 invoked from network); 1 Sep 2003 17:25:25 -0000
Received: from unknown (HELO apate.telenet-ops.be) (195.130.132.57)
  by daedalus.apache.org with SMTP; 1 Sep 2003 17:25:25 -0000
Received: from localhost (localhost.localdomain [127.0.0.1])
	by apate.telenet-ops.be (Postfix) with SMTP id 0655837EA1
	for <users@cocoon.apache.org>; Mon,  1 Sep 2003 19:25:23 +0200 (MEST)
Received: from yum.ot (D5774E46.kabel.telenet.be [213.119.78.70])
	by apate.telenet-ops.be (Postfix) with ESMTP id 7747C38089
	for <users@cocoon.apache.org>; Mon,  1 Sep 2003 19:25:19 +0200 (MEST)
Subject: Re: AW: AW: Incremental Processing in Cocoon 2.1
From: Bruno Dumon <bruno@outerthought.org>
To: users@cocoon.apache.org
In-Reply-To: <1062431870.1986.58.camel@yum.ot>
References: 
	 <299EBAE0F3D83242A853EADAC8E9EEC7019354@bigbender.bendit.bitz-bremen.de>
	 <1062431870.1986.58.camel@yum.ot>
Content-Type: text/plain
Organization: Outerthought
Message-Id: <1062436866.1981.109.camel@yum.ot>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.4 
Date: Mon, 01 Sep 2003 19:21:06 +0200
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

On Mon, 2003-09-01 at 17:57, Bruno Dumon wrote:
> 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.

Since I had that class lying around anyway, I thought I might as well
check myself, and for me it works, it prints out something like this:
Thread = PoolThread-4
Thread = Thread-16

I'm using the same changes to cocoon.xconf like you.

Maybe the fact that you're seeing other behaviour is caused by a change
in Xalan, or by an increased buffer size somewhere (less likely I
think). Maybe try using Xalan 2.5.1 with Cocoon 2.0 to see what that
gives.

-- 
Bruno Dumon                             http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
bruno@outerthought.org                          bruno@apache.org


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