Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <31DF72A980E5D511B48C000102BD8685061DB3C1@calexc01.diginsite.com>
From: Ralph Goers <Ralph.Goers@digitalinsight.com>
To: "'dev@cocoon.apache.org'" <dev@cocoon.apache.org>
Subject: RE: JXTemplate performance
Date: Wed, 5 May 2004 15:48:28 -0700 
MIME-Version: 1.0
Content-Type: text/plain

Oops. I forgot to mention that the main layout could handled by the
jxtemplate generator in this case.

-----Original Message-----
From: Ralph Goers 
Sent: Wednesday, May 05, 2004 3:02 PM
To: 'dev@cocoon.apache.org'
Subject: RE: JXTemplate performance

This may sound a tad bit bizarre, but it looks like I could define a fairly
generic layout with sections for "header", "nav", "body", "footer", etc.
Each section can use import uri="cocoon:something" to generate that section.
In turn jxtemplate generator can be used in those to create subsections,
etc.  This is a lot like what we do with XSLT although we create the
separate parts through aggregation and then use a layout stylesheet to put
it all together.

Does this seem realistic and might it perform better than XSLT?  In both
cases (for us) the header, nav, and footer are constant but the body (or a
part of it) changes with every request.

Ralph

-----Original Message-----
From: Sylvain Wallez [mailto:sylvain@apache.org] 
Sent: Wednesday, May 05, 2004 2:33 PM
To: dev@cocoon.apache.org
Subject: Re: JXTemplate performance

JXTemplate as a transformer certainly runs way slower than XSLT, since 
the template being the input of the transformer, its compilation occurs 
for every request.

Also JXTemplate isn't cachable both in its generator and transformer 
incarnations.

Sylvain

-- 
Sylvain Wallez                                  Anyware Technologies
http://www.apache.org/~sylvain           http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }